tests time out on arm64 and armhf

[Michael Hudson-Doyle]

[impact]
The tests, both during build and in autopkgtest, tend to time out on slow machines (e.g. when all builders are busy). The autopkgtest failures in particular interfere with updating Python in Bionic and Cosmic.

[test case]
The builds and autopkgtests must complete successfully without stomping on the retry button.

[regression potential]
It's just setting an environment variable during build and autopkgtest which has no impact on the built packages so there is no regression potential.

[Steve Langasek (vorlon)]

Hello Michael, or anyone else affected,

Accepted python-tornado into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-tornado/5.0.2-1.0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Brian Murray (brian-murray)]

I was looking at the SRU of this for bionic and noticed that the cosmic SRU still fails to build, so accepting it in Bionic seems premature.

[Brian Murray (brian-murray)]

An upload of python-tornado to bionic-proposed has been rejected from the upload queue for the following reason: "I'm rejecting this because the same changes failed to build for cosmic.".

[Michael Hudson-Doyle (mwhudson)]

Turns out the package in release ftbfs too. I guess I get to fix that too!

[Łukasz Zemczak (sil2100)]

Any movement on this? The package has been around in -proposed for quite a long time. I'd say if this doesn't get a follow up fix in the nearest weeks, I'll drop it from -proposed.

[Michael Hudson-Doyle (mwhudson)]

No, no progress on this. The package ftbfs in release in both bionic and cosmic, in ways that are not obviously the same. I'm not very inclined to fix cosmic but I guess fixing bionic should be slightly higher priority.

[Gianfranco Costamagna (costamagnagianfranco)]

I added some hints on
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/34
and
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/35
for a possible fix and reasons for the failures.
I hope this helps!

[Andreas Hasenack (ahasenack)]

Indeed, just export ASYNC_TEST_TIMEOUT=30 doesn't help with the bionic + proposed build.

[Andreas Hasenack (ahasenack)]

Also quickly tried https://github.com/tornadoweb/tornado/commit/00675409071b41650a5cd6894cafd921d16085ae but that didn't help on its own.

[Steve Langasek (vorlon)]

The version of python-tornado in the proposed pocket of Cosmic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.

[Bryce Harrington (bryce)]

Dropping the Cosmic task since Cosmic is now EOL. The bionic task is still viable if someone sorts out reproducibility.