[CI] Modify Jenkinfile to always display junit report, fix for #8674

[mikepapadim]

This is a fix for #8674.

It always displays junit reports when tests fail.

@areusch

[areusch]

thanks @mikepapadim , pushed to https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/144/pipeline with some injected test failures to see how they look!

[areusch]

hmm https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/144/tests

don't see any tests

[mikepapadim]

I will check again. An alternative seems to be moving the junit as the following post-stage action:

 post {
        always {
            junit "build/pytest-results/*.xml"
        }
    }

[areusch]

@mikepapadim I think this might still be busted. can you see if you can run it through a staging jenkins? here's what i am using to test your change

[areusch]

@mikepapadim any update here?

[mikepapadim]

@mikepapadim any update here?

Need to give it a go through CI. I ll update accordingly.

[mikepapadim]

Let's wait for the CI, but now with the post-action per stage, test results should always be registerd.

[areusch]

thanks @mikepapadim i think the Jenkinsfile looks good now, just some extra cruft in this one. I pushed to https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/159/pipeline with some injected test failures.

can you remove the cruft and assuming that build looks good (test failures are reported) we can merge?

[areusch]

there are a couple of random changes to .md files in here, can you revert?

[mikepapadim]

thanks @mikepapadim i think the Jenkinsfile looks good now, just some extra cruft in this one. I pushed to https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/159/pipeline with some injected test failures.

can you remove the cruft and assuming that build looks good (test failures are reported) we can merge?

I will fix them. Thanks for reviewing.

Btw if we go forward with #9042 then we might want to wait for this one as it could potentially be much cleaner with a declarive pipeline.

[areusch]

@mikepapadim let's merge this first, then migrate to #9042 separately. it will be more helpful to get test flakiness data sooner rather than later.

[denise-k]

@areusch @mikepapadim any update on this?

[driazati]

With something like #9823 this could also help this be cleaner (since the post could be defined just once)

[areusch]

closing due to stale PR and I believe this is implemented now