You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Olabusayo Kilo (Jira)" <ji...@apache.org> on 2023/07/12 23:01:00 UTC

[jira] [Assigned] (DAFFODIL-2833) CLI Trace not visible to expectit functions

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

Olabusayo Kilo reassigned DAFFODIL-2833:
----------------------------------------

    Assignee: Olabusayo Kilo

> 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
>
> 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)