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

Bit more verbose output from the switchboard task #1677

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

zregvart
Copy link
Member

@zregvart zregvart commented Dec 2, 2024

Makes it easier to debug eventual issues and makes it easier to fine tune expressions.

Also a fix in c974eed to search only merged pull requests. I could have done a separate pull request, but then I'd need to rebase this so this was easier

@zregvart zregvart marked this pull request as draft December 2, 2024 15:57
@zregvart zregvart force-pushed the pr/verbose-switchboard branch from c974eed to f2d171b Compare December 3, 2024 10:57
@zregvart zregvart marked this pull request as ready for review December 20, 2024 11:20
@zregvart zregvart requested a review from a team as a code owner December 20, 2024 11:20
@zregvart zregvart force-pushed the pr/verbose-switchboard branch from f2d171b to 27d1120 Compare December 20, 2024 11:20
Copy link
Contributor

@chmeliik chmeliik left a comment

Choose a reason for hiding this comment

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

Due to rebasing the same revision that triggered the pipeline for one
pull request can occur in other pull requests.

I'm not sure I understand how this happens. Would the other pull requests need to have been merged already in order for this to happen?

@zregvart
Copy link
Member Author

I'm not sure I understand how this happens. Would the other pull requests need to have been merged already in order for this to happen?

It's an edge case when the same commit exists in two or more pull requests, for unmerged pull requests this can be when one pull request is based on another pull request. I had this issue in the pipeline triggered on push, probably not as frequent for unmerged pull requests.

Copy link
Contributor

@chmeliik chmeliik left a comment

Choose a reason for hiding this comment

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

It's an edge case when the same commit exists in two or more pull requests, for unmerged pull requests this can be when one pull request is based on another pull request.

Ah, makes sense. LGTM

@zregvart zregvart added this pull request to the merge queue Dec 20, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 20, 2024
@zregvart
Copy link
Member Author

Hmm, the error from the task-switchboard is:

jq: error (at <stdin>:1): Cannot iterate over null (null)
[]

Makes it easier to debug eventual issues and makes it easier to fine
tune expressions.
Due to rebasing the same revision that triggered the pipeline for one
pull request can occur in other pull requests. With this not only the
first result from `gh search prs` is used, changes from all of them are
considered.

This means that some Tasks that might not need to run are still ran,
this should be acceptable given it guarantees that all Tasks that need
to run have ran.
@zregvart zregvart force-pushed the pr/verbose-switchboard branch from 27d1120 to 728b6f9 Compare December 20, 2024 14:06
@zregvart zregvart added this pull request to the merge queue Dec 20, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 20, 2024
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