Hello,
I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example:
25/41 Test #25: List_test ........................ Passed 0.01 sec Start 26: Particle_test 26/41 Test #26: Particle_test .................... Passed Errors while running CTest make[3]: *** [src/core/unit_tests/CMakeFiles/check_unit_tests.dir/build.make:60: src/core/unit_tests/CMakeFiles/check_unit_tests] Error 8 make[2]: *** [CMakeFiles/Makefile2:2265: src/core/unit_tests/CMakeFiles/check_unit_tests.dir/all] Error 2 make[1]: *** [CMakeFiles/Makefile2:116: CMakeFiles/check.dir/rule] Error 2 make: *** [Makefile:191: check] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check) 0.01 sec Start 27: for_each_pair_test ... 41/41 Test #41: Span_test ........................ Passed 0.01 sec
98% tests passed, 1 tests failed out of 41
Total Test time (real) = 16.69 sec
The following tests FAILED: 23 - ParticleCache_test (Failed) make[3]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[2]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[1]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build'
RPM build errors: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)
See the "error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)" part in the middle of %check output.
Has something changed? Or is it an rpm 4.15 thing?
On Mon, Jul 1, 2019, 15:42 Miro Hrončok mhroncok@redhat.com wrote:
Hello,
I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example:
25/41 Test #25: List_test ........................ Passed 0.01 sec Start 26: Particle_test 26/41 Test #26: Particle_test .................... Passed Errors while running CTest make[3]: *** [src/core/unit_tests/CMakeFiles/check_unit_tests.dir/build.make:60: src/core/unit_tests/CMakeFiles/check_unit_tests] Error 8 make[2]: *** [CMakeFiles/Makefile2:2265: src/core/unit_tests/CMakeFiles/check_unit_tests.dir/all] Error 2 make[1]: *** [CMakeFiles/Makefile2:116: CMakeFiles/check.dir/rule] Error 2 make: *** [Makefile:191: check] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check) 0.01 sec Start 27: for_each_pair_test ... 41/41 Test #41: Span_test ........................ Passed 0.01 sec
98% tests passed, 1 tests failed out of 41
Total Test time (real) = 16.69 sec
The following tests FAILED: 23 - ParticleCache_test (Failed) make[3]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[2]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[1]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build'
RPM build errors: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)
See the "error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)" part in the middle of %check output.
Has something changed? Or is it an rpm 4.15 thing?
I think this is caused by multithreading in RPM 4.15. A similar issue breaks specially-formatted output from Java packaging tools - because it's no longer necessarily on contiguous, uninterrupted lines in the build.log.
I think stdout / stderr from different sources are no longer printed in strictly chronological order (file / stdfoo writes are not flushed).
Fabio
On 01. 07. 19 15:53, Fabio Valentini wrote:
On Mon, Jul 1, 2019, 15:42 Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
Hello, I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example: 25/41 Test #25: List_test ........................ Passed 0.01 sec Start 26: Particle_test 26/41 Test #26: Particle_test .................... Passed Errors while running CTest make[3]: *** [src/core/unit_tests/CMakeFiles/check_unit_tests.dir/build.make:60: src/core/unit_tests/CMakeFiles/check_unit_tests] Error 8 make[2]: *** [CMakeFiles/Makefile2:2265: src/core/unit_tests/CMakeFiles/check_unit_tests.dir/all] Error 2 make[1]: *** [CMakeFiles/Makefile2:116: CMakeFiles/check.dir/rule] Error 2 make: *** [Makefile:191: check] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check) 0.01 sec Start 27: for_each_pair_test ... 41/41 Test #41: Span_test ........................ Passed 0.01 sec 98% tests passed, 1 tests failed out of 41 Total Test time (real) = 16.69 sec The following tests FAILED: 23 - ParticleCache_test (Failed) make[3]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[2]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[1]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' RPM build errors: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check) See the "error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)" part in the middle of %check output. Has something changed? Or is it an rpm 4.15 thing?
I think this is caused by multithreading in RPM 4.15. A similar issue breaks specially-formatted output from Java packaging tools - because it's no longer necessarily on contiguous, uninterrupted lines in the build.log.
I think stdout / stderr from different sources are no longer printed in strictly chronological order (file / stdfoo writes are not flushed).
I wonder whether this would be considered a bug in rpm?
Florian, Panu?
Miro Hrončok wrote:
Hello,
I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example:
Are you using %make_build or at least 'make -O' ?
just 'make %{?_smp_mflags}' does have chances of getting ordering wrong without -O flag
-- Rex
On 11. 07. 19 22:40, Rex Dieter wrote:
Miro Hrončok wrote:
Hello,
I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example:
Are you using %make_build or at least 'make -O' ?
just 'make %{?_smp_mflags}' does have chances of getting ordering wrong without -O flag
This happens everywhere, not just with make.
Sometimes I even see "Bad exist status from %check" in the middle of pytest output.
On 7/1/19 3:54 PM, Miro Hrončok wrote:
Hello,
I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example:
[...]
See the "error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)" part in the middle of %check output.
Has something changed? Or is it an rpm 4.15 thing?
It was indeed a regression introduced in 4.15, and should be now fixed as of rpm >= 4.15.0-0.beta.3
The fix is upstream already but test-driving it in rawhide for a few days prior to rc1 release (next week), please report any new anomalies ASAP if you encounter them.
- Panu -