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

add CI for WSL #974

Closed
warner opened this issue Apr 21, 2020 · 1 comment · Fixed by #998
Closed

add CI for WSL #974

warner opened this issue Apr 21, 2020 · 1 comment · Fixed by #998
Assignees
Labels
tooling repo-wide infrastructure

Comments

@warner
Copy link
Member

warner commented Apr 21, 2020

To help with #950 (and discover such failures earlier in the future), I'm trying to set up a CI workflow that runs on windows, specially under the "Windows Subsystem for Linux" that @dtribble uses on his workstation.

@warner warner added the tooling repo-wide infrastructure label Apr 21, 2020
@warner warner self-assigned this Apr 21, 2020
@warner warner mentioned this issue Apr 24, 2020
@warner
Copy link
Member Author

warner commented Apr 24, 2020

notes on how long the CI takes:

  • 0m10s to install Go
  • 0m03s to install NVM
  • 0m11s for NVM to install Node 13
  • 0m05s for Node 13 to install Yarn
  • 2m13s to install build-essential (gcc, g++, make, etc)
  • 3m00s to run yarn (install) and yarn build
  • 9m39s to run yarn test on all packages

Total job time is 15m27s.

warner added a commit that referenced this issue Apr 24, 2020
add Appveyor CI to test agoric-sdk on WSL

This takes about 15 minutes to run right now.

closes #974
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling repo-wide infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant