stevedlawrence commented on PR #1108: URL: https://github.com/apache/daffodil/pull/1108#issuecomment-1813150458
With the updates to change debug tests to fork, we now get a number of failures on windows. I've tracked down the cause to these lines: https://github.com/apache/daffodil/blob/main/daffodil-cli/src/main/scala/org/apache/daffodil/cli/debugger/CLIDebuggerRunner.scala#L61-L66 These lines caused all of our CLI tests that used jline to use a `DumbTerminal` because they didn't use normal stdin/stdout. But by changing these tests to fork, they now use normal stdin/stdout and so use the `TerminalBuilder` to get a jline terminal. For whatever reason, the terminal that jline returns causes random failures. I haven't yet figured out why, if there is a workaround, or if there's an alternative way to detect that we are doing integration tests and should use a DumbTerminal. Interestingly, when these CLI tests fail, jline outputs: > WARNING: Unable to create a system terminal, creating a dumb terminal So it seems like it's using the same DumbTerminal. Maybe it's configured in a slightly different way, or its terminal detection is somehow breaking things... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
