[
https://issues.apache.org/jira/browse/DAFFODIL-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2833.
-----------------------------------
Verified the specified commit (commit 81de17089a175f518b91ac5e6a8c3a8d29b6add7)
is included in the latest pull from the daffodil repository.
Verified, via review, changes identified in the commit comment were
implemented.
Verified the affected daffodil subproject sbt test suites executed successfully
including the added tests.
> CLI Trace not visible to expectit functions
> --------------------------------------------
>
> Key: DAFFODIL-2833
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2833
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 3.5.0
> Reporter: Olabusayo Kilo
> Assignee: Olabusayo Kilo
> Priority: Minor
> Fix For: 3.5.1
>
>
> When fixing DFDL-2694, we found that the cli.expect function isn't able to
> read the trace output. Instead the test_CLI_Tdml_Trace_singleTest fails with
> the following:
> {noformat}
> net.sf.expectit.ExpectIOException: Expect operation fails (timeout: -1 ms)
> for matcher: contains('parser:'){noformat}
> We can the trace output on the console, so it is unclear why expectit cant.
> Some preliminary research shows the cli tests output to a PipedOutputStream,
> and may be a good place to start.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)