Hi Jeff,
On 03-10-2022 13:39, Jeff wrote:
This morning, I see that for s390x in testing, there was a timeout and
failure (both in 380_cancel_user_defined_with_pids), as well as two passes:
https://ci.debian.net/packages/g/gscan2pdf/testing/s390x/
Ends with:
"""
"Too many open files" at t/380
This morning, I see that for s390x in testing, there was a timeout and
failure (both in 380_cancel_user_defined_with_pids), as well as two passes:
https://ci.debian.net/packages/g/gscan2pdf/testing/s390x/
armel had a failure that was unrelated to gscan2pdf:
https://ci.debian.net/data/autopkgte
This is proving hard to nail down.
The examples you give all time-out on different tests.
I've never had a timeout problem whilst testing interactively or in a
local schroot.
I see the status on the runs that time out is always "tmpfail". What
does tmpfail mean? How is the status determined?
Source: gscan2pdf
Version: 2.12.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package on s390x
because it was showing up on our alert page [1]. I noticed that there
were several runs that took 27h be
4 matches
Mail list logo
