-
Notifications
You must be signed in to change notification settings - Fork 2
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
Use GitHub Workflow for CI #38
base: master
Are you sure you want to change the base?
Conversation
@takluyver Tests 'work' as in they actually run properly, but some are failing, any idea why? |
One nice thing that Circle CI offers, and as far as I know no other CI service does, is that when a job fails, you can re-run it with an SSH server enabled, then SSH in to investigate interactively. This has been useful on occasion with testing the GUI - if something hangs, you can SSH with X forwarding, run in the exact same environment, and see what's happening. I haven't used this very often, so maybe the benefits of Github actions outweigh it, but it's worth noting that there's some downside here. You might want to see what @CammilleCC thinks, as the person now mostly responsible for the GUI code. |
Co-authored-by: Thomas Kluyver <[email protected]>
3cb10ee
to
39c9a91
Compare
There is an action for this: https://github.com/marketplace/actions/debugging-with-ssh Which can use the public SSH keys you have added to your GitHub profile to let you access the CI as it runs.
TBH I think that it should be simple to reproduce the CI environments locally, at the top of the CI log you can see the information about the environment setup:
And there's the the act tool to run the CI locally: https://github.com/nektos/act act is pretty neat, it's extremely useful, you can run the CI pipeline triggered by a certain event (e.g. |
No description provided.