-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Jenkins failing on Scala GPU #13080
Comments
@mxnet-label-bot [flaky, test, GPU, Scala] |
@marcoabreu @lebeg @larroy Me and Zach are now investigating the issue and see if we can reproduce them. Please take a look at here as well, is there any changes on GPU config recently? |
Resolution: This issue is typically appeared with GPU and not crash on CPU and Clojure. |
The issue appeared with a recent OpenJDK upgrade, here is the workaround we will take to solve this issue:
But I am still thinking this problem can only reproduce on GPU, not the CPU. There might be a diff on the JDK version between these two VM, |
No there has not been an update recently. @lebeg you rolled back, right? @Chancebair fyi |
Another occurrence of the same - http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-12775/14/pipeline/ |
@zachgk since PR is merged, do we close this? |
@zachgk , please close the issue as it seems that PR has been merged. Unless there is something else to do here to address it? |
There is a failure occurring on the Jenkins in the Scala GPU task. The failure is occurring when running "make scalapkg" to build the core module.
One sample error ending is:
We have identified a number of Jenkins runs that produced this:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-13077/1/pipeline
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-13071/1/pipeline
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-13052/2/pipeline
The problem has also been observed on the dev Jenkins:
http://jenkins.mxnet-ci-dev.amazon-ml.com/blue/organizations/jenkins/restricted-publish-artifacts/detail/automate-maven/61/pipeline
The text was updated successfully, but these errors were encountered: