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.

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

Split CI tests into seprate jobs (temporary work around for flaky tests) #1247

Closed
DonJayamanne opened this issue Mar 30, 2018 · 0 comments · Fixed by #1251
Closed

Split CI tests into seprate jobs (temporary work around for flaky tests) #1247

DonJayamanne opened this issue Mar 30, 2018 · 0 comments · Fixed by #1251
Assignees
@DonJayamanne
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Milestone
April 2018

Comments

@DonJayamanne
Copy link

DonJayamanne commented Mar 30, 2018 •
edited
Loading

Split CI tests into three separate jobs:

  • Debugger tests
  • Single workspace tests
  • Multiroot workspace test

Purpose:

  • Faster tests on CI
  • Easier to restart a specific test (rather than running all test all over again)

Currently the above three sets of tests are already run separately. Running them as separate jobs on CI will make it easier to re-start one of them without having to re-run everything all over again.

Temporary work around until we get flaky tests running properly
This could lay the ground works for running Integration tests on a release branch
@DonJayamanne DonJayamanne self-assigned this Mar 30, 2018
@DonJayamanne DonJayamanne added this to the April 2018 milestone Mar 30, 2018
@DonJayamanne DonJayamanne added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Mar 30, 2018
@DonJayamanne DonJayamanne mentioned this issue Mar 30, 2018
Merged
5 tasks
DonJayamanne added a commit that referenced this issue Apr 4, 2018
@DonJayamanne
Parallelize unit tests on CI server (Travis) (#1251)
60ff772 
Fixes #1247
Temporary work around for #1250 (didn't add a news entry for the work around)
@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Projects
None yet
Milestone
April 2018
Development

Successfully merging a pull request may close this issue.

Parallelize unit tests on CI server (Travis) DonJayamanne/pythonVSCode
1 participant
@DonJayamanne