Control: severity -1 normal
Control: retitle -1 src:autopkgtest: test_copy_timeout skipped because it's
dependent on speed of testbed
Control: tags -1 - pending
On Thu, 04 Apr 2024 at 10:08:29 +0200, Paul Gevers wrote:
> I looked at the results of the autopkgtest of your package. I noticed that
> it recently started to fail a lot on ppc64el.
On Thu, 04 Apr 2024 at 22:08:32 +0200, Paul Gevers wrote:
> The test is [copying] a huge file and expects the copy to
> fail because it should take longer. Well, with [/tmp on] tmpfs the
> autopktest inside
> the test passes and hence the outer test fails.
On Sun, 12 May 2024 at 08:59:18 +0200, Paul Gevers wrote:
> On 06-04-2024 9:58 p.m., Paul Gevers wrote:
> > Anyways, it looks like we could just lower the timeout to 1 second and
> > hope were fine for some time to come.
>
> No. 1 second is *too short* for the PodmanRunner.test_copy_timeout test on
> salsa. So I'll just disable the test for now.
This was done in 5.35, making this bug non-RC. I'm retitling it and
leaving it open to represent the technical debt of missing test-suite
coverage, but I'm not really seeing any good way to test this particular
corner case: it's difficult to trigger a timeout during copying on-demand
without making the test vulnerable to timing out for an unrelated reason.
If other maintainers don't think this is worth having a bug open for,
please close it.
smcv
