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

Ignore some more crates #722

Merged
merged 4 commits into from
Mar 20, 2024
Merged

Ignore some more crates #722

merged 4 commits into from
Mar 20, 2024

Conversation

saethlin
Copy link
Member

@saethlin saethlin commented Mar 9, 2024

Adding all the spurious failures I identified in rust-lang/rust#121282 (comment)

I'm also not sure what blacklist.md is for, but it hasn't been updated in 6 years so I imagine it's not important.

@Mark-Simulacrum
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Mar 18, 2024

📌 Commit 54ffaca has been approved by Mark-Simulacrum

It is now in the queue for this repository.

bors added a commit that referenced this pull request Mar 18, 2024
Ignore some more crates

Adding all the spurious failures I identified in rust-lang/rust#121282 (comment)

I'm also not sure what `blacklist.md` is for, but it hasn't been updated in 6 years so I imagine it's not important.
@bors
Copy link
Contributor

bors commented Mar 18, 2024

⌛ Testing commit 54ffaca with merge d6e458f...

@bors
Copy link
Contributor

bors commented Mar 18, 2024

💔 Test failed - checks-actions

@Kobzol
Copy link
Contributor

Kobzol commented Mar 20, 2024

@bors r=Mark-simulacrum

@bors
Copy link
Contributor

bors commented Mar 20, 2024

📌 Commit b7bc3d4 has been approved by Mark-simulacrum

It is now in the queue for this repository.

@bors
Copy link
Contributor

bors commented Mar 20, 2024

⌛ Testing commit b7bc3d4 with merge 683b67f...

bors added a commit that referenced this pull request Mar 20, 2024
Ignore some more crates

Adding all the spurious failures I identified in rust-lang/rust#121282 (comment)

I'm also not sure what `blacklist.md` is for, but it hasn't been updated in 6 years so I imagine it's not important.
@bors
Copy link
Contributor

bors commented Mar 20, 2024

💔 Test failed - checks-actions

@saethlin
Copy link
Member Author

Strange. I could have sworn I had the test suite passing with --ignored last time but indeed when I tried to run it again, I got failures.

In any case, I've applied the blessing as advised by the failing tests and it passes locally now.

@Kobzol
Copy link
Contributor

Kobzol commented Mar 20, 2024

@bors r=Mark-simulacrum

@bors
Copy link
Contributor

bors commented Mar 20, 2024

📌 Commit 0cd58a7 has been approved by Mark-simulacrum

It is now in the queue for this repository.

@bors
Copy link
Contributor

bors commented Mar 20, 2024

⌛ Testing commit 0cd58a7 with merge de2da9d...

@bors
Copy link
Contributor

bors commented Mar 20, 2024

☀️ Test successful - checks-actions
Approved by: Mark-simulacrum
Pushing de2da9d to master...

@bors bors merged commit de2da9d into rust-lang:master Mar 20, 2024
3 checks passed
This was referenced Mar 20, 2024
@saethlin saethlin deleted the flaky-crates branch March 20, 2024 17:30
bors added a commit that referenced this pull request Mar 31, 2024
Forbid unprefixed SHAs for toolchains

This PR forbids unprefixed SHAs for toolchain arguments, to avoid crater hanging when they appear.

I'm not sure this is fully valid though: I don't know if SHAs could appear in a `Toolchain`'s name (and `RustwideToolchain::dist()`) without being an error 😓. This commonly happens with `rustup-toolchain-install-master` but I don't know if a similar situation could arise within common crater usage.

CI will surely fail: some of the used dependencies are broken on nightly right now, and clippy emits warnings -- both issues are fixed in #722.

<sub>(this is [for](rust-lang/rust#122230 (comment)) `@oli-obk` and [for](rust-lang/rust#122502 (comment)) `@compiler-errors)</sub>`
bors added a commit that referenced this pull request Mar 31, 2024
Forbid unprefixed SHAs for toolchains

This PR forbids unprefixed SHAs for toolchain arguments, to avoid crater hanging when they appear.

I'm not sure this is fully valid though: I don't know if SHAs could appear in a `Toolchain`'s name (and `RustwideToolchain::dist()`) without being an error 😓. This commonly happens with `rustup-toolchain-install-master` but I don't know if a similar situation could arise within common crater usage.

CI will surely fail: some of the used dependencies are broken on nightly right now, and clippy emits warnings -- both issues are fixed in #722.

<sub>(this is [for](rust-lang/rust#122230 (comment)) `@oli-obk` and [for](rust-lang/rust#122502 (comment)) `@compiler-errors)</sub>`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants