Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve jenkins failures in 3.46.0.2 #16154

Closed
valenad1 opened this issue Apr 12, 2024 · 0 comments · Fixed by #16185, #16158, #16157, #16156 or #16155
Closed

Resolve jenkins failures in 3.46.0.2 #16154

valenad1 opened this issue Apr 12, 2024 · 0 comments · Fixed by #16185, #16158, #16157, #16156 or #16155
Assignees
Milestone

Comments

@valenad1
Copy link
Collaborator

This task is a harbor for all PR regards Jenkins failure fixes. It will be closed on rel-3.46.0.2 release.

@valenad1 valenad1 added this to the 3.46.0.2 milestone Apr 12, 2024
@valenad1 valenad1 self-assigned this Apr 12, 2024
valenad1 added a commit that referenced this issue Apr 12, 2024
valenad1 added a commit that referenced this issue Apr 12, 2024
…at usually fail for timeout (#16156)

* extend timeouts for XGBoostSmoke tests

* Increase timeout for nightly stages that usually fail for timeout. Try to mitigate timeout issue to see if there is acual problem in code or cluster connection.
valenad1 added a commit that referenced this issue Apr 15, 2024
It was a hot fix for xgboost release - since all the images are now on 44 and updated even for new xgboost, then we can use them properly.
krasinski pushed a commit that referenced this issue Apr 17, 2024
…at usually fail for timeout (#16156)

* extend timeouts for XGBoostSmoke tests

* Increase timeout for nightly stages that usually fail for timeout. Try to mitigate timeout issue to see if there is acual problem in code or cluster connection.
krasinski pushed a commit that referenced this issue Apr 17, 2024
It was a hot fix for xgboost release - since all the images are now on 44 and updated even for new xgboost, then we can use them properly.
valenad1 added a commit that referenced this issue Apr 30, 2024
* Currently the jenkins link not contain a node name. Its not a point to determine labels by that.
* change node label also for PR pipelines - related to 3253c98

TODO: delete the node labels logic if all the builds run ok
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment