The build logs for the Fedora jobs in gitlab CI are all getting
truncated with a message:

[1278/1650] gcc  -o te
Job's log exceeded limit of 4194304 bytes.
Job execution will continue but no more output will be collected.

when we're only 3/4 of the way through the build process this is
massively unhelpful if something fails at the end...like unit
tests.

Removing some -D flags and cutting down logs from the package
install phase remove about 1 MB of log file output.

Moving -W flags off the compiler command line, to a separate file,
removes about another 2 MB of log file output.

IOW, the overall log drops from 5.7 MB to 2.7 MB and are thus
fully captured by gitlab.

Patch 3 depends on:

  https://gitlab.com/libvirt/libvirt-ci/-/merge_requests/563

Daniel P. Berrangé (3):
  src: remove some -D defines from compiler args
  meson: write all warning flags to 'c-warnings.txt'
  ci: regenerate with 'lcitool manifest'

 ci/buildenv/almalinux-10.sh                   | 142 +++++++++--------
 ci/buildenv/almalinux-9.sh                    | 144 ++++++++---------
 ci/buildenv/centos-stream-10.sh               | 138 ++++++++--------
 ci/buildenv/centos-stream-9.sh                | 144 ++++++++---------
 ci/buildenv/fedora-42.sh                      | 142 ++++++++---------
 ci/buildenv/fedora-43-cross-mingw32.sh        |  94 +++++------
 ci/buildenv/fedora-43-cross-mingw64.sh        |  94 +++++------
 ci/buildenv/fedora-43.sh                      | 142 ++++++++---------
 ci/buildenv/fedora-rawhide-cross-mingw32.sh   |  96 +++++------
 ci/buildenv/fedora-rawhide-cross-mingw64.sh   |  96 +++++------
 ci/buildenv/fedora-rawhide.sh                 | 144 ++++++++---------
 ci/containers/almalinux-10.Dockerfile         | 146 ++++++++---------
 ci/containers/almalinux-9.Dockerfile          | 148 ++++++++---------
 ci/containers/centos-stream-10.Dockerfile     | 142 ++++++++---------
 ci/containers/centos-stream-9.Dockerfile      | 148 ++++++++---------
 ci/containers/fedora-42.Dockerfile            | 148 ++++++++---------
 .../fedora-43-cross-mingw32.Dockerfile        | 102 ++++++------
 .../fedora-43-cross-mingw64.Dockerfile        | 102 ++++++------
 ci/containers/fedora-43.Dockerfile            | 148 ++++++++---------
 .../fedora-rawhide-cross-mingw32.Dockerfile   | 104 ++++++------
 .../fedora-rawhide-cross-mingw64.Dockerfile   | 104 ++++++------
 ci/containers/fedora-rawhide.Dockerfile       | 150 +++++++++---------
 ci/gitlab/build-templates.yml                 |   6 +-
 meson.build                                   | 114 ++++++-------
 scripts/meson-warnings.py                     |   9 ++
 src/internal.h                                |   2 +
 src/meson.build                               |   6 +-
 src/remote/remote_protocol.x                  |   1 +
 28 files changed, 1490 insertions(+), 1466 deletions(-)
 create mode 100644 scripts/meson-warnings.py

-- 
2.52.0

On a Friday in 2026, Daniel P. Berrangé via Devel wrote:
>The build logs for the Fedora jobs in gitlab CI are all getting
>truncated with a message:
>
>[1278/1650] gcc  -o te
>Job's log exceeded limit of 4194304 bytes.
>Job execution will continue but no more output will be collected.
>
>when we're only 3/4 of the way through the build process this is
>massively unhelpful if something fails at the end...like unit
>tests.
>
>Removing some -D flags and cutting down logs from the package
>install phase remove about 1 MB of log file output.
>
>Moving -W flags off the compiler command line, to a separate file,
>removes about another 2 MB of log file output.
>
>IOW, the overall log drops from 5.7 MB to 2.7 MB and are thus
>fully captured by gitlab.
>
>Patch 3 depends on:
>
>  https://gitlab.com/libvirt/libvirt-ci/-/merge_requests/563
>
>Daniel P. Berrangé (3):
>  src: remove some -D defines from compiler args
>  meson: write all warning flags to 'c-warnings.txt'
>  ci: regenerate with 'lcitool manifest'
>

Reviewed-by: Ján Tomko <jtomko@redhat.com>

Jano