You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2023/02/08 15:28:00 UTC

[jira] [Assigned] (DAFFODIL-2778) Make the CLI thread-safe

     [ https://issues.apache.org/jira/browse/DAFFODIL-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence reassigned DAFFODIL-2778:
----------------------------------------

    Assignee: Steve Lawrence

> Make the CLI thread-safe
> ------------------------
>
>                 Key: DAFFODIL-2778
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2778
>             Project: Daffodil
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 3.5.0
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Minor
>
> The CLI is not currently thread safe. In most cases this isn't a big deal because the CLI is wrong from a command line and so each instance of daffodil runs in its own process space and we don't have to worry about thread safety.
> However, when testing the CLI, we run it in separate threads instead of forking, which substantially decreases the time needed to run tests. But because the CLI isn't thread safe, we must disable parallel execution of tests in daffodil-cli/build.sbt.
> Ideally we could modify the CLI so it was thread safe, which would allow parallel test execution. It would also also libraries to run the CLI without forking if it was something they needed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)