[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#985725: marked as done (slurm-wlm: flaky autopkgtest: srun: Required node not available (down, drained or reserved))

Your message dated Thu, 31 Mar 2022 13:55:01 +0200
with message-id <YkWWlcslg8vI8X09@fuorigrotta.fritz.box>
and subject line Re: Bug#985725: slurm-wlm: flaky autopkgtest: srun: Required node not available (down, drained or reserved)
has caused the Debian Bug report #985725,
regarding slurm-wlm: flaky autopkgtest: srun: Required node not available (down, drained or reserved)
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 owner@bugs.debian.org
immediately.)


-- 
985725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985725
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: slurm-wlm
Version: 20.11.4-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed it fails regularly on
all architectures I checked. I have copied some of the output below. Can
you please look into it and fix it? Either the output to stderr is
actually OK, then a allow-stderr restriction is enough to fix the issue,
or it's actually showing that there's a real issue that needs fixing (as
the test itself doesn't fail).

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.

Paul

https://ci.debian.net/packages/s/slurm-wlm/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/s/slurm-wlm/11213446/log.gz

autopkgtest [09:10:26]: test srun: [-----------------------
PARTITION AVAIL  TIMELIMIT  NODES  STATE NODELIST
test*        up   infinite      1    unk localhost
NODELIST   NODES PARTITION STATE
localhost      1     test* unk
srun: Required node not available (down, drained or reserved)
srun: job 2 queued and waiting for resources
srun: job 2 has been allocated resources
autopkgtest [09:10:31]: test srun: -----------------------]
autopkgtest [09:10:31]: test srun:  - - - - - - - - - - results - - - -
- - - - - -
srun                 FAIL stderr: srun: Required node not available
(down, drained or reserved)
autopkgtest [09:10:31]: test srun:  - - - - - - - - - - stderr - - - - -
- - - - -

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Package: slurm-wlm
Version: 20.11.5-1

Hi Paul,

On Mon, Mar 22, 2021 at 07:35:00PM +0100, Paul Gevers wrote:
> Your package has an autopkgtest, great. However, I looked into
> the history of your autopkgtest [1] and I noticed it fails regularly on
> all architectures I checked. I have copied some of the output below. Can
> you please look into it and fix it?

I was not sure if [1] would have fix the problem, but it looks like it
did [2].

> 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.

Sorry to read that, at the time I didn't know about these tests.

Best regards,

[1] https://salsa.debian.org/hpc-team/slurm-wlm/-/commit/c8cc263515f62cbbb579df4b41e09565e60a2628
[2] https://ci.debian.net/packages/s/slurm-wlm/testing/amd64/

-- 
Gennaro Oliva

--- End Message ---
Reply to: