chore(ci): avoid duplicate LoongSuite push runs#201
Open
sipercai wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Limit generated LoongSuite CI workflows so
pushruns only formain, while keepingpull_requestandmerge_grouptriggers.This avoids running a duplicate full LoongSuite matrix when a same-repository PR branch receives a new commit. PR updates remain covered by the
pull_requesttrigger.This also changes LoongSuite lint/test workflows from static per-package jobs with job-level skips to detector-driven dynamic matrices:
loongsuite_changescomputesfull,packages,degraded, and a dynamic matrix.mainpush, shared CI files, unknown packages, and degraded detector paths still run the full LoongSuite matrix.Fixes # (none)
Branch Protection Note
This PR intentionally changes the LoongSuite lint/test check shape.
Before merging, branch protection / merge queue required checks should be updated from old per-package LoongSuite lint/test checks, for example:
LoongSuite loongsuite-instrumentation-google-adkLoongSuite loongsuite-instrumentation-google-adk-oldest 3.10 UbuntuLoongSuite ...lint/test matrix checksto the new aggregate checks:
LoongSuite Lint 0 resultLoongSuite Test 0 resultThe existing LoongSuite misc checks can remain separate.
Type of change
How Has This Been Tested?
tox -e generate-workflowstox -c tox-loongsuite.ini -e py311-test-detect-loongsuite-changestox -e precommitgit diff --checkpython $PIPELINE_SKILL_DIR/scripts/check_loongsuite_pr_readiness.py --repo .loongsuite-instrumentation-google-adk: 1 lint job, 10 test jobsloongsuite-instrumentation-crewai: 1 lint job, 4 test jobsloongsuite-instrumentation-litellm: 1 lint job, 4 test jobsDoes This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.
Changelog and documentation updates are not included because this is a CI-only workflow change.