cerc-io/lighthouse
15
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
230168deff
lighthouse/bors.toml

31 lines
759 B
TOML
Raw Normal View History

Remove macos tests (#1687) ## Issue Addressed N/A ## Proposed Changes Remove the MacOs tests. They routinely fail, causing bors to retry and slowing down the whole merge process. ## Additional Info N/A Co-authored-by: Michael Sproul <michael@sigmaprime.io>
2020-09-30 01:27:36 +00:00
status = [
"cargo-fmt",
"release-tests-ubuntu",
Add Windows to Bors config (#2358) We accidentally omitted the new Windows tests (#2333) from the Bors config, meaning that PRs will merge before the tests pass. This PR corrects that.
2021-05-20 00:23:08 +00:00
"release-tests-windows",
Remove macos tests (#1687) ## Issue Addressed N/A ## Proposed Changes Remove the MacOs tests. They routinely fail, causing bors to retry and slowing down the whole merge process. ## Additional Info N/A Co-authored-by: Michael Sproul <michael@sigmaprime.io>
2020-09-30 01:27:36 +00:00
"debug-tests-ubuntu",
"state-transition-vectors-ubuntu",
"ef-tests-ubuntu",
"dockerfile-ubuntu",
"eth1-simulator-ubuntu",
Add merge support to simulator (#3292) ## Issue Addressed N/A ## Proposed Changes Make simulator merge compatible. Adds a `--post_merge` flag to the eth1 simulator that enables a ttd and simulates the merge transition. Uses the `MockServer` in the execution layer test utils to simulate a dummy execution node. Adds the merge transition simulation to CI.
2022-07-18 23:15:40 +00:00
"merge-transition-ubuntu",
Remove macos tests (#1687) ## Issue Addressed N/A ## Proposed Changes Remove the MacOs tests. They routinely fail, causing bors to retry and slowing down the whole merge process. ## Additional Info N/A Co-authored-by: Michael Sproul <michael@sigmaprime.io>
2020-09-30 01:27:36 +00:00
"no-eth1-simulator-ubuntu",
"check-benchmarks",
"check-consensus",
"clippy",
"arbitrary-check",
"cargo-audit",
Rename random to prev_randao (#3040) ## Issue Addressed As discussed on last-night's consensus call, the testnets next week will target the [Kiln Spec v2](https://hackmd.io/@n0ble/kiln-spec). Presently, we support Kiln V1. V2 is backwards compatible, except for renaming `random` to `prev_randao` in: - https://github.com/ethereum/execution-apis/pull/180 - https://github.com/ethereum/consensus-specs/pull/2835 With this PR we'll no longer be compatible with the existing Kintsugi and Kiln testnets, however we'll be ready for the testnets next week. I raised this breaking change in the call last night, we are all keen to move forward and break things. We now target the [`merge-kiln-v2`](https://github.com/MariusVanDerWijden/go-ethereum/tree/merge-kiln-v2) branch for interop with Geth. This required adding the `--http.aauthport` to the tester to avoid a port conflict at startup. ### Changes to exec integration tests There's some change in the `merge-kiln-v2` version of Geth that means it can't compile on a vanilla Github runner. Bumping the `go` version on the runner solved this issue. Whilst addressing this, I refactored the `testing/execution_integration` crate to be a *binary* rather than a *library* with tests. This means that we don't need to run the `build.rs` and build Geth whenever someone runs `make lint` or `make test-release`. This is nice for everyday users, but it's also nice for CI so that we can have a specific runner for these tests and we don't need to ensure *all* runners support everything required to build all execution clients. ## More Info - [x] ~~EF tests are failing since the rename has broken some tests that reference the old field name. I have been told there will be new tests released in the coming days (25/02/22 or 26/02/22).~~
2022-03-03 02:10:57 +00:00
"cargo-udeps",
"beacon-chain-tests",
"op-pool-tests",
"doppelganger-protection-test",
"execution-engine-integration-ubuntu",
Add minimum supported Rust version (#3082) ## Proposed Changes Set a minimum supported Rust version (MSRV) in the `Cargo.toml` for the Lighthouse binary so that attempts to compile it with an outdated compiler fail immediately with a clear error. To ensure that the codebase builds with the MSRV I've also added a Github actions job that runs `cargo check` using the MSRV extracted from `Cargo.toml`. This will force us to keep it up to date. I opted to use `cargo check` rather than Clippy because Clippy frequently introduces new lints that we adopt, so our MSRV for Clippy is usually the most recent Rust version, while the MSRV for building Lighthouse is older.
2022-03-17 03:33:29 +00:00
"cargo-vendor",
bors: require slasher and syncing sim tests (#3645) ## Issue Addressed I noticed that [this build](https://github.com/sigp/lighthouse/actions/runs/3269950873/jobs/5378036501) wasn't marked failed by Bors when the `syncing-simulator-ubuntu` job failed. This is because that job is absent from the `bors.toml` config. ## Proposed Changes Add missing jobs to Bors config so that they are required: - `syncing-simulator-ubuntu` - `slasher-tests` - `disallowed-from-async-lint` The `disallowed-from-async-lint` was previously allowed to fail because it was considered beta, but I think it's stable enough now we may as well require it.
2022-10-19 22:55:50 +00:00
"check-msrv",
"slasher-tests",
"syncing-simulator-ubuntu",
"disallowed-from-async-lint"
Remove macos tests (#1687) ## Issue Addressed N/A ## Proposed Changes Remove the MacOs tests. They routinely fail, causing bors to retry and slowing down the whole merge process. ## Additional Info N/A Co-authored-by: Michael Sproul <michael@sigmaprime.io>
2020-09-30 01:27:36 +00:00
]
Add bors configuration (#1340) Melded together stuff from https://github.com/sigp/lighthouse/pull/1326 and https://github.com/sigp/lighthouse/pull/1337. Note that I've reduced the timeout to 2 hours to save some time in case the build gets stuck. Co-authored-by: Michael Sproul <michael@sigmaprime.io>
2020-07-07 06:31:20 +00:00
use_squash_merge = true
Increase Bors timeout, refine target-branch-check (#3035) ## Issue Addressed Timeouts due to Windows builds running for 2h 20m. ## Proposed Changes * Increase Bors timeout to 3h * Refine the target branch check so that it will pass when we make PRs to feature branches. This is just an extra change I've been meaning to sneak in for a while. ## Additional Info * I think it would also be cool to try caching for CI again, but that's a separate issue and we'll still need the long timeout on a cache miss.
2022-02-21 23:21:03 +00:00
timeout_sec = 10800
Check that pull requests target unstable (#2187) Attempt to prevent accidental merges to `stable` due to GitHub's default behaviour of opening PRs against it. I've intentionally opened this PR against `stable` to test the functionality ;)
2021-02-09 02:00:53 +00:00
pr_status = ["license/cla", "target-branch-check"]
Reference in New Issue Copy Permalink