-
Notifications
You must be signed in to change notification settings - Fork 747
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
Introduce self-hosted runners #4115
Conversation
interesting failure there... I don't have sufficient permissions to manually trigger a re-run |
Re-run triggered! |
I've blocked this on some internal devops changes we need to do (DM me for deets). I should be able to clear those this week 🤞 |
Same weird error 🤔 |
oooops... I changed something during / right after submitting this PR, breaking ipv6 tests |
We're waiting on one more senior infosec engineer to get their eyes across this one. ETA one week 🙏 |
I've just resolved the merge conflicts. It was fairly straight-forward but I note two things:
If Windows builds start failing we might need to add this snippet to bump LLVM: lighthouse/.github/workflows/test-suite.yml Lines 86 to 89 in 0c7eed5
|
Closed in favour of #4506 |
## Issue Addressed NA ## Proposed Changes Carries on from #4115, with the following modifications: 1. Self-hosted runners are only enabled if `github.repository == sigp/lighthouse`. - This allows forks to still have Github-hosted CI. - This gives us a method to switch back to Github-runners if we have extended downtime on self-hosted. 1. Does not remove any existing dependency builds for Github-hosted runners (e.g., installing the latest Rust). 1. Adds the `WATCH_HOST` environment variable which defines where we expect to find the postgres db in the `watch` tests. This should be set to `host.docker.internal` for the tests to pass on self-hosted runners. ## Additional Info NA Co-authored-by: antondlr <anton@delaruelle.net>
## Issue Addressed NA ## Proposed Changes Carries on from sigp#4115, with the following modifications: 1. Self-hosted runners are only enabled if `github.repository == sigp/lighthouse`. - This allows forks to still have Github-hosted CI. - This gives us a method to switch back to Github-runners if we have extended downtime on self-hosted. 1. Does not remove any existing dependency builds for Github-hosted runners (e.g., installing the latest Rust). 1. Adds the `WATCH_HOST` environment variable which defines where we expect to find the postgres db in the `watch` tests. This should be set to `host.docker.internal` for the tests to pass on self-hosted runners. ## Additional Info NA Co-authored-by: antondlr <anton@delaruelle.net>
## Issue Addressed NA ## Proposed Changes Carries on from sigp#4115, with the following modifications: 1. Self-hosted runners are only enabled if `github.repository == sigp/lighthouse`. - This allows forks to still have Github-hosted CI. - This gives us a method to switch back to Github-runners if we have extended downtime on self-hosted. 1. Does not remove any existing dependency builds for Github-hosted runners (e.g., installing the latest Rust). 1. Adds the `WATCH_HOST` environment variable which defines where we expect to find the postgres db in the `watch` tests. This should be set to `host.docker.internal` for the tests to pass on self-hosted runners. ## Additional Info NA Co-authored-by: antondlr <anton@delaruelle.net>
Run the following CI tasks on self-hosted runners:
Some tasks are no longer run inside the workflow ( installation of some dependencies,
rustup update
):Currently there are 2 active runners of each flavour:
[windows-1, windows-2, large-1, large-2, small-1, small-2]