On Mon, Apr 29, 2019 at 02:55:23PM +0200, Miro Hrončok wrote: > There is no way to see what's going on: > https://pagure.io/fedora-ci/general/issue/2 (8 months old) Seems to be acked and known. This is not a small/easy fix though > There is no way to reproduce+debug easily: > https://pagure.io/fedora-ci/general/issue/4 (8 months old) Seems to have been worked on and has stalled a little bit. Let's see if we can poke it. > There is no way to see why it errored: > https://pagure.io/fedora-ci/general/issue/43 (1 month old) While there was some discussion it seems the actual issue is still valid. This also may not be an easy fix as wrapping errors is always a complicated task. > There is no way to see when it errored: > https://pagure.io/fedora-ci/general/issue/49 (fresh) This was opened last Friday, we can give them a little more time to provide feedback :) > There is no way to rely on CI not erroring by random reason: > https://pagure.io/fedora-ci/general/issue/44 (1 month old) Not much input on this one as well :( Thanks for your tickets, I'll try to get them some attention. Pierre _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
