The GitHub Actions job "Benchmarks" on texera.git/main has succeeded. Run started by GitHub user github-merge-queue[bot] (triggered by github-merge-queue[bot]).
Head commit for run: 3b39b75dd69989570cc4b5585368426ebeecfb12 / Xinyuan Lin <[email protected]> fix(deps, ci): bump setup-sbt and playwright (#9100) ### What changes were proposed in this PR? Nothing can merge into `main` right now. Three CI faults block it, and each fix needs the others to land first. ``` Before: Scala job -> sbt/setup-sbt v1.5.7 -> nested carabiner action not allowed -> fails at Set up job frontend job -> ubuntu-26.04 runner -> Playwright 1.59.1 has no Chromium -> fails at install merge group -> no runner within 45 min -> checks_timed_out, PR leaves the queue After: Scala job -> sbt/setup-sbt v1.5.12 -> every nested action allowed -> runs frontend job -> ubuntu-26.04 runner -> Playwright 1.64.1 installs Chromium -> runs merge group -> waits up to 360 min for runners -> merges ``` - **setup-sbt.** The ASF actions allowlist dropped the nested `carabiner-dev/actions/install/*` refs that `sbt/setup-sbt` v1.5.7 reaches, so every job that sets up sbt (`amber`, `amber-integration`, `platform`, `platform-integration`, `Bench`) has died at *Set up job* since 2026-10-19. This moves all 9 call sites to v1.5.12, whose whole chain is allowed. The action's inputs did not change. - **Playwright.** `ubuntu-latest` now resolves to the Ubuntu 26.04 image, where Playwright 1.59.1 refuses to install Chromium ("Playwright does not support chromium on ubuntu26.04-x64"), so the ubuntu frontend leg fails before any test runs. This bumps `playwright` to 1.64.1, which supports 26.04. - **Merge queue timeout.** The queue ejects an entry whose required checks have not reported within `check_response_timeout_minutes`, which is 45. ASF's shared runners are backed up well past that: in the last merge group, *Validate PR title*, a 2-second job, waited 110 minutes for a runner. This raises the limit to 360 minutes, as DataFusion did in apache/datafusion#26293. `Required Checks` stays red without both version bumps, and no PR gets through the queue without the higher limit, so all three go in one PR. ### Any related issues, documentation, discussions? Closes #9095. ### How was this PR tested? Every changed file parses: ``` python -I -c "import sys, yaml; [yaml.safe_load(open(f)) for f in sys.argv[1:]]" .asf.yaml .github/workflows/benchmarks.yml .github/workflows/build-and-push-images.yml .github/workflows/build.yml .github/workflows/dependency-graph.yml ``` Walking the `uses:` chain under `sbt/setup-sbt@ecad189` (v1.5.12) reaches `ampel/verify@32587e8`, `install/ampel@d6d91c5`, `install/download-and-verify@2fec8bd` and `install/ampel-bootstrap@16009dc`, and all four are in `apache/infrastructure-actions`' `approved_patterns.yml` as of 2026-10-23. Under v1.5.7, `install/ampel@2fec8bd`, `install/download-and-verify@16009dc` and `install/ampel-bootstrap@619a474` are not. The rest is CI. The labeler applies `ci` for `.github/**`, which runs every stack that sets up sbt, the frontend legs, and `Bench`. On this PR's previous head every job passed except the ubuntu frontend leg, which landed on ubuntu-26.04 and failed at the Playwright install. The new timeout only shows once this is merged. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Ian Maxon <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/40038889052 With regards, GitHub Actions via GitBox
