-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fix integration tests #2 #11225
Fix integration tests #2 #11225
Conversation
r? @flip1995 (rustbot has picked a reviewer for you, use r? to override) |
lol |
@bors try |
[wip] Fix integration tests2 wip wap wup
💔 Test failed - checks-action_test |
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
591d277
to
501ae8c
Compare
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
[wip] Fix integration tests2 wip wap wup changelog: lolno
b84fb9b
to
ea5bb6d
Compare
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
…H to rustc sysroot
ea5bb6d
to
12b63f5
Compare
@bors try |
[wip] Fix integration tests2 wip wap wup changelog: lolno
☀️ Try build successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
should be ready now ✨ |
…, r=<try> test that we correctly detect panics in intergation tests Right now, this should pass as it is on top of #11225 but once I removed that from the pr, I should be able to see the failure. changelog: add test for integration tests
…, r=<try> test that we correctly detect panics in intergation tests Right now, this should pass as it is on top of #11225 but once I removed that from the pr, I should be able to see the failure. changelog: add test for integration tests
…, r=<try> test that we correctly detect panics in intergation tests Right now, this should pass as it is on top of #11225 but once I removed that from the pr, I should be able to see the failure. changelog: add test for integration tests
// debug: | ||
eprintln!("{stderr}"); |
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.
Is this actually a leftover for debugging, or do you want to have this in the tests? From the added --show-output
flag, I assume this is left here intentionally.
I think this could be quite useful, just want to make sure it wasn't forgotten about.
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.
No, this makes us print the clippy command stderr, but it would still be hidden by the testing harness by default, which is why we also need the other flag.
I think its nice to be verbose by default here so we can see what the problem is right away,in case there are any.
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.
I thought so. Makes sense, let's ship it
@bors delegate+ r=me with the comment addressed one way or another. Thank you for working on this and fixing it! ❤️ |
✌️ @matthiaskrgr, you can now approve this pull request! If @flip1995 told you to " |
@bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
…, r=<try> test that we correctly detect panics in intergation tests should be merged after #11225 changelog: add test for integration tests
…, r=flip1995 test that we correctly detect panics in intergation tests should be merged after #11225 changelog: add test for integration tests
fix integration tests.
It turned out that the following tests fail to build at all:
chalk, combine, stdarch and hyper.
This is often a problem of passing
--all-targets --all-features
, in case of combine though, outdated deps were to blame.I have opened tickets against combine and rustfmt
rust-lang/rustfmt#5859
Marwes/combine#357
should we just remove the other failing repos? :/
changelog: fix integration tests on ci