Skip to content

Conversation

dpaoliello
Copy link
Contributor

Attempting to bisect error in #121854 (comment)

@rustbot
Copy link
Collaborator

rustbot commented Mar 1, 2024

r? @Kobzol

rustbot has assigned @Kobzol.
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-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Mar 1, 2024
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer
Copy link
Collaborator

The job arm-android failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
GITHUB_ACTION=__run_7
GITHUB_ACTIONS=true
GITHUB_ACTION_REF=
GITHUB_ACTION_REPOSITORY=
GITHUB_ACTOR=dpaoliello
GITHUB_API_URL=https://api.github.com
GITHUB_BASE_REF=master
GITHUB_ENV=/home/runner/work/_temp/_runner_file_commands/set_env_62f50ac9-f7db-4a43-af5a-5b2e4a54d3fe
GITHUB_EVENT_NAME=pull_request
---
GITHUB_SERVER_URL=https://github.com
GITHUB_SHA=c266c9202631dbd02b5dcb6f69a133de4a241bd7
GITHUB_STATE=/home/runner/work/_temp/_runner_file_commands/save_state_62f50ac9-f7db-4a43-af5a-5b2e4a54d3fe
GITHUB_STEP_SUMMARY=/home/runner/work/_temp/_runner_file_commands/step_summary_62f50ac9-f7db-4a43-af5a-5b2e4a54d3fe
GITHUB_TRIGGERING_ACTOR=dpaoliello
GITHUB_WORKFLOW_REF=rust-lang/rust/.github/workflows/ci.yml@refs/pull/121873/merge
GITHUB_WORKFLOW_SHA=c266c9202631dbd02b5dcb6f69a133de4a241bd7
GITHUB_WORKSPACE=/home/runner/work/rust/rust
GOROOT_1_20_X64=/opt/hostedtoolcache/go/1.20.14/x64
---
   Compiling std v0.0.0 (/checkout/library/std)
error: unexpected `cfg` condition value: `miri-test-libstd`
  --> library/core/src/lib.rs:63:16
   |
63 | #![cfg(any(not(feature = "miri-test-libstd"), test, doctest))]
   |
   |
   = note: expected values for `feature` are: `debug_refcell`, `panic_immediate_abort`
   = help: consider adding `miri-test-libstd` as a feature in `Cargo.toml`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
   = note: `-D unexpected-cfgs` implied by `-D warnings`
   = help: to override `-D warnings` add `#[allow(unexpected_cfgs)]`
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/num/mod.rs:30:11
   |
   |
30 | #[cfg(not(no_fp_fmt_parse))]
   |
   |
   = help: expected names are: `bootstrap`, `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `unix`, `windows`
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/num/mod.rs:32:11
   |
   |
32 | #[cfg(not(no_fp_fmt_parse))]
   |
   |
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/num/mod.rs:34:11
   |
   |
34 | #[cfg(not(no_fp_fmt_parse))]
   |
   |
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/num/mod.rs:36:11
   |
   |
36 | #[cfg(not(no_fp_fmt_parse))]
   |
   |
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/num/mod.rs:58:11
   |
   |
58 | #[cfg(not(no_fp_fmt_parse))]
   |
   |
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition value: `spirv`
   --> library/core/src/mem/mod.rs:733:19
    |
    |
733 |     #[cfg(not(any(target_arch = "spirv")))]
    |
    |
    = note: expected values for `target_arch` are: `aarch64`, `arm`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`
    = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/fmt/mod.rs:16:11
   |
   |
16 | #[cfg(not(no_fp_fmt_parse))]
   |
   |
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `no_fp_fmt_parse`
  --> library/core/src/fmt/mod.rs:18:7
   |
   |
18 | #[cfg(no_fp_fmt_parse)]
   |
   |
   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(no_fp_fmt_parse)");` to the top of a `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `stdarch_intel_sde`
   --> library/core/src/../../stdarch/crates/core_arch/src/x86/mod.rs:801:11
    |
    |
801 | #[cfg(not(stdarch_intel_sde))]
    |
    |
    = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(stdarch_intel_sde)");` to the top of a `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `stdarch_intel_sde`
   --> library/core/src/../../stdarch/crates/core_arch/src/x86/mod.rs:803:11
    |
    |
803 | #[cfg(not(stdarch_intel_sde))]
    |
    |
    = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(stdarch_intel_sde)");` to the top of a `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `stdarch_intel_sde`
   --> library/core/src/../../stdarch/crates/core_arch/src/x86/mod.rs:807:11
    |
    |
807 | #[cfg(not(stdarch_intel_sde))]
    |
    |
    = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(stdarch_intel_sde)");` to the top of a `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition name: `stdarch_intel_sde`
   --> library/core/src/../../stdarch/crates/core_arch/src/x86/mod.rs:809:11
    |
    |
809 | #[cfg(not(stdarch_intel_sde))]
    |
    |
    = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(stdarch_intel_sde)");` to the top of a `build.rs`
    = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: unexpected `cfg` condition value: `all_lane_counts`
  --> library/core/src/../../portable-simd/crates/core_simd/src/lane_count.rs:37:7
   |
37 | #[cfg(feature = "all_lane_counts")]
37 | #[cfg(feature = "all_lane_counts")]
   |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: expected values for `feature` are: `debug_refcell`, `panic_immediate_abort`
   = help: consider adding `all_lane_counts` as a feature in `Cargo.toml`
   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
error: could not compile `core` (lib) due to 14 previous errors
warning: build failed, waiting for other jobs to finish...
Build completed unsuccessfully in 0:00:29
  local time: Fri Mar  1 22:13:32 UTC 2024

@dpaoliello dpaoliello closed this Mar 1, 2024
@dpaoliello dpaoliello deleted the cc83 branch March 1, 2024 22:33
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-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants