test: fix CI failure caused by newly updated baseline #328
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
fasttime
added
the
accepted
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.
Prerequisites checklist
What is the purpose of this pull request?
In this PR, I've fixed a CI failure caused by the newly updated baseline.
In PR #326, the
color-mixfunction's baseline was changed, which caused CI to fail:https://github.com/eslint/css/actions/runs/19428945309/job/55582966958
Oddly, this CI failure wasn't detected in #326 itself because the test workflow didn't run in the auto-generated PR:
What changes did you make? (Give an overview)
In this PR, I've fixed a CI failure caused by the newly updated baseline.
I've replaced the
color-mixfunction with thelight-darkfunction to preserve the test case's original intent as much as possible.Related Issues
Ref: #326
Is there anything you'd like reviewers to focus on?
Looking through the auto-generated PRs in the history, it seems that none of them run the test workflow. They only run the following three cases:
I think we need to update some setup so the CI workflow can run on auto-generated PRs. However, I'm not sure what the best approach is, since this may not be fixable at the code level and might require changes to the GitHub repository settings.
FYI, auto-generated
release-pleasePRs, as well as repositories containing Markdown, CSS, JSON, and others, are also affected.