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

Remove Windows as target machine from CI #616

Closed
ZER0 opened this issue Oct 13, 2021 · 0 comments · Fixed by #617
Closed

Remove Windows as target machine from CI #616

ZER0 opened this issue Oct 13, 2021 · 0 comments · Fixed by #617
Assignees

Comments

@ZER0
Copy link
Contributor

ZER0 commented Oct 13, 2021

Describe what you want implemented
CI shouldn't currently target Windows machine.

Describe "Why" this is needed
Having Windows as working machine is nice but it's not a target machine for our libraries. We had some random CI failures with no explanation whatsoever, and tests on Windows takes ages, slowing down the development process.
We can have a separate workflow for Windows once we reach a good level of library stabilization and we decide to target Windows too.

Describe alternatives you've considered
N/A

Additional context
N/A

@ZER0 ZER0 added this to the Implementing PlonkUp milestone Oct 13, 2021
@ZER0 ZER0 changed the title Add Windows as separate workflow for the CI Remove Windows as target machine from CI Oct 13, 2021
ureeves added a commit that referenced this issue Oct 13, 2021
@ureeves ureeves linked a pull request Oct 13, 2021 that will close this issue
ZER0 pushed a commit that referenced this issue Oct 13, 2021
@ureeves ureeves closed this as completed Oct 14, 2021
vlopes11 pushed a commit that referenced this issue Oct 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants