Hide Forgot
Description of problem: If a build fails in %meson_test, the logs are "lost". It'd be great to automatically print the full log to stdout to make it easier to debug the failure. (If the tests don't fail, printing the logs is not interesting, and would make the logs stupidly long without reason.) I think that simply doing: %meson_test \ - %ninja_test -C %{_vpath_builddir} + %ninja_test -C %{_vpath_builddir} || \ + { r=$?; echo "==================== LOGS BEGIN ================; \ + cat %{_vpath_builddir}/meson-logs/testlog.txt; \ + echo "==================== LOGS END ================; \ + exit $r; } would be enough (untested). Version-Release number of selected component (if applicable): meson-0.43.0-1.fc26.noarch
https://github.com/mesonbuild/meson/pull/2476
meson-0.44.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d36a93314d
meson-0.44.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-38c43deb3b
meson-0.44.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d36a93314d
meson-0.44.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-38c43deb3b
meson-0.44.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
meson-0.44.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.