-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Don't consider panic fixes as "new failures" #1294
Conversation
Test262 conformance changes:
New panics:
|
I also took the opportunity to improve a bit the code and update the Test262 suite. |
Benchmark for fb48172Click to view benchmark
|
Benchmark for 59a6743Click to view benchmark
|
It seems that the update of the Test262 submodule is breaking this, probably due to tc39/test262@56ca8ad |
Can you make it so that there's a way to tell apart tests that were panicking but now pass and tests that were panicking but now fail? |
Something that can be done is to consider a Panic -> Passed a normal "fixed" test. In the list, it will show that it was panicking before. |
I think we still want to know if a test that previously panicked now fails, since that's an improvement. Though if we get to zero panics and make sure to not merge anything that adds panics, we might not see this very often. |
Yes, the idea would be that if a "Panic" goes to "Pass", it will be considered a "new passing test", but if it goes from "panic" to "Fail", then it would be considered a "panic fix". |
Benchmark for ec781a0Click to view benchmark
|
Benchmark for 9297a37Click to view benchmark
|
Benchmark for 9d1243bClick to view benchmark
|
This is ready for review. The extra panic seems this panic that happens only "sometimes". I'm unable to reproduce it locally. |
Previously, if a panic was fixed and it was now failing, it would be considered as a "new failure". This considers it a panic fix.