Truncated script logs (100MB limit?)

[emaste]

Expected Behavior

Full log is available in web view or via download link, or at least an indication that the log was truncated.

Real Behavior

Script log is truncated at about 100MB (example linked below is 100007936 bytes)

Example: https://cirrus-ci.com/task/6379372546883584
Downloaded log ends at the same place as shown in web UI

In function 'ice_add_marker_act',
    inlined from 'ice_add_update_vsi_list' at /tmp/cirrus-ci-build/sys/dev/ice/ice_switch.c:1877:8,
    inlined from 'ice_add_rule_internal' at /tmp/cirrus-ci-build/sys/dev/ice/ice_switch.c:2032:11,
    inlined from '_ice_set_vsi_promisc' at /tmp/cirrus-ci-build/sys/dev/ice/ice_switch.c:3577:12,
    inlined from 'ice_set_vsi_promisc' at /tmp/cirrus-ci-build/sys/dev/ice/ice_switch.c:3598:9:
/tmp/cirrus-ci-build/sys/dev/ice/ice_switch.c:1422:37: warning: arr

Related Info

This is a (tick one of the following):

• Website issue
  • Link to page:
• Task issue
  • OS: FreeBSD
  • Task name: amd64-gcc12 World and kernel build and boot smoke test (FreeBSD repo)
  • Script/cache name (if applies):

[emaste]

Issue avoided in FreeBSD by splitting into two smaller scripts: freebsd/freebsd-src@6024564 but would still be nice to have some explicit indication that truncation occurred

[emaste]

Apparently one of the smaller split jobs is now over the limit. FreeBSD job disabled again until we can sort it out: freebsd/freebsd-src@0ed2e7e