8000 The azure CI times out more and more often · Issue #23185 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]
Skip to content

The azure CI times out more and more often #23185

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.

Sign up for GitHub

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

Jump to bottom
Closed
jeremiedbb opened this issue Apr 22, 2022 · 2 comments · Fixed by #23190
Closed

The azure CI times out more and more often #23185

jeremiedbb opened this issue Apr 22, 2022 · 2 comments · Fixed by #23190
Labels
Build / CI

Comments

@jeremiedbb
Copy link
Member
jeremiedbb commented Apr 22, 2022 •
edited
Loading

  • The 2 windows jobs timeout (60min) more often than they don't these days. When they manage to complete, they take ~55min. I recall that they used to take "only" ~40min not so long ago.

  • The 2 macos jobs don't timeout but usually take ~50min while they used to take ~30min.

  • Even the linux jobs take more time than before.
@github-actions github-actions bot added the Needs Triage Issue requires triage label Apr 22, 2022
@jeremiedbb jeremiedbb added Build / CI and removed Needs Triage Issue requires triage labels Apr 22, 2022
@jeremiedbb
Copy link
Member Author
jeremiedbb commented Apr 22, 2022 •
edited
Loading

for reference, locally (linux, 4 cores) it runs in less than 17min, without xdist.
EDIT: locally it only runs ~25000 tests while it's ~90000 tests in the CI !

@lesteve lesteve changed the title The azure CI timesout more and more often The azure CI times out more and more often Apr 22, 2022
@jeremiedbb
Copy link
Member Author

So it's probably due to this addition:

if [[ "$SELECTED_TESTS" != "" ]]; then
    TEST_CMD="$TEST_CMD -k $SELECTED_TESTS"

    # Override to make selected tests run on all random seeds
    export SKLEARN_TESTS_GLOBAL_RANDOM_SEED="all"
fi

the CI shows the -k in the pytest invocation command meaning we are entering the test

@jeremiedbb jeremiedbb mentioned this issue Apr 22, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Build / CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

CI Fix don't run all random seeds all the time jeremiedbb/scikit-learn
1 participant
@jeremiedbb
0