Hi Thomas,

This has been fixed as of yesterday.  The failure was caused by a commit to the SPDK repos in how they pull in their dependencies, which was done in a way that is not compatible with docker.  The team created a work around so that case is fixed, but there is always a risk where other commits for those type of items could cause a failure in the containers.

I asked Brandon to change the scripts that run the testing in the containers to try and catch failures from docker separately, so they can be flagged as infrastructure, compared to failures of the build.

I'm also very surprised, this was not raised during the CI meeting, or by anyone else.  I'm wondering if this is caused by the actual error logs being a little abstracted from the emails, i.e. they are a link and a zip file away for the actual email text, so maybe folks are not really looking into the output as closely as they should be.  Is this something we can make better by including more detail in the email text, so issues are caught more quickly?

Cheers,
Lincoln