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

Pipelines 32bit/64bit might not be set up identically #5079

Open
dbischof90 opened this issue Oct 6, 2022 · 1 comment
Open

Pipelines 32bit/64bit might not be set up identically #5079

dbischof90 opened this issue Oct 6, 2022 · 1 comment
Labels
A-ci Area: The continuous integration setup

Comments

@dbischof90
Copy link
Contributor

I ran the pipelines this morning for a commit and found a missing import in a doc-test.
This was flagged in the 64bit test run, did however pass in the 32bit run.
Upon inspection, I saw that in the 32bit setup a much smaller number of document tests are run:

[...]
test single_immediate_delay ... ok
test single_short_delay ... ok
test multi_delay_at_start ... ok
test result: ok. 30 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.03s
     Running tests/udp.rs (target/i686-unknown-freebsd/debug/deps/udp-92286984c3521068)
running 3 tests
test send_framed_byte_codec ... ok
test framed_half ... ok
test send_framed_lines_codec ... ok
test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
   Doc-tests tokio-macros
running 28 tests
test src/lib.rs - main (line 109) ... ok
test src/lib.rs - main (line 100) ... ok
test src/lib.rs - main (line 123) ... ok
[...]

... whereas for the 64bit setup we have:

[...]
test single_immediate_delay ... ok
test single_short_delay ... ok
test multi_delay_at_start ... ok
test result: ok. 30 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.06s
     Running tests/udp.rs (target/debug/deps/udp-30080e20dad4d502)
running 3 tests
test send_framed_byte_codec ... ok
test framed_half ... ok
test send_framed_lines_codec ... ok
test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
   Doc-tests tests-build
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
   Doc-tests tests-integration
running 1 test
test src/lib.rs - (line 64) - compile ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.05s
   Doc-tests tokio
running 627 tests
test src/fs/copy.rs - fs::copy::copy (line 14) - compile ... ok
test src/fs/canonicalize.rs - fs::canonicalize::canonicalize (line 38) - compile ... ok
test src/fs/create_dir.rs - fs::create_dir::create_dir (line 39) - compile ... ok
test src/fs/create_dir_all.rs - fs::create_dir_all::create_dir_all (line 41) - compile ... ok
[...]

Links to the cirrus logs:
https://cirrus-ci.com/task/6628174892105728
https://cirrus-ci.com/task/5713381217796096

Is there a reason for this?

@Darksonn Darksonn added the A-ci Area: The continuous integration setup label Oct 6, 2022
@Darksonn
Copy link
Contributor

Darksonn commented Oct 6, 2022

No, I'm not sure why this is. It's not intentional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ci Area: The continuous integration setup
Projects
None yet
Development

No branches or pull requests

2 participants