Update NSS to 3.106.0 Update to Firefox 133.0
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-b266d38c44Please log in to add feedback.
| 0 | 2 | Test Case firefox addons |
| 0 | 3 | Test Case firefox browse |
| 0 | 3 | Test Case firefox media |
| 0 | 2 | Test Case firefox screenshot |
This update has been submitted for testing by fkrenzel.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works.
stransky edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by stransky.
This update has been submitted for stable by bodhi.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
FEDORA-2024-b266d38c44 ejected from the push because 'Required tests for this update are queued or running.'
Are tests stuck?
This update's test gating status has been changed to 'ignored'.
This update has been submitted for stable by bodhi.
This update's test gating status has been changed to 'waiting'.
Is it going to be ejected again due tests not completed?
Gating status is still waiting...
This update's test gating status has been changed to 'passed'.
Sorry for the gating problem, it seems to have been because the test got restarted but the result of the retry never made it to resultsdb. I have a script which tries to fix up the occasional case where, for some reason, results don't go to openQA, but it didn't catch this case because it looks a bit different than usual. The last result that made it to resultsdb was 'running', so the gating status was 'waiting' not 'failed', and the fixup script only looks for updates in 'failed' gating status.
er, "where, for some reason, results don't go to openQA" should be "where, for some reason, openQA results don't go to resultsdb". sorry.
Thanks for sorting it @adamwill !
This update has been pushed to stable.