The last build where it ran out of space was my bad, the build started earlier today resolved it but failed in HWTest which is probably something else.

this is also started to happening in M66, looks like out of disk also ?  What needs to be done to fix this ?  We are missing images for M66

https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos_release%2Ffizz-release_release-R66-10452.B%2F27%2F%2B%2Frecipes%2Fsteps%2FBuildImage__afdo_use_%2F0%2Fstdout

ERROR   : Target image has run out of space:
ERROR   : Filesystem     1M-blocks  Used Available Use% Mounted on
ERROR   : /dev/loop1          1723  1723         0 100% /mnt/host/source/src/build/images/fizz/R66-10452.34.0/rootfs
INFO    : Unmounting image from /mnt/host/source/src/build/images/fizz/R66-10452.34.0/stateful and /mnt/host/source/src/build/images/fizz/R66-10452.34.0/rootfs
INFO    : Unmounting temporary rootfs /mnt/host/source/src/build/images/fizz/R66-10452.34.0/rootfs//build/rootfs.
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/fizz/R66-10452.34.0/stateful/dev_image
An error occurred in your build so your latest output directory is invalid.
Running in non-interactive mode so deleting output directory.
Deleted /mnt/host/source/src/build/images/fizz/R66-10452.34.0
04:57:58: ERROR: 
return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmp15Wm_l' 'USE=-cros-debug chrome_internal afdo_use' 'FEATURES=separatedebug' 'CHROME_ORIGIN=LOCAL_SOURCE' -- ./build_image '--board=fizz' --replace '--version=10452.34.0' '--builder_path=fizz-release/R66-10452.34.0' base test
cmd=['/b/c/cbuild/repository/chromite/bin/cros_sdk', 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmp15Wm_l', u'USE=-cros-debug chrome_internal afdo_use', 'FEATURES=separatedebug', 'CHROME_ORIGIN=LOCAL_SOURCE', '--', './build_image', u'--board=fizz', '--replace', '--version=10452.34.0', u'--builder_path=fizz-release/R66-10452.34.0', 'base', 'test'], cwd=/b/c/cbuild/repository, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmp15Wm_l', 'USE': u'-cros-debug chrome_internal afdo_use', 'FEATURES': 'separatedebug', 'CHROME_ORIGIN': 'LOCAL_SOURCE'}
04:57:58: ERROR: Packages failed in ./build_image: chromeos-base/chromeos-chrome chromeos-base/chromeos-init

That space issue is the same thing and should already be fixed in the currently running 66 build.

Dropping 65 label since we build there, 66 should drop after the next build finishes, we can probably close this then.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.