Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip incremental-mutants job for main #3158

Merged
merged 2 commits into from
Jul 8, 2024

Conversation

dunxen
Copy link
Contributor

@dunxen dunxen commented Jul 4, 2024

There is no diff when running against main, so we skip incremental-mutants. Before this commit, we'd get Error: Failed to parse diff: Line 1: Error while parsing: as the diff file was empty.

There is no diff when running against main, so we skip incremental-mutants.
Before this commit, we'd get `Error: Failed to parse diff: Line 1: Error while parsing:`
as the diff file was empty.
@@ -250,6 +250,7 @@ jobs:

incremental-mutants:
runs-on: ubuntu-latest
if: github.ref_name != 'main' # `main` has no diff with itself
Copy link
Contributor

Choose a reason for hiding this comment

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

Makes sense, but would the 'real' solution be to check whether the diff is empty and always early-exit if so?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah it makes the expression a bit more complex and I had considered it. Or it requires an extra step before. I'll see how it can fit in this expression.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, don't bother if it's too much hassle I think, just wondered if we might into run similar cases where it wouldn't be main == main.

Copy link
Contributor

@tnull tnull left a comment

Choose a reason for hiding this comment

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

Going ahead and merging this

@tnull tnull merged commit 0c3196c into lightningdevkit:main Jul 8, 2024
16 of 17 checks passed
@dunxen
Copy link
Contributor Author

dunxen commented Jul 8, 2024

Going ahead and merging this

No worries. I was about to say we can look at an expression later. But for now I don't think it will cause issues with other refs even if people open PRs from other remote "main"s

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.

None yet

2 participants