Two runs of curtin's CI were performed for xenial: the first, our regular Jenkins run had some tests fail due to bugs in the test code (that have since been fixed upstream), so the second reruns the upstream test code for those tests against the -proposed package.
Two runs of curtin's CI were performed for xenial: the first, our regular Jenkins run had some tests fail due to bugs in the test code (that have since been fixed upstream), so the second reruns the upstream test code for those tests against the -proposed package.