Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1242418 > unrolled thread
| Started by | Paul Gevers <elbrus@debian.org> |
|---|---|
| First post | 2025-04-17 10:30 +0200 |
| Last post | 2025-04-17 13:00 +0200 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.debian.bugs.dist
Bug#1103406: ogdi-dfsg: flaky autopkgtest on arm64 Paul Gevers <elbrus@debian.org> - 2025-04-17 10:30 +0200
Bug#1103406: ogdi-dfsg: flaky autopkgtest on arm64 Paul Gevers <elbrus@debian.org> - 2025-04-17 13:00 +0200
| From | Paul Gevers <elbrus@debian.org> |
|---|---|
| Date | 2025-04-17 10:30 +0200 |
| Subject | Bug#1103406: ogdi-dfsg: flaky autopkgtest on arm64 |
| Message-ID | <KCsNb-e8uF-3@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Source: ogdi-dfsg Version: 4.1.1+ds-5 Severity: serious User: debian-ci@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on arm64, while other architectures seem fine. Unfortunately, the test doesn't produce any output, so I can't give any advice on the failure based on that. I noticed that this test downloads some data from the internet, maybe adding a timeout to wget and some debugging info might help identify problems related to that. Maybe having a retry in case of network issues might be prudent. The arm64 ci.d.n hosts are located in China (as are the loong64 and riscv64 hosts, which don't seem to suffer (or less)). 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 https://ci.debian.net/packages/o/ogdi-dfsg/testing/arm64/ https://ci.debian.net/packages/o/ogdi-dfsg/testing/arm64/58850275/ 54s autopkgtest [19:08:10]: test ogdi-bin: [----------------------- 2878s autopkgtest [19:55:14]: test ogdi-bin: -----------------------] ▾ test ogdi-bin: test results 2878s autopkgtest [19:55:14]: test ogdi-bin: - - - - - - - - - - results - - - - - - - - - - 2878s ogdi-bin FAIL non-zero exit status 4
[toc] | [next] | [standalone]
| From | Paul Gevers <elbrus@debian.org> |
|---|---|
| Date | 2025-04-17 13:00 +0200 |
| Message-ID | <KCv8l-e9SL-1@gated-at.bofh.it> |
| In reply to | #1242418 |
[Multipart message — attachments visible in raw view] — view raw
Hi, On 17-04-2025 12:49, Sebastiaan Couwenberg wrote: > On 4/17/25 12:16 PM, Paul Gevers wrote: >> To avoid having to do this on the package side, I (ci.d.n maintainer >> hat on) could add your package to the ci.d.n reject_list > That doesn't sound like a good idea because then two people need to do > work to re-enable arm64 again. My proposal here was that you don't do it, but I do it *instead*. I totally agree it doesn't make sense we do it both. Paul
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web