3301404157f52688f2a27511cdc1d2eb84c546ce
42518169e9b96982dd2036bb46b032a02ca5e95b
81360b37e9c4bdf2883acf896d2eec06b928bed2
0122822c86072882e6352bd6f10ec7e44e9266ce
abd56aaf71c0c278b8acb31c7b7ddf69ad3dfd16
This is the staging PR for: https://pagure.io/releng/compose-tracker/pull-request/56
This should hopefully fix/workaround: https://pagure.io/fedora-infrastructure/issue/11833
Awesome. Lets try it. ;)
Pull-Request has been merged by kevin
So, that didn't seem to work...
https://stg.pagure.io/releng/failed-composes/issue/4755 for example.
But perhaps I didn't deploy it correctly?
First one was kind of a blind patch based on your comments and looking at the code, there was an okay chance it would work but I was far from 100% ... to do another patch I probably need some way to run it and see what is going on etc.
How easy is it to download a logfile and run the code over it?
I'm not at all sure. ;( I would hope you could bypass the message trigger and just pass it a compose? But I don't know...
This is the staging PR for: https://pagure.io/releng/compose-tracker/pull-request/56
This should hopefully fix/workaround: https://pagure.io/fedora-infrastructure/issue/11833