You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the tests in ShellTest fail with non-deterministic errors. Here is an example:
Error: testEmptyLines Time elapsed: 0.194 s <<< FAILURE!
java.lang.AssertionError:
Expected: is "(* a comment followed by empty *)\r\n\r\n;\r\n- (* a comment followed by empty *)\r\r\n- \r\r\n- ;\r\r\n- \r\r\n"
but: was "- (* a comment followed by empty *)\r\n\r\n;\r\n(* a comment followed by empty *)\r\r\n- \r\r\n- ;\r\r\n- \r\r\n"
at net.hydromatic.morel.ShellTest.testEmptyLines(ShellTest.java:134)
The cause seems to be a race-condition in JLine. Usually the echoed command appears first in the output, but occasionally the output appears first. Note that the "- " prompt has changed positions in the expected versus actual output.
The text was updated successfully, but these errors were encountered:
The problem seems to be that JLine has a race-condition.
The solution is for the GitHub action to set an environment
variable 'morel.ci' when running 'mvn test'; the
non-deterministic tests in ShellTest check that variable and
skip if it is set.
When run from the command-line, all tests in ShellTest will
run as normal. This ensures that they get run occasionally.
Non-determinism seems to be less of a problem from the
command-line, perhaps because there are more cores available,
and perhaps because it is easier to re-run.
Fixes#107
Some of the tests in ShellTest fail with non-deterministic errors. Here is an example:
The cause seems to be a race-condition in JLine. Usually the echoed command appears first in the output, but occasionally the output appears first. Note that the "- " prompt has changed positions in the expected versus actual output.
The text was updated successfully, but these errors were encountered: