-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test framework fails to report errors #19542
Comments
I could reproduce it with the sligtly faster command
Also with |
It seem that this issue started showing up with 756ae34. This change is probably making it easier to trigger another issue. |
Minimal reproduction
Note the line
|
I have no idea what is causing it yet. I suspect that the issue is in the reporter. We can patch the current failure on |
* Disable `tests/neg/i8984.scala`. * Fix broken tests
As far as I can tell, this only affects |
* Disable `tests/neg/i8984.scala` ([see #19542](#19542 (comment))) * Fix broken tests
I noticed
there is no trailing empty string in the result. Yes, I'm a total noob. |
The issue is that one of the reporters throws an exception. Furthermore, that exception throws an exception on |
Part of scala#19542. We protect against the case where `Exception.getMessage` or `Exception.getStackTrace` throw an exception.
To close this issue we need to
|
…19566) Part of #19542. We protect against the case where `Exception.getMessage` or `Exception.getStackTrace` throw an exception. This change makes `testCompilation tests/neg/i8984.scala` fail as expected. `tests/neg/i8984.scala` is currently disabled (see #19561). `tests/neg/i8984.scala` will not be fixed in this PR. Making the test framework more resilient is a priority. Fixing this is the last part of #19542.
Relieved it was not |
* Disable `tests/neg/i8984.scala`. * Fix broken tests [Cherry-picked 92c5cb2][modified]
Backports #19561 to the LTS branch. PR submitted by the release tooling. [skip ci]
Compiler version
3.4.1-RC1
Minimized example
Given in #19538.
Output
scala3-boostrapped/test passes.
Expectation
The tests should fail since there are two errors in neg tests that fail. They get reported, but don't show in the test summary.
I also noted that in the output on the terminal error counts oscillate for other kinds of tests as well. I.e. pickling would jump from 0 to 1 and back. But in the end nothing gets reported.
It looks like a bunch of race conditions that were introduced recently to the testing framework. I am very surprised that I am the first to notice this.
This is a serious problem that needs to be treated at the highest priority. Without a reliable testing framework we cannot make progress anywhere.
The text was updated successfully, but these errors were encountered: