On 17/01/2023 11.23, Peter Maydell wrote:
On Mon, 16 Jan 2023 at 16:55, Peter Maydell <peter.mayd...@linaro.org> wrote:
On Thu, 15 Dec 2022 at 15:30, Thomas Huth <th...@redhat.com> wrote:
We're still running into the problem that some logs are cut in the
gitlab-CI since they got too big. The biggest part of the log is
still the output of the qom-test. Let's stop printing the properties
by default to get to a saner size here. The full output can still
be enabled by setting V=2 (or higher) in the environment.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
v2: Use atoi() to do proper checking of the verbosity level
Applied to master in the hope of improving the CI logs; thanks.
Looks like we can still hit the gitlab log limit in some
cases, even with this patch; here's an example job:
https://gitlab.com/qemu-project/qemu/-/jobs/3610621992
Ok, too bad ... three ideas to improve this situation further:
- We could shut up those "Obtaining properties of" lines by
default
- Stop running the tests with "V=1"
- Instead of doing "cat meson-logs/testlog.txt" in the CI
scripts, we switch to "tail -n 1000 meson-logs/testlog.txt"
instead
What do you think?
Thomas
