-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
More stage1 test coverage #15879
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
More stage1 test coverage #15879
Conversation
2bccce5
to
f76230c
Compare
a6dfc36
to
0c95f48
Compare
0c95f48
to
7a30152
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work. You mind doing one last rebase and then I'll mark this as auto-merge?
7a30152
to
c66b823
Compare
c66b823
to
86f573c
Compare
20a2134
to
2a4dce9
Compare
I'm pretty sure I didn't change anything that would cause this new failure that previously didn't happen:
Pretty sure all I did was resolve the conflict and rebase on master/the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I did not take as close a look at the new test cases last time as I should have.
Please use panics instead of illegal behavior (i.e. assert
) so that the tests are meaningful in safety-off optimization modes as well.
Also please use behavior tests where possible instead of run test cases.
Oh, that is very true. I must've just taken that idea from other tests without thinking about it enough. It's also very good to know that behavior tests are in fact preferable. |
a191148
to
9460e82
Compare
0eb2fad
to
6e65275
Compare
Interesting. This has also not previously happened before the rebase. Anyway, AFAIU the zig downloads are broken right now so I'm going to wait till I can get the latest master from the download page. |
8bd381e
to
7b518d5
Compare
I'm going to try limiting tests that I think might have to do with the failure to linux-x86_64 for now. |
7b518d5
to
769531f
Compare
Vectors are a likely culprit: #13782 |
769531f
to
39e2849
Compare
Thanks! That helps a lot. |
39e2849
to
ad1a9a8
Compare
ad1a9a8
to
c006b19
Compare
c006b19
to
adf0718
Compare
No description provided.