ci: update test job runner from ubuntu-20.04 to ubuntu-22.04

[TimeToBuildBob]

Summary

• ubuntu-20.04 GitHub-hosted runners are no longer available, causing the Test job to wait indefinitely for a runner that never picks it up
• Updated to ubuntu-22.04 (current LTS, full runner availability)

Root Cause

Erik noticed in #156 that the Test CI job was stuck at "Waiting for a runner to pick up this job..." — the ubuntu-20.04 runner image has been removed by GitHub. The test job at line 232 of build.yml was the culprit.

Note

There are also several deprecated action versions in the workflow (actions/checkout@v2, actions/setup-java@v1, actions/upload-artifact@v3, actions/download-artifact@v3). Those were already being tracked separately and are a follow-up concern — this PR only fixes the blocking runner issue.

[greptile-apps]

Greptile Summary

This PR fixes the blocked test CI job by updating its runner from ubuntu-20.04 (no longer available on GitHub-hosted runners) to ubuntu-22.04.

• The diff is a single-line change to .github/workflows/build.yml, targeted precisely at the stalled runner label.
• The test job also uses actions/setup-java@v1, which is the oldest and most OS-coupled of the deprecated actions still present — worth addressing alongside or shortly after this fix to avoid a similar blockage on the new runner.

Confidence Score: 4/5

Safe to merge — the change is minimal and directly unblocks a stuck CI job.

The change is a single-line runner label swap that correctly addresses the root cause. The only open question is whether actions/setup-java@v1 will behave well on Ubuntu 22.04; if it doesn't, the test job will fail for a new reason rather than silently waiting forever, which is at least a visible failure.

.github/workflows/build.yml — the setup-java@v1 step at line 247 is worth a follow-up update.

Important Files Changed

Filename	Overview
.github/workflows/build.yml	Single-line change updating the test job runner from ubuntu-20.04 to ubuntu-22.04; the job also uses actions/setup-java@v1 which may need attention on the new OS.

Sequence Diagram

sequenceDiagram
    participant GH as GitHub Actions
    participant BR as build-rust
    participant T as test (ubuntu-22.04)
    participant E2E as test-e2e

    GH->>BR: trigger on push/PR
    BR->>BR: Build aw-server-rust JNI libs
    BR->>GH: upload artifact + cache jniLibs
    GH->>T: needs: [build-rust]
    T->>GH: restore jniLibs cache
    T->>T: "Set up JDK (setup-java@v1)"
    T->>T: make test
    T-->>GH: pass/fail
    GH->>E2E: needs: [build-rust]
    E2E->>E2E: run e2e tests

Loading

Comments Outside Diff (1)

1. .github/workflows/build.yml, line 247-249 (link)

   actions/setup-java@v1 compatibility with Ubuntu 22.04

   actions/setup-java@v1 is very old and predates Ubuntu 22.04 support. On the new runner it may fail to resolve and install the JDK correctly, since v1 relies on package sources that have changed in Ubuntu 22.04 — meaning the test job could still break, just for a different reason. The PR description notes these deprecated actions as a follow-up, but setup-java@v1 is the most likely of the bunch to cause an actual runtime failure on the upgraded OS. Bumping to at least actions/setup-java@v3 (which requires adding distribution: 'temurin') is the safe path forward.

_{Reviews (1): Last reviewed commit: "ci: update test job runner from ubuntu-2..." | Re-trigger Greptile}