hello-stephen opened a new pull request, #395: URL: https://github.com/apache/doris-thirdparty/pull/395
## Problem The `build` matrix job includes `macOS-x86_64` running on `macos-13`. GitHub Actions `macos-13` (Intel Mac) runners have become increasingly scarce and can queue for up to **24 hours** before timing out. This caused a cascade of failures in the `build-4.0.yml` and `build.yml` workflows: 1. `macos-13` runner waits 24h → times out → entire `build` matrix result = `failure` 2. `update-docker` condition requires `build.result == 'success'` → **skipped** 3. `success` job depends on `update-docker` → **skipped** 4. `failure` job has `if: failure()` but `update-docker` was skipped (not failed), so with GitHub Actions' default skip-propagation, `failure` also **does not run** 5. Release status is stuck at `BUILDING` indefinitely; Docker image is never updated This was observed in run [#26616785582](https://github.com/apache/doris-thirdparty/actions/runs/26616785582) where the `macOS-x86_64` build waited exactly 24h0m0s and the Docker image has not been refreshed since May 29. ## Fix Three minimal changes to `build-4.0.yml` and `build.yml`: 1. **`fail-fast: false`** on the build matrix — a macOS timeout no longer cancels the in-progress `arm64` and `Linux` builds. 2. **`continue-on-error: true`** on the `macOS-x86_64` entry — when the Intel Mac runner is unavailable or times out, the overall `build` job result remains `success`, allowing `update-docker` to proceed. The Docker image only needs the Linux binary anyway. 3. **`if: always() && failure()`** on the `failure` job — ensures the failure-notification job always evaluates its condition, even when `update-docker` was skipped rather than failed, so the release status is correctly updated to `FAILURE` instead of being left at `BUILDING`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
