failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download.
any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure.
[impact]
failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download.
[test case]
see any failed build or failed root-unittest, e.g. /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- eoan/eoan/ ppc64el/ s/systemd/ 20200331_ 010822_ 1c88e@/ log.gz
https:/
[regression potential]
any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure.
[scope]
this is needed in all releases.