Looking into mysql-connector-java, the thing it requires was provided by protobuf-java , which you seem to have simply removed in this update because "Can't get it to build". That seems questionable.
This update's test gating status has been changed to 'failed'.
The tests for mysql-java-connector are failing with
expected ExclusiveArch "aarch64 ppc64le s390x x86_64 riscv64" but was ""
I have no idea why it is there.
What about the criu? If the test is since previous update I am inclining to waive it out.
I have just discussed the failing "mysql-java-connector" test with @mkoncek and it is ok to waive it. The tests are made for single package update and will not wokr for side-tag builds with more packages.
Meh, it's rather difficult to reproduce the test process with any confidence, but I think it's probably okay. What I wound up doing is setting up a Rawhide VM and running the python3 ./zdtm.py run --criu-bin /usr/sbin/criu -a --ignore-taint --keep-going command from the test suite (in a checkout of the package, after building criu within the source dir...), then update with all the packages from this update and doing the same thing.
On the 'before' run, the tests file_locks01(uns) and rseq01(h) failed; on the 'after' run, those tests failed and also socket-tcpbuf-local failed. But I think that's likely a flake; I think it also failed on an earlier 'before' run (when I wasn't properly logging the output). Neither run shows mmap failures.
So...I think it's probably OK to waive the criu failure? But it'd still be great if @adrian could look at it.
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 'failed'.
The criu test failure seems to be caused by a bug in mumble's scriptlets:
I'm not sure why rpmdeplint.functional is missing for perl-Alien-ProtoBuf.
rmdepcheck notes one missing dependent rebuild:
Oh, rpmdeplint was skipped because there are more than 20 builds in the update.
I do wonder if we could stop doing that, now I made it faster.
adamwill edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
Looking into mysql-connector-java, the thing it requires was provided by protobuf-java , which you seem to have simply removed in this update because "Can't get it to build". That seems questionable.
This update's test gating status has been changed to 'failed'.
criu test now appears to have some issues allocating memory:
@adrian , can you see what's going on here by any chance? It seems the tests passed on your most recent standalone update a month ago...
We plan to start the Python 3.15 rebuild tonight. I would feel much more comfortable if this landed before that.
I guess we could try and see if the criu tests fail outside of this update, somehow. But that still leaves the missing java interface.
msuchy edited this update.
New build(s):
Removed build(s):
Karma has been reset.
I added protobuf with java subpackage and rebuilt mysql-connector-java with the new protobuf-java
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
The tests for mysql-java-connector are failing with expected ExclusiveArch "aarch64 ppc64le s390x x86_64 riscv64" but was "" I have no idea why it is there. What about the criu? If the test is since previous update I am inclining to waive it out.
I have just discussed the failing "mysql-java-connector" test with @mkoncek and it is ok to waive it. The tests are made for single package update and will not wokr for side-tag builds with more packages.
I'm trying to see if I can reproduce the criu failure with older protobuf. It's a PITA to get it running.
Meh, it's rather difficult to reproduce the test process with any confidence, but I think it's probably okay. What I wound up doing is setting up a Rawhide VM and running the
python3 ./zdtm.py run --criu-bin /usr/sbin/criu -a --ignore-taint --keep-goingcommand from the test suite (in a checkout of the package, after building criu within the source dir...), then update with all the packages from this update and doing the same thing.On the 'before' run, the tests file_locks01(uns) and rseq01(h) failed; on the 'after' run, those tests failed and also socket-tcpbuf-local failed. But I think that's likely a flake; I think it also failed on an earlier 'before' run (when I wasn't properly logging the output). Neither run shows mmap failures.
So...I think it's probably OK to waive the criu failure? But it'd still be great if @adrian could look at it.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
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
fwiw, libphonenumber-8.13.55-10 silently changed abi. e-d-s->evolution ails to start
evolution: symbol lookup error: /lib64/libebook-contacts-1.2.so.5: undefined symbol: _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaEb