Your message dated Sat, 16 Dec 2023 11:28:03 +0100
with message-id <20231216102803.46ic7x7rkdn7i4qo@bla>
and subject line Re: cargo: flaky autopkgtest:
has caused the Debian Bug report #1053424,
regarding cargo: flaky autopkgtest:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1053424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cargo
Version: 0.66.0+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed that it fails very often.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

E.g.
https://ci.debian.net/data/autopkgtest/testing/armhf/c/cargo/38257775/log.gz

401s failures:
401s     publish::api_error_200
401s     publish::api_other_error
401s
401s test result: FAILED. 2461 passed; 2 failed; 142 ignored; 0 measured; 0 filtered out; finished in 199.82s


https://ci.debian.net/data/autopkgtest/testing/amd64/c/cargo/38436894/log.gz

183s failures:
183s
183s ---- credential_process::publish stdout ----
183s running `/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/debug/cargo build` 183s running `/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/debug/cargo publish --no-verify --registry alternative -Z credential-process`
183s req: Request {
183s     url: Url {
183s         scheme: "http",
183s         cannot_be_a_base: false,
183s         username: "",
183s         password: None,
183s         host: Some(
183s             Ipv4(
183s                 127.0.0.1,
183s             ),
183s         ),
183s         port: Some(
183s             39447,
183s         ),
183s         path: "/api/v1/crates/new",
183s         query: None,
183s         fragment: None,
183s     },
183s     method: "put",
183s     authorization: Some(
183s         "sekrit",
183s     ),
183s     if_modified_since: None,
183s     if_none_match: None,
183s }
183s thread 'credential_process::publish' panicked at '
183s test failed running `/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/debug/cargo publish --no-verify --registry alternative -Z credential-process`
183s error: process exited with code 101 (expected 0)
183s --- stdout
183s
183s --- stderr
183s     Updating `alternative` index
183s Packaging foo v0.1.0 (/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/tmp/cit/t810/foo) 183s Uploading foo v0.1.0 (/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/tmp/cit/t810/foo)
183s error: failed to publish to registry at http://127.0.0.1:39447/
183s
183s Caused by:
183s   [55] Failed sending data to the peer (Send failure: Broken pipe)
183s ', tests/testsuite/credential_process.rs:203:10
183s note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
183s
183s
183s failures:
183s     credential_process::publish
183s
183s test result: FAILED. 2463 passed; 1 failed; 142 ignored; 0 measured; 0 filtered out; finished in 68.41s


https://ci.debian.net/data/autopkgtest/testing/i386/c/cargo/38284747/log.gz

2413s failures:
2413s
2413s ---- credential_process::publish stdout ----
2413s running `/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/debug/cargo build` 2413s running `/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/debug/cargo publish --no-verify --registry alternative -Z credential-process`
2413s req: Request {
2413s     url: Url {
2413s         scheme: "http",
2413s         cannot_be_a_base: false,
2413s         username: "",
2413s         password: None,
2413s         host: Some(
2413s             Ipv4(
2413s                 127.0.0.1,
2413s             ),
2413s         ),
2413s         port: Some(
2413s             44181,
2413s         ),
2413s         path: "/api/v1/crates/new",
2413s         query: None,
2413s         fragment: None,
2413s     },
2413s     method: "put",
2413s     authorization: Some(
2413s         "sekrit",
2413s     ),
2413s     if_modified_since: None,
2413s     if_none_match: None,
2413s }
2413s thread 'credential_process::publish' panicked at '
2413s test failed running `/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/debug/cargo publish --no-verify --registry alternative -Z credential-process`
2413s error: process exited with code 101 (expected 0)
2413s --- stdout
2413s
2413s --- stderr
2413s     Updating `alternative` index
2413s Packaging foo v0.1.0 (/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/tmp/cit/t810/foo) 2413s Uploading foo v0.1.0 (/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/tmp/cit/t810/foo)
2413s error: failed to publish to registry at http://127.0.0.1:44181/
2413s
2413s Caused by:
2413s   [55] Failed sending data to the peer (Send failure: Broken pipe)
2413s ', tests/testsuite/credential_process.rs:203:10
2413s note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2413s
2413s
2413s failures:
2413s     credential_process::publish
2413s
2413s test result: FAILED. 2462 passed; 1 failed; 142 ignored; 0 measured; 0 filtered out; finished in 1917.50s

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Version: 0.66.0+ds2-2
Version: 0.70.1+ds1-1~exp1

These versions (and subsequent ones) disable all flaky publish tests.

--- End Message ---

Reply via email to