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.

Sign up for GitHub

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

Jump to bottom

Spurious failure in test_inherit_env #55503

Closed
kennytm opened this issue Oct 30, 2018 · 1 comment
Closed

Spurious failure in test_inherit_env #55503

kennytm opened this issue Oct 30, 2018 · 1 comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@kennytm
Copy link
Member

kennytm commented Oct 30, 2018

Symptom: the test process::tests::test_inherit_env failed even if the PR doesn't touch this part of the standard library.

[01:56:52] test process::tests::test_inherit_env ... FAILED
...
[01:56:52] thread '<unnamed>' panicked at 'output doesn't contain `RUN_TEST_NEW_ENV2=456`
...

Previous instances:

It is known that this test had a race condition, and the fix #42795 wasn't merged.
@kennytm kennytm added A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-bug Category: This is a bug. labels Oct 30, 2018
@Enselic
Copy link
Member

Enselic commented Jul 25, 2023

This issue can be closed, because the test was removed in d1cd4e8

@Dylan-DPC Dylan-DPC closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kennytm @Enselic @Dylan-DPC