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

dep_kinds_filtering::tests::test_dep_kind* tests fail on ppc64le, armv7 and armhf #118

Open
WhyNotHugo opened this issue Feb 19, 2025 · 4 comments

Comments

@WhyNotHugo
Copy link
Contributor

Upgrading cargo-vendor-filterer to from 0.5.9 to 0.5.17, dep_kinds_filtering::tests::test_dep_kind_dev_only, dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build and dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev fail on ppc64le, armv7 and armhf.

I've come across this by upgrading the downstream Alpine package.

---- dep_kinds_filtering::tests::test_dep_kind_dev_only stdout ----
thread 'dep_kinds_filtering::tests::test_dep_kind_dev_only' panicked at src/dep_kinds_filtering.rs:180:23:
Got error: Failed to execute cargo tree: "error: failed to run `rustc` to learn about target-specific information\n\nCaused by:\n  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -Clink-arg=-Wl,-z,pack-relative-relocs --target x86_64-pc-windows-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)\n  --- stderr\n  error: could not create LLVM TargetMachine for triple: x86_64-pc-windows-gnu: No available targets are compatible with triple \"x86_64-pc-windows-gnu\"\n\n"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---- dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev stdout ----
thread 'dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev' panicked at src/dep_kinds_filtering.rs:259:18:
One of get_required_packages() calls failed
---- dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build stdout ----
thread 'dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build' panicked at src/dep_kinds_filtering.rs:229:18:
One of get_required_packages() calls failed
failures:
    dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev
    dep_kinds_filtering::tests::test_dep_kind_dev_only
    dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build
test result: FAILED. 7 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.27s

Full build output for ppcle64, armv7 and armhf.

@WhyNotHugo WhyNotHugo changed the title dep_kinds_filtering::tests::test_dep_kind* test fail on ppc64le, armv7 and armhf dep_kinds_filtering::tests::test_dep_kind* tests fail on ppc64le, armv7 and armhf Feb 19, 2025
@WhyNotHugo
Copy link
Contributor Author

I don't see an obvious pattern in the targets which are failing:

  • Two are 32bit, but x86 works fine.
  • Two are arm, but aarch64 works fine.
  • One is 64 bit.

Unless I've misread something, the test failure is the exact same on all three platforms.

@cgwalters
Copy link
Member

I don't know what the problem is, but #119 should make it easier to debug. Can you try that patch?

@WhyNotHugo
Copy link
Contributor Author

Here's the output for armhf:

---- dep_kinds_filtering::tests::test_dep_kind_dev_only stdout ----
thread 'dep_kinds_filtering::tests::test_dep_kind_dev_only' panicked at src/dep_kinds_filtering.rs:178:10:
called `Result::unwrap()` on an `Err` value: Failed to execute cargo tree: "error: failed to run `rustc` to learn about target-specific information\n\nCaused by:\n  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --target x86_64-pc-windows-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)\n  --- stderr\n  error: could not create LLVM TargetMachine for triple: x86_64-pc-windows-gnu: No available targets are compatible with triple \"x86_64-pc-windows-gnu\"\n\n"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---- dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build stdout ----
thread 'dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build' panicked at src/dep_kinds_filtering.rs:208:10:
called `Result::unwrap()` on an `Err` value: Failed to execute cargo tree: "error: failed to run `rustc` to learn about target-specific information\n\nCaused by:\n  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --target x86_64-pc-windows-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)\n  --- stderr\n  error: could not create LLVM TargetMachine for triple: x86_64-pc-windows-gnu: No available targets are compatible with triple \"x86_64-pc-windows-gnu\"\n\n"
---- dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev stdout ----
thread 'dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev' panicked at src/dep_kinds_filtering.rs:239:10:
called `Result::unwrap()` on an `Err` value: Failed to execute cargo tree: "error: failed to run `rustc` to learn about target-specific information\n\nCaused by:\n  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --target x86_64-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)\n  --- stderr\n  error: could not create LLVM TargetMachine for triple: x86_64-unknown-linux-gnu: No available targets are compatible with triple \"x86_64-unknown-linux-gnu\"\n\n"
failures:
    dep_kinds_filtering::tests::test_dep_kind_build_vs_no_dev
    dep_kinds_filtering::tests::test_dep_kind_dev_only
    dep_kinds_filtering::tests::test_dep_kind_normal_vs_no_build
test result: FAILED. 7 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.15s

@WhyNotHugo
Copy link
Contributor Author

I think that LLVM indicates that it doesn't know target x86_64-pc-windows-gnu? I'm not sure that I'm interpreting this correctly.

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

No branches or pull requests

2 participants