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

Mocha tests are completing but AzDO fails to end, causing a timeout failure on CI #4760

Closed
d3r3kk opened this issue Mar 14, 2019 · 2 comments
Closed

Mocha tests are completing but AzDO fails to end, causing a timeout failure on CI #4760

d3r3kk opened this issue Mar 14, 2019 · 2 comments
Assignees
@DonJayamanne
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Milestone
2019, week 11 - M...

Comments

@d3r3kk
Copy link

d3r3kk commented Mar 14, 2019

Mocha tests are completing, and succeeding, in AzDO, but the test task never completes. This causes AzDO to fail after an hour due to timeout.
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Mar 14, 2019
@d3r3kk d3r3kk added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Mar 14, 2019
@ghost ghost removed triage-needed Needs assignment to the proper sub-team labels Mar 14, 2019
@d3r3kk
Copy link
Author

d3r3kk commented Mar 14, 2019

This happens most usually on Windows, but we've seen it on macOS builds as well.

d3r3kk added a commit to d3r3kk/vscode-python that referenced this issue Mar 14, 2019
@d3r3kk
Fix up AzDO CI
db55956 
For microsoft#4336

This PR cleans up our nightly build. Some issues remains as there is not a reliable fix yet (microsoft#4760).

- skip flaky tests
- remove mocha-vsts-reporter from use
- update build badges to point to new AzDO
@d3r3kk d3r3kk mentioned this issue Mar 14, 2019
Merged
9 tasks
d3r3kk added a commit that referenced this issue Mar 14, 2019
@d3r3kk
Azure DevOps Nightly CI fixes (#4761)
6e746c6 
This PR cleans up our nightly build. Some issues remains as there is not a reliable fix yet (#4760).
- skip flaky tests
- remove mocha-vsts-reporter from use
- update build badges to point to new AzDO
@d3r3kk d3r3kk mentioned this issue Mar 15, 2019
Closed
8 tasks
@d3r3kk
Copy link
Author

d3r3kk commented Mar 21, 2019

Using tools like wtfnode and why-is-node-running will likely help sort out this issue.

@d3r3kk d3r3kk mentioned this issue Mar 21, 2019
Closed
@DonJayamanne DonJayamanne self-assigned this Mar 26, 2019
@ghost ghost removed the needs PR label Mar 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Apr 24, 2019
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
2019, week 11 - March Sprint 6
Development

No branches or pull requests
2 participants
@DonJayamanne @d3r3kk