Add build-success marker job to ci.yml

[findepi]

Add a new build-success job in the main CI GitHub Actions workflow. This job should pass when the whole workflow passes and should fail otherwise.

Summary by Sourcery

Add a build-success marker job to the main CI workflow to ensure the overall pipeline status reflects failures of any individual job, and update tests to verify its configuration

New Features:

• Add a build-success job to the GitHub Actions CI workflow that aggregates the results of all other jobs and fails if any job failed

CI:

• Introduce the build-success job with an always-running condition and dependencies on all existing CI jobs
• Implement a 'Check results' step that verifies each dependent job succeeded or was skipped

Tests:

• Add a TestCiWorkflow test to validate the build-success job’s dependencies and generated run script

[sourcery-ai]

Reviewer's Guide

This PR adds a new build-success sentinel job to the main GitHub Actions CI workflow that always runs after all other jobs, checks each preceding job’s result, and includes a unit test in TestCiWorkflow to verify its dependencies and script configuration.

File-Level Changes

Change	Details	Files
Add build-success job to CI workflow	Configure build-success job in ci.yml with if: always() and needs on all existing jobs Add Check results step running a shell script to assert each dependency’s result is success or skipped	.github/workflows/ci.yml
Add test for build-success job in TestCiWorkflow	Implement testBuildSuccessDependencies to verify job presence, sorted-unique needs, and correct run script Introduce ifPresent helper method for optional YAML key retrieval	testing/trino-tests/src/test/java/io/trino/tests/ci/TestCiWorkflow.java

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[electrum]

I like this:

[Copilot]

Pull Request Overview

Adds a build-success marker job to the CI workflow that aggregates the results of all other jobs, ensuring the overall pipeline status accurately reflects individual job failures or cancellations. This provides a single, reliable status indicator for branch protection rules or other automation that depends on CI completion.

Key Changes:

• Introduces a build-success job that depends on all other CI jobs and validates their results
• Adds test coverage to verify the job's dependencies match all other jobs and validates the generated run script

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/ci.yml	Adds the build-success job with dependencies on all CI jobs and result validation logic
testing/trino-tests/src/test/java/io/trino/tests/ci/TestCiWorkflow.java	Adds test to verify build-success job dependencies and generated script match expectations

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[findepi]

CI

• setup action sometimes fails in Clearing up disk usage step #26943

[findepi]

CI

• Flaky test TestAlluxioFileSystem and TestAlluxioFileSystemExchangeManager #23596 (again)

[findepi]

CI

• Flaky test TestAlluxioFileSystem and TestAlluxioFileSystemExchangeManager #23596 (again)

[wendigo]

@findepi roll dice harder ;-)

[findepi]

CI

• Flaky test TestAlluxioFileSystem and TestAlluxioFileSystemExchangeManager #23596 (again)