A successful run with test results: https://ci.docker.com/public/blue/organizations/jenkins/moby/detail/PR-39638/3/tests

ping @vdemeester ptal

interesting failure on janky

16:40:05 === FAIL: pkg/pubsub TestSendToOneSub (0.00s)
16:40:05     publisher_test.go:17: expected message hi but received hi

@thaJeztah i needed to introduce a failure to see how junit failure reporting looks: https://ci.docker.com/public/job/moby/job/PR-39638/9/testReport/github/com_docker_docker_pkg_pubsub/TestSendToOneSub/

I think this is ready for merge. This PR adds another parallel PR check stage in the Jenkinsfile for just running the unit tests via hack/test/unit on x86_64. The result of the stage will produce 3 artifacts in a unit-bundles.tar.gz file that will be stored with the job run, e.g. https://ci.docker.com/public/blue/organizations/jenkins/moby/detail/PR-39638/10/artifacts

The contents of the bundle are:

• go-test-report.json - the go test -json output
• junit-report.xml - the junit format of the test result for consumption by jenkins
• profile.out - the coverage report of the unit test runs

The Jenkinsfile has been updated in this PR to consume the junit-report.xml for making graphs and tables of the result like so: https://ci.docker.com/public/job/moby/job/PR-39638/10/testReport/github/

The graphs and tables will help developers quickly locate the info of the failing unit tests instead of searching for the error on the verbose console output page of the jenkins job.

To accomplish this, I had to add gotestsum to the Dockerfile image because it can run the unit tests and generate the junit-report.xml.

gotestsum works great with go test, but will break for gocheck used by integration-cli. We can discuss that separately.

PTAL @thaJeztah @vdemeester

LGTM