[
https://issues.apache.org/jira/browse/DAFFODIL-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-2778.
--------------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
Fixed in 10b74f4fc6ff5a12e2f7bd24e053631deebd714a
Note that Log4j was replaced with SLF4j, which made making thread specific log
capture and log level more straightforward.
> 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
> Fix For: 3.5.0
>
>
> 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)
