[
https://issues.apache.org/jira/browse/DAFFODIL-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Wass closed DAFFODIL-2461.
-------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Fixed in
[0be304dc120f5a659bf6118762ea6237b1c24263|https://github.com/apache/incubator-daffodil/commit/0be304dc120f5a659bf6118762ea6237b1c24263]
> Intermittant test failure in schematron CLI tests
> -------------------------------------------------
>
> Key: DAFFODIL-2461
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2461
> Project: Daffodil
> Issue Type: Bug
> Components: CLI, Infrastructure, QA
> Reporter: Steve Lawrence
> Assignee: John Wass
> Priority: Minor
> Fix For: 3.1.0
>
>
> In a recent GitHub Actions tests, there was a failure with checking the error
> code of a test:
> https://github.com/apache/incubator-daffodil/pull/477/checks?check_run_id=1745505882#step:10:200
> Based on the output, it's looks like Daffodil did the right thing, but then
> failed to detect the correct error code. The error makes this clear:
> {quote}
> Error: Test org.apache.daffodil.schematron.TestEmbedded.extends2 failed:
> unparseable ec, D:\a\incubator-daffodil\incubator-daffodil>
> {quote}
> This "unparseable ec" is expecting an integer, but instead it got the command
> prompt. Looking at the output, we can see that we are sending the "echo
> %errorlevel%" command before we get to the prompt, and our code seems to be
> accepting the command prompt as a match for the error code.
> Perhaps we need to have an expect that looks for the prompt before sending
> new line?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
