use gh runners in ci - #5019
Conversation
3bf82db to
445ed56
Compare
d064f09 to
aa8e53a
Compare
There was a problem hiding this comment.
🔵 Human review recommended
It changes critical CI runner selection/caching infrastructure and also removes MSRV verification from PR checks without an evident replacement.
Pull request overview
This PR updates the project’s GitHub Actions configuration to use new runner labels / caching infrastructure and adjusts an IBC MASP-related E2E test timing to avoid shielding before conversions are published.
Changes:
- Switch multiple CI and docker workflows to new
namada-runners-*runners and update cache/role environment variables, including centralizing defaultRUSTFLAGS. - Extend the
ibc_token_inflationE2E test wait period to include an additional MASP epoch, and update the expected runtime budget ine2e.json. - Remove the MSRV verification job from the PR workflow and apply a minor formatting-only change in
release.yml.
File summaries
| File | Description |
|---|---|
| crates/tests/src/e2e/ibc_tests.rs | Wait longer before shielding to ensure MASP conversions exist, preventing permanent “undated note” behavior from invalidating inflation checks. |
| .github/workflows/scripts/e2e.json | Increase the scheduled budget for ibc_token_inflation to reflect the longer wait. |
| .github/workflows/release.yml | Formatting-only adjustment (no functional change). |
| .github/workflows/pr.yml | Removes the MSRV (cargo-msrv) job from PR checks. |
| .github/workflows/docker.yml | Moves the docker workflow to the new runner label. |
| .github/workflows/ci.yml | Migrates CI jobs to new runner labels and updates cache/role/env wiring; centralizes default RUSTFLAGS with targeted overrides. |
Review details
Suppressed comments (1)
.github/workflows/pr.yml:89
- The PR workflow no longer runs the MSRV verification job (cargo-msrv) and there doesn’t appear to be an equivalent check in other workflows; this reduces CI coverage for the project’s minimum supported Rust version and may allow MSRV regressions to merge unnoticed. If the intent is to disable it, consider adding an explicit rationale in the PR description and/or moving MSRV verification to another workflow (e.g., ci.yml or a scheduled workflow) rather than removing it entirely.
uses: actions-ecosystem/action-add-labels@v1
if: steps.semver.outcome == 'failure'
with:
labels: "breaking:api"
- Files reviewed: 5/6 changed files
- Comments generated: 0
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
sug0
left a comment
There was a problem hiding this comment.
I'd also get rid of the changelog stuff in ci
|
Queued — the merge queue status continues in this comment ↓. |
Merge Queue Status
This pull request spent 38 minutes 48 seconds in the queue, including 37 minutes 39 seconds running CI. Waiting for any of
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks
Failing checks:
HintYou may have to fix your CI before adding the pull request to the queue again. Requeued — the merge queue status continues in this comment ↓. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Hey @Fraccaman, your pull request has been dequeued due to the following reason: CHECKS_FAILED. |
aa8e53a to
f7736f3
Compare
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 59 minutes 28 seconds in the queue, including 57 minutes 33 seconds running CI. Required conditions to merge
|
use gh runners in ci (backport #5019)
Describe your changes
Checklist before merging
breaking::labelsnamada-docsreponamada-indexerornamada-masp-indexer, a corresponding PR is opened in that repo