@walki this failed tests because you changed the source tarball even though the package version did not change. Why did you do this? Why would the source tarball change between builds?
@adamwill I did this because I did not know the proper way how to handle this before. I used to do a new release on GitHub and then upload the new tarballs to Fedora and OpenSUSE only to find that e.g. the Fedora build failed due to some compiler flag I had never tested before. So then I would have to immediately do a new release on GitHub and all distors I maintain (Fedora , OpenSUSE and Windows).
In order to prevent this issue I started first uploading my to be released tarballs to Fedora and OpenSUSE and only if those builds would not cause any issues I would then do the official release on GitHub. I realise now that this is not the proper way to do it and I will have to figure out how to handle this better. The thing I want to avoid at all costs is to have to do multiple releases on GitHub because the Fedora or OpenSUSE build failed.
Yes, that's definitely not good project hygiene. :D Once you tag a release, that should be final, you should never change it.
To avoid this kind of issue, you can either do test builds on the distros you care about before you tag the upstream release, or you can just accept that you might have to do 8.5.1 and 8.5.2 and so on after releasing 8.5 and testing the downstream builds. The world is not going to run out of numbers.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update was automatically created
This update has obsoleted primecount-8.5-2.fc45, and has inherited its bugs and notes.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
@walki this failed tests because you changed the source tarball even though the package version did not change. Why did you do this? Why would the source tarball change between builds?
@adamwill I did this because I did not know the proper way how to handle this before. I used to do a new release on GitHub and then upload the new tarballs to Fedora and OpenSUSE only to find that e.g. the Fedora build failed due to some compiler flag I had never tested before. So then I would have to immediately do a new release on GitHub and all distors I maintain (Fedora , OpenSUSE and Windows).
In order to prevent this issue I started first uploading my to be released tarballs to Fedora and OpenSUSE and only if those builds would not cause any issues I would then do the official release on GitHub. I realise now that this is not the proper way to do it and I will have to figure out how to handle this better. The thing I want to avoid at all costs is to have to do multiple releases on GitHub because the Fedora or OpenSUSE build failed.
Yes, that's definitely not good project hygiene. :D Once you tag a release, that should be final, you should never change it.
To avoid this kind of issue, you can either do test builds on the distros you care about before you tag the upstream release, or you can just accept that you might have to do 8.5.1 and 8.5.2 and so on after releasing 8.5 and testing the downstream builds. The world is not going to run out of numbers.
This update has been obsoleted by primecount-8.6-1.fc45.