This is an update for system JDK shift from JDK 17 to JDK 21.
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-9b9da603e1
Please login to add feedback.
0 | 0 | Test Case crypto-policies |
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
Congratulations on building an update so big, openQA can't download all the packages in it to a 10GB scratch disk. :D
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
LOL, I am sorry, I guess Javastack is too big now O:)
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
.
so I am working on getting all the test mess cleaned up, but while I do that, I think there is actually a genuine bug here. I think it breaks FreeIPA server deployment, with this error:
It is definitely possible some rebuilt dependency broke it. Thank you, I will look into it now.
The reason is for sure, that stack wsa built by jdk21, but the used runtime jre was 17 (the numbers are sure - 17 is 61 and 21 is 65).
The simple workaround is to built com/fasterxml/ t0ools with backward compatible bytecode . That measn setting source and target to 17. But that can bite later.
The fix is to ensure, that the FreeIPA server (or only its tests?) get launched by system JDK.. The most likely casue is that freeipa (or some of its dependencies) requires literally java-17-openjdk, instead of just versionless java. The dfree ip a 9test?)runner then pick 17 instead of 21.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update cannot be pushed to stable. These builds diffoscope-257-2.fc41 have a more recent build in koji's f41 tag.
pmikova edited this update.
New build(s):
Removed build(s):
Karma has been reset.
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 submitted for stable by bodhi
This update's test gating status has been changed to 'failed'.
@abbra @rcritten please take a look...
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Oh, wow. So someone just waived the test failure and pushed this stable? Please do not do that. It is not the right thing to do. Now FreeIPA is broken for everyone, and the test will fail for every other update, preventing them all from going stable.
I will get this untagged.
Untag request: https://pagure.io/releng/issue/11990
@jvanek this test is not running some kind of test suite, it is testing an actual real-world deployment of FreeIPA. the test failing means deployment of FreeIPA is broken by this update.
Fortunately, I was able to clean this up; by luck, just rebuilding dogtag-pki to actually build against Java 21 works at least well enough for the FreeIPA tests to pass. There may well be other incompatibilities that need resolving, but at least the basic test set is OK.
ty!
What about other, numerous test failures? Are they going to be fixed?