Special Cases III:
postgesql-rum æ armhf is one of the (unfortunate) flaky test env cases. Not related to the actual upload [1]. I have restarted it (the queue is too long to wait) and ran it locally (good).
Furthermore the very same PostgreSQL source code in Groovy has tested successfully already [2]
and the package itself is also the same F/G
postgresql-rum | 1.3.6-2 | focal/universe | source
postgresql-rum | 1.3.6-2 | groovy/universe | source
Therefore we can already assume that postgresql-rum will complete on a retry, but due to the 5k test queue that will take a while.
Special Cases III:
postgesql-rum æ armhf is one of the (unfortunate) flaky test env cases. Not related to the actual upload [1]. I have restarted it (the queue is too long to wait) and ran it locally (good).
Furthermore the very same PostgreSQL source code in Groovy has tested successfully already [2]
and the package itself is also the same F/G
postgresql-rum | 1.3.6-2 | focal/universe | source
postgresql-rum | 1.3.6-2 | groovy/universe | source
Therefore we can already assume that postgresql-rum will complete on a retry, but due to the 5k test queue that will take a while.
[1]: https:/ /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- focal-ci- train-ppa- service- 4333/focal/ armhf/p/ postgresql- rum/20201113_ 113310_ 58535@/ log.gz /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- groovy- ci-train- ppa-service- 4334/groovy/ armhf/p/ postgresql- rum/20201113_ 004959_ 07de2@/ log.gz
[2]: https:/