Skip to content

Update std and test to newest crates.io versions #143004

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SciMind2460
Copy link

Just some updates to the Cargo.toml of std and test.

@rustbot
Copy link
Collaborator

rustbot commented Jun 25, 2025

r? @thomcc

rustbot has assigned @thomcc.
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 S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Jun 25, 2025
@rust-log-analyzer
Copy link
Collaborator

The job mingw-check-tidy failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
fmt check
fmt: checked 6122 files
tidy check

thread 'deps (.)' panicked at src/tools/tidy/src/deps.rs:597:24:
cmd.exec() failed with `cargo metadata` exited with an error:     Updating crates.io index
error: the lock file /checkout/library/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at src/tools/tidy/src/main.rs:64:49:
called `Result::unwrap()` on an `Err` value: Any { .. }
Command has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:00:49
  local time: Wed Jun 25 07:04:50 UTC 2025
  network time: Wed, 25 Jun 2025 07:04:50 GMT
##[error]Process completed with exit code 1.
Post job cleanup.

@SciMind2460 SciMind2460 reopened this Jun 25, 2025
@rust-log-analyzer
Copy link
Collaborator

The job mingw-check-tidy failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
fmt check
fmt: checked 6123 files
tidy check

thread 'deps (.)' panicked at src/tools/tidy/src/deps.rs:598:24:
cmd.exec() failed with `cargo metadata` exited with an error:     Updating crates.io index
error: the lock file /checkout/library/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at src/tools/tidy/src/main.rs:64:49:
called `Result::unwrap()` on an `Err` value: Any { .. }
Command has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:00:48
  local time: Wed Jun 25 12:50:58 UTC 2025
  network time: Wed, 25 Jun 2025 12:50:58 GMT
##[error]Process completed with exit code 1.
Post job cleanup.


[target.x86_64-fortanix-unknown-sgx.dependencies]
fortanix-sgx-abi = { version = "0.5.0", features = [
fortanix-sgx-abi = { version = "0.6.0", features = [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you actually tests that this still works?

'rustc-dep-of-std',
], public = true }

[target.'cfg(target_os = "wasi")'.dependencies]
wasi = { version = "0.11.0", features = [
wasi = { version = "0.14.2+wasi-0.2.4", features = [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

@bjorn3
Copy link
Member

bjorn3 commented Jun 25, 2025

Several of these already use the latest version in Cargo.lock.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. 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.

5 participants