Your message dated Mon, 24 Jul 2023 04:09:05 +0200
with message-id <20230724020905.gd12...@beskar.mdcc.cx>
and subject line Re: Bug#1034348: at: autopkgtest regression on arm64
has caused the Debian Bug report #1034348,
regarding at: autopkgtest regression on arm64: Either at.20377 doesn't exist or
the content differs.
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.)
--
1034348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: at
Version: 3.2.5-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails on
arm(64|el|hf) since September 2022 (and slightly longer on s390x). Can
you please investigate the situation and fix it? I copied some of the
output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
https://ci.debian.net/data/autopkgtest/testing/arm64/a/at/32696040/log.gz
autopkgtest [01:12:17]: test basic-usage: [-----------------------
+ TMPFILE=at.20377
++ mktemp -d
+ WORKDIR=/tmp/tmp.7IsxZpWEJn
+ trap 'rm -rf /tmp/tmp.7IsxZpWEJn' 0 INT QUIT ABRT PIPE TERM
++ atq
++ wc -l
+ JOBS_BEFORE=0
+ at now + 1 minute
++ date
warning: commands will be executed using /bin/sh
+ echo 'echo Fri Apr 7 01:12:17 CST 2023 > /tmp/tmp.7IsxZpWEJn/at.20377'
job 1 at Fri Apr 7 01:13:00 2023
+ sleep 2
+ test -f at.20377
+ echo 'OK, at.20377 doesn'\''t exist yet; expected..'
OK, at.20377 doesn't exist yet; expected..
++ atq
++ wc -l
+ JOBS_AFTER=1
+ [[ 1 -eq 1 ]]
+ echo 'OK, 1 new queued job exists..'
+ sleep 58
OK, 1 new queued job exists..
+ grep -Fq UTC /tmp/tmp.7IsxZpWEJn/at.20377
+ echo 'Either at.20377 doesn'\''t exist or the content differs.'
+ exit 1
Either at.20377 doesn't exist or the content differs.
+ rm -rf /tmp/tmp.7IsxZpWEJn
autopkgtest [01:13:18]: test basic-usage: -----------------------]
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
Another happy at user here.
Jose M Calhariz <j...@calhariz.com> wrote:
> Hi, I believe my last update fixed the problem can someone double check?
That was at 3.2.5-2, right? Closing this bug: afaik nobody has been able to
reproduce the issue. Therefore better to close and see what happens next.
Please reopen if you feel this is not appropriate.
Thanks! Bye,
Joost
--- End Message ---
