If the debian-package-build/rpm-package-build tasks fail to create a chroot, that should show up as a system failure (purple) instead of a task failure (red) so it is easier to determine whether the task was broken by code changes or environment changes.

The evergreen docs suggest this could be done by creating a file on failure to create a chroot environment, and having a subsequent "system" task check if that file exists.