- 
                Notifications
    
You must be signed in to change notification settings  - Fork 107
 
Open
Description
Describe the bug
The conflicting-index-deps test fails under 32-bit architectures including x86, armv7 and armhf:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot file: package/tests/snapshots/integration__package__tests__integration__inputs__path__conflicting-index-deps__Nickel-pkg.ncl.snap
Snapshot: package/tests/integration/inputs/path/conflicting-index-deps/Nickel-pkg.ncl
Source: package/tests/integration.rs:266
────────────────────────────────────────────────────────────────────────────────
test package/tests/integration/inputs/path/path-to-index-dep/Nickel-pkg.ncl               ... ok
Expression: e.to_string()
────────────────────────────────────────────────────────────────────────────────
-old snapshot
+new results
────────────┬───────────────────────────────────────────────────────────────────
    1     1 │ package version resolution failed:
    2       │-Because 'Path <filtered> depends on github:example/leaf 0.1.0 and top-level package 0.1.0 depends on 'Path <filtered> top-level package 0.1.0 depends on github:example/leaf 0.1.0.
    3       │-And because top-level package 0.1.0 depends on github:example/leaf 0.1.1, top-level package 0.1.0 is forbidden.
          2 │+Because 'Path <filtered> depends on github:example/leaf 0.1.0 and top-level package 0.1.0 depends on github:example/leaf 0.1.1, top-level package 0.1.0, 'Path <filtered> * are incompatible.
          3 │+And because top-level package 0.1.0 depends on 'Path <filtered> top-level package 0.1.0 is forbidden.
────────────┴───────────────────────────────────────────────────────────────────
Stopped on the first failure. Run `cargo insta test` to run all snapshots.
thread '<unnamed>' panicked at /home/buildozer/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/insta-1.43.2/src/runtime.rs:694:13:
snapshot assertion for 'package/tests/integration/inputs/path/conflicting-index-deps/Nickel-pkg.ncl' failed in line 266
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test package/tests/integration/inputs/path/conflicting-index-deps/Nickel-pkg.ncl          ... FAILED
Already have a cache entry at "/tmp/.tmpxu7Ted/cache_dir/git-packages/44b1c226afdc6220892c242f6b05c9c654aa6065/"
test package/tests/integration/inputs/path/duplicate-path/Nickel-pkg.ncl                  ... ok
test package/tests/integration/inputs/path/git-path-dep/Nickel-pkg.ncl                    ... ok
failures:
---- package/tests/integration/inputs/path/conflicting-index-deps/Nickel-pkg.ncl ----
test panicked: snapshot assertion for 'package/tests/integration/inputs/path/conflicting-index-deps/Nickel-pkg.ncl' failed in line 266
failures:
    package/tests/integration/inputs/path/conflicting-index-deps/Nickel-pkg.ncl
test result: FAILED. 14 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.32s
error: test failed, to rerun pass `-p nickel-lang-package --test integration`
To Reproduce
Build the package and run tests on 32-bit arch
Expected behavior
The test should pass
Environment
- OS name + version: Alpine 3.22
 - Version of the code: 1.13.0
 
Additional context
I don't think this is limited to Alpine. Running cargo insta review on x86 arch generates an inverse snapshot that fails on 64-bit archs. I suspect this is a possible bug in the pubgrub crate, can anyone confirm here before I open an issue with pubgrub maintainers?
Metadata
Metadata
Assignees
Labels
No labels