Re: Lines disordered in mock's build.log

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01. 07. 19 15:53, Fabio Valentini wrote:
On Mon, Jul 1, 2019, 15:42 Miro Hrončok <mhroncok@xxxxxxxxxx <mailto:mhroncok@xxxxxxxxxx>> 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
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux