Skip to content

Run Results regression on toolchain PR path changes - #64

Merged
jmjava merged 1 commit into
mainfrom
cursor/trigger-results-pr-paths-fc5f
Sep 16, 2026
Merged

jmjava merged 1 commit into
mainfrom
cursor/trigger-results-pr-paths-fc5f

Conversation

@jmjava

@jmjava jmjava commented Sep 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • PR #62 already landed Java 21, PHP 8.3 + dom, and Go on the scheduled Results workflow
  • that workflow was still schedule/manual only, which is why the missing JDK hid until Wednesday
  • run the same strict Results job when this workflow or the Results/lang installers change
  • lock the new trigger with static acceptance assertions

Why this is the live check

This path filter starts results-regression on this PR, so the first JDK 21 Results run does not have to wait for next week's cron.

Companion

The M17 aggregate already includes this trigger in #63.

Verification

  • libs/tekton-dag-common/tests/test_m17_results_automation.py: 2 passed
  • bash scripts/run-regression-agent.sh: regression exit code: 0 (local-only; no kubectl). Maven compiled baggage-spring-boot-starter with JDK 21, PHPUnit 19/19, operator Go tests passed
  • GitHub will start the 180-minute Results job on this PR
Open in Web Open in Cursor 

Schedule-only triggering hid the missing JDK 21 until Wednesday. Also run
the strict Results workflow when this file or the Results/lang installers
change so the next toolchain gap fails on the PR.

Co-authored-by: jmjava <jmjava@gmail.com>
@jmjava
jmjava merged commit 7da0b82 into main Sep 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants