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

Adjust memchr pinning and run cargo update #129624

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

tgross35
Copy link
Contributor

@tgross35 tgross35 commented Aug 26, 2024

try-job: x86_64-mingw

Supersedes #129538

@rustbot
Copy link
Collaborator

rustbot commented Aug 26, 2024

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Aug 26, 2024
@rustbot
Copy link
Collaborator

rustbot commented Aug 26, 2024

These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

@tgross35
Copy link
Contributor Author

Running a try job because of #127890

@bors try

@bors
Copy link
Contributor

bors commented Aug 26, 2024

⌛ Trying commit 95a0761 with merge fd4dc52...

bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 26, 2024
Adjust `memchr` pinning and run `cargo update`

try-job: x86_64-pc-windows-gnu
@rust-log-analyzer

This comment has been minimized.

@tgross35
Copy link
Contributor Author

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 26, 2024
Adjust `memchr` pinning and run `cargo update`

try-job: x86_64-mingw
@bors
Copy link
Contributor

bors commented Aug 26, 2024

⌛ Trying commit 95a0761 with merge bf3d3ef...

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Contributor

bors commented Aug 26, 2024

💔 Test failed - checks-actions

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 26, 2024
@tgross35
Copy link
Contributor Author

Hm. I assume this comes from stacker making a change that brings in windows-sys 0.36.1, which is quite a bit older than the other versions we use

@tgross35
Copy link
Contributor Author

@nagisa it looks like you maintain https://github.com/rust-lang/stacker, any clue if this is related?

@nagisa
Copy link
Member

nagisa commented Aug 26, 2024

Sounds plausible enough. There's already a PR that bumps it on stacker side, so you'll be able to check this soon enough.

tgross35 added a commit to tgross35/rust that referenced this pull request Aug 26, 2024
Ignore the root Cargo.lock for now becuase stacker's Windows dependency
may be problematic [1].

Link:
rust-lang#129624 (comment) [1]
@tgross35
Copy link
Contributor Author

Okay, I dropped doing a cargo update in the root repo. Let's try again.

@bors try

@bors
Copy link
Contributor

bors commented Aug 26, 2024

⌛ Trying commit 47c2f97 with merge 60d700d...

bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 26, 2024
Adjust `memchr` pinning and run `cargo update`

try-job: x86_64-mingw
@bors
Copy link
Contributor

bors commented Aug 27, 2024

☀️ Try build successful - checks-actions
Build commit: 60d700d (60d700d5439dd91cf6ad2fd0616f3eb6afe7fe4f)

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Sep 11, 2024
bors added a commit to rust-lang-ci/rust that referenced this pull request Sep 11, 2024
…crum

Adjust `memchr` pinning and run `cargo update`

try-job: x86_64-mingw
@bors
Copy link
Contributor

bors commented Sep 11, 2024

⌛ Testing commit 7f51490 with merge 3bc3fd9...

@rust-log-analyzer
Copy link
Collaborator

The job x86_64-msvc failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
warning: profiler_builtins@0.0.0: 1 warning generated.
[RUSTC-TIMING] corebenches test:true 59.847
[RUSTC-TIMING] coretests test:true 86.466
Build completed unsuccessfully in 0:53:57
make: *** [Makefile:106: ci-msvc-ps1] Error 1
  network time: Wed, 11 Sep 2024 10:51:06 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

@bors
Copy link
Contributor

bors commented Sep 11, 2024

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 11, 2024
@ChrisDenton
Copy link
Member

Maybe changing the lock file affects the cache in some way that makes this error more likely to be hit? It does seem incredibly frequent with this PR.

@tgross35
Copy link
Contributor Author

Yeah I don’t know why this is so weird, especially after your partial fix. When I’m back at a computer I’ll just try splitting it into a separate PR for each lockfile.

That is an interesting datapoint for the Windows CI issue if it seems like caching affects things.

@ChrisDenton
Copy link
Member

trying to see if this is still a problem, if so #130151 may eliminate one source of failure.

@ChrisDenton
Copy link
Member

@bors retry

@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 Sep 15, 2024
bors added a commit to rust-lang-ci/rust that referenced this pull request Sep 15, 2024
…crum

Adjust `memchr` pinning and run `cargo update`

try-job: x86_64-mingw
@bors
Copy link
Contributor

bors commented Sep 15, 2024

⌛ Testing commit 7f51490 with merge 0f066db...

@rust-log-analyzer
Copy link
Collaborator

The job x86_64-msvc failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
warning: profiler_builtins@0.0.0: 1 warning generated.
[RUSTC-TIMING] corebenches test:true 59.401
[RUSTC-TIMING] coretests test:true 86.157
Build completed unsuccessfully in 0:54:05
make: *** [Makefile:106: ci-msvc-ps1] Error 1
  network time: Sun, 15 Sep 2024 18:25:10 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

@bors
Copy link
Contributor

bors commented Sep 15, 2024

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 15, 2024
@ChrisDenton
Copy link
Member

Sorry for using this PR as a kind of canary but I'd like to try just one more time:

@bors retry

@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 Sep 18, 2024
bors added a commit to rust-lang-ci/rust that referenced this pull request Sep 18, 2024
…crum

Adjust `memchr` pinning and run `cargo update`

try-job: x86_64-mingw
@bors
Copy link
Contributor

bors commented Sep 18, 2024

⌛ Testing commit 7f51490 with merge 2794692...

@tgross35
Copy link
Contributor Author

tgross35 commented Sep 18, 2024

Sorry for using this PR as a kind of canary but I'd like to try just one more time:

Still haven’t gotten around to splitting this up, so be my guest as much as needed :)

@rust-log-analyzer
Copy link
Collaborator

The job x86_64-msvc failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
warning: profiler_builtins@0.0.0: 1 warning generated.
[RUSTC-TIMING] corebenches test:true 59.259
[RUSTC-TIMING] coretests test:true 85.327
Build completed unsuccessfully in 0:53:53
make: *** [Makefile:106: ci-msvc-ps1] Error 1
  network time: Wed, 18 Sep 2024 21:49:48 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

@bors
Copy link
Contributor

bors commented Sep 18, 2024

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 18, 2024
@workingjubilee
Copy link
Member

PR's haunted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants