Skip to content
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 flakiness in close_output test #8668

Merged
merged 1 commit into from
Aug 31, 2020

Conversation

alexcrichton
Copy link
Member

It looks like stdout/stderr can race as to which gets printed first, but
both are valid for this test.

Closes #8665

It looks like stdout/stderr can race as to which gets printed first, but
both are valid for this test.

Closes rust-lang#8665
@rust-highfive
Copy link

r? @ehuss

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 31, 2020
@ehuss
Copy link
Contributor

ehuss commented Aug 31, 2020

Thanks! Sorry this test has been so finicky.

For reference, this is likely caused by rust-lang/rust#72808. I don't fully understand that PR, but it seems plausible that the order would change if stdout is now block-buffered.

@bors r+

@bors
Copy link
Contributor

bors commented Aug 31, 2020

📌 Commit bf10871 has been approved by ehuss

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 31, 2020
@bors
Copy link
Contributor

bors commented Aug 31, 2020

⌛ Testing commit bf10871 with merge 126907a...

@alexcrichton
Copy link
Member Author

Oh wow that does look like a gnarly PR...

I think this was theoretically possible to happen previously as well, though. It's possible that Cargo read stdout first before stderr and passed it along, failing to write that and then later receiving stderr (or so I think). In any case seems fine either way.

@bors
Copy link
Contributor

bors commented Aug 31, 2020

☀️ Test successful - checks-actions
Approved by: ehuss
Pushing 126907a to master...

@bors bors merged commit 126907a into rust-lang:master Aug 31, 2020
bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 31, 2020
Update cargo

8 commits in 51b66125ba97d2906f461b3f4e0408f206299bb6..126907a7cfccbe93778530e6a6bbaa3adb6c515c
2020-08-19 20:22:52 +0000 to 2020-08-31 20:42:11 +0000
- Fix flakiness in close_output test (rust-lang/cargo#8668)
- Reload unstable table from config file in `reload_rooted_at` (rust-lang/cargo#8656)
- Bump to 0.49.0, update changelog (rust-lang/cargo#8659)
- Fix LTO with doctests. (rust-lang/cargo#8657)
- Add spaces after -C and -Z flags for consistency (rust-lang/cargo#8648)
- Fix cache_messages::rustdoc test broken on beta. (rust-lang/cargo#8653)
- fix: remove unnecessary allocations (rust-lang/cargo#8641)
- Fixed a spelling and some clippy warnings (rust-lang/cargo#8637)
@ehuss ehuss added this to the 1.48.0 milestone Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build::close_output occasionally fails on Rust CI
4 participants