This repository was archived by the owner on Nov 17, 2023. It is now read-only.
adding stacktrace in Jenkinsfile_utils.groovy #17065
Merged
Merged
Conversation
Contributor
Author
|
@anirudh2290 @marcoabreu Can you review ? |
Member
|
were you able to test this somewhere ? |
Contributor
Author
|
No I tested this code in a different file for stacktrace. I don't know how to. Let me know if you do |
Member
|
Apologies, i dont know how it edited your comment .
Okay, thats what I was looking for. Testing the line of code if it works in general. To test in this specific code, you can throw an exception from throw block and see if it prints stacktrace in a dev environment. |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
to inspect cause of Python2 failure in CI (Unix CPU)
To identify root cause of : #16995
Upon Inspecting different timeout on Unix CPU in the following runs:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-16965/12/pipeline/296 Py3 CPU Debug
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-16971/8/pipeline/294 Py2 CPU
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-17018/5/pipeline/294 Py2 CPU
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/master/1387/pipeline/47 CPU MKLDNN / CPU_MKLDNN_MKL (build)
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-cpu/branches/PR-16885/runs/9/nodes/294/steps/786/log/?start=0 Py2 CPU
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-cpu/branches/master/runs/1371/nodes/294/steps/747/log/?start=0 Py2 CPU
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-cpu/branches/master/runs/1336/nodes/294/steps/796/log/?start=0 Py2 CPU
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-cpu/branches/master/runs/1337/nodes/294/steps/784/log/?start=0 Py2 CPU
All the tests passed when looked into the logs of Jenkin's run but it fails with message:
you can see many files when you grep for Cancelling nested steps due to timeout, but all of them have just one line : caught "Exception name"
This PR prints the stacktrace of the exception to help identify the root cause of CI timeouts in jenkins
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.