The chroot environment we create in these tasks is not uploaded as an evergreen artifact (and it probably should not be due to the large size). But to help diagnose whether failures on these tasks are transient, it'd be helpful to echo or upload the associated logs.

For debian-package-build, that appears to be the debootstrap.log mentioned in the evergreen logs. Example:

See /data/mci/ac6a036b0a286979eeb45928278579bc/unstable-chroot/debootstrap/debootstrap.log for details (possibly the package systemd is at fault)