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

Diagnose and correct build breakage with VSCode-Python-CI (VSTS) #2549

Closed
3 tasks done
d3r3kk opened this issue Sep 11, 2018 · 0 comments · Fixed by #2550
Closed
3 tasks done

Diagnose and correct build breakage with VSCode-Python-CI (VSTS) #2549

d3r3kk opened this issue Sep 11, 2018 · 0 comments · Fixed by #2550
Assignees
@DonJayamanne @d3r3kk
Labels
bug Issue identified by VS Code Team member as probable bug debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority
Milestone
2018, week 36 - S...

Comments

@d3r3kk
Copy link

d3r3kk commented Sep 11, 2018 •
edited
Loading

The build has been consistently broken for over a week now, and it's time to escalate and get this fixed.

Need to investiaget:

  • CI changes that may be interfering with our Windows builds
  • Changes that made it in over the past few weeks, perhaps with a false positive?
  • Idenitfy the exact moment the build broke, and determine root cause.

=> Vscode changed how we initialize the extension
@d3r3kk d3r3kk self-assigned this Sep 11, 2018
@d3r3kk d3r3kk added feature-* bug Issue identified by VS Code Team member as probable bug debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Sep 11, 2018
@DonJayamanne DonJayamanne self-assigned this Sep 11, 2018
@DonJayamanne DonJayamanne mentioned this issue Sep 11, 2018
Merged
3 tasks
@brettcannon brettcannon added the important Issue identified as high-priority label Sep 11, 2018
@d3r3kk d3r3kk reopened this Sep 17, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Oct 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

@d3r3kk d3r3kk

Labels
bug Issue identified by VS Code Team member as probable bug debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority
Projects
None yet
Milestone
2018, week 36 - September 2018 Sprint 1
Development

Successfully merging a pull request may close this issue.

Resolves broken CI on Azure DevOps DonJayamanne/pythonVSCode
3 participants
@brettcannon @DonJayamanne @d3r3kk