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?

The timeouts seem rare and even then something that has only recently started. Changes to gscan2pdf in the last year have only been cosmetic, and I wonder therefore if a dependency is causing this.

I see error messages such as:

AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

Which according to

https://gist.github.com/jeffcogswell/62395900725acef1c0a5a608f7eb7a05

Might be fixed with

  sudo apt install at-spi2-core

On the other hand, this seems very hacky, as these really shouldn't have anything to do with gscan2pdf - maybe a dependency, e.g. gtk+.

But these also occur in runs which pass, such as:

https://ci.debian.net/data/autopkgtest/stable/amd64/g/gscan2pdf/23364484/log.gz

I'd be grateful for any suggestions

Regards

Jeff

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to