Skip to content

[TEST] No-trigger test: .md file change - #3009

Open
rashmigottipati wants to merge 6 commits into
mainfrom
test-no-trigger-md-change
Open

[TEST] No-trigger test: .md file change#3009
rashmigottipati wants to merge 6 commits into
mainfrom
test-no-trigger-md-change

Conversation

@rashmigottipati

@rashmigottipati rashmigottipati commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Test PR to verify if_changed exclusions

This PR modifies a .md file which should NOT TRIGGER transformers tests (excluded).

Part of verifying the if_changed include/exclude pattern in #2983

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 84695f2b-4212-4fb3-ad8e-a2df8f5ae46e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mergify mergify Bot added documentation Improvements or additions to documentation two-reviews When a PR requires two reviews labels Aug 7, 2026
@mergify

mergify Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 2 of 2 protections blocking · waiting on 👀 reviews

Protection Waiting on
🔴 Require one maintainer review 👀 reviews
🔴 Require two reviews 👀 reviews

🔴 Require one maintainer review

Waiting for any of

  • approved-reviews-by=HDCharles
  • approved-reviews-by=brian-dellabetta
  • approved-reviews-by=dsikka
  • approved-reviews-by=kylesayrs
  • approved-reviews-by=yiliu30
This rule is failing.

All PRs must have at least one approving review from a maintainer before merging.

  • any of:
    • approved-reviews-by=HDCharles
    • approved-reviews-by=brian-dellabetta
    • approved-reviews-by=dsikka
    • approved-reviews-by=kylesayrs
    • approved-reviews-by=yiliu30
  • #changes-requested-reviews-by = 0

🔴 Require two reviews

Waiting for

  • #approved-reviews-by >= 2
This rule is failing.

PRs labelled "two-reviews" must have at least two approving reviews before merging.

  • #approved-reviews-by >= 2
  • #changes-requested-reviews-by = 0

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the Buildkite pipeline configurations (gpu-tests-H100.yml and gpu-tests-L4.yml) to split the "Transformers Tests" step into two separate steps: one that always runs on branch pushes, and another that runs conditionally on pull requests when relevant files are modified. Feedback on these changes highlights critical Buildkite syntax issues in both YAML files. Specifically, build.pull_request evaluates to false rather than null on branch builds, which breaks the conditional logic. Additionally, Buildkite's if_changed attribute does not support nested include and exclude keys; instead, a flat list of glob patterns using the ! prefix should be used for exclusions to prevent pipeline parsing errors.

Comment thread .buildkite/gpu-tests/gpu-tests-H100.yml Outdated
- label: ":mag: Detect changes for Transformers Tests"
# Transformers tests - always run on branch pushes
- label: ":mag: Transformers Tests (branch)"
if: build.pull_request == null

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

In Buildkite, build.pull_request evaluates to false (boolean) when the build is not triggered by a pull request, rather than null. Using build.pull_request == null will evaluate to false on branch builds, preventing this step from running.

Please use build.pull_request == false instead.

    if: build.pull_request == false

Comment thread .buildkite/gpu-tests/gpu-tests-H100.yml Outdated
Comment thread .buildkite/gpu-tests/gpu-tests-H100.yml
Comment thread .buildkite/gpu-tests/gpu-tests-L4.yml Outdated
- label: ":mag: Detect changes for Transformers Tests"
# Transformers tests - always run on branch pushes
- label: ":mag: Transformers Tests (branch)"
if: build.pull_request == null

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

In Buildkite, build.pull_request evaluates to false (boolean) when the build is not triggered by a pull request, rather than null. Using build.pull_request == null will evaluate to false on branch builds, preventing this step from running.

Please use build.pull_request == false instead.

    if: build.pull_request == false

Comment thread .buildkite/gpu-tests/gpu-tests-L4.yml Outdated

# Transformers tests - conditional on PRs when relevant paths changed
- label: ":mag: Transformers Tests (PR)"
if: build.pull_request != null

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

In Buildkite, build.pull_request evaluates to false (boolean) when the build is not triggered by a pull request. Using build.pull_request != null will evaluate to true on branch builds (since false != null is true), causing this PR-only step to run on branch pushes as well.

Please use build.pull_request != false instead.

    if: build.pull_request != false

Comment on lines +90 to +101
if_changed:
include:
- "src/**"
- "tests/**"
- "setup.py"
- "MANIFEST.in"
- ".buildkite/gpu-tests/**"
exclude:
- "tests/e2e/**"
- "tests/lmeval/**"
- "tests/examples/**"
- "**/*.md"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Buildkite's native if_changed attribute expects a single glob pattern or an array of glob patterns. It does not support nested include and exclude keys, which will result in a pipeline parsing error.

To exclude specific paths, you can use the ! prefix directly within a flat list of glob patterns.

    if_changed:
      - "src/**"
      - "tests/**"
      - "setup.py"
      - "MANIFEST.in"
      - ".buildkite/gpu-tests/**"
      - "!tests/e2e/**"
      - "!tests/lmeval/**"
      - "!tests/examples/**"
      - "!**/*.md"

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

@rashmigottipati
rashmigottipati force-pushed the test-no-trigger-md-change branch from 42c18ca to d27327f Compare August 14, 2026 03:08
Signed-off-by: Rashmi Gottipati <rgottipa@redhat.com>
Signed-off-by: Rashmi Gottipati <rgottipa@redhat.com>
Signed-off-by: Rashmi Gottipati <rgottipa@redhat.com>
Signed-off-by: Rashmi Gottipati <rgottipa@redhat.com>
… regex operator

Signed-off-by: Rashmi Gottipati <rgottipa@redhat.com>
@rashmigottipati
rashmigottipati force-pushed the test-no-trigger-md-change branch from d27327f to 4fdd529 Compare August 14, 2026 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation two-reviews When a PR requires two reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant