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

Re-enable Windows CI #13342

Closed
gsnedders opened this issue Oct 3, 2018 · 4 comments · Fixed by #16936
Closed

Re-enable Windows CI #13342

gsnedders opened this issue Oct 3, 2018 · 4 comments · Fixed by #16936

Comments

@gsnedders
Copy link
Member

gsnedders commented Oct 3, 2018

We should get CI running on Windows again.

The first stage of this should be getting all the tools/ unit tests and infrastructure/ tests running, even if we have to mark large amounts of these as XFAIL.

@foolip
Copy link
Member

foolip commented Nov 2, 2018

Plan A is to use Azure Pipelines. Basic tests can be run on Windows Server, but Windows 10 would be needed to test that Edge works.

@gsnedders
Copy link
Member Author

And to be clear, for those not following along with what I say in multiple different places: I don't view testing Edge so high priority, because the majority of Windows-specific bugs we've historically had have been in the lower level code than the browser-specific code.

@gsnedders
Copy link
Member Author

Mostly been waiting on #14300 getting something running on Windows. That's mostly working now, so I guess we should try basing the work here off of that, and just running things we can on Windows Server on the MS hosted agents.

@lukebjerring
Copy link
Contributor

@gsnedders - any progress on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants