Skip to content

Conversation

@nehalvpatel
Copy link
Contributor

According to flutter/flutter#100081, this should fix ci.yaml validation errors.

Pre-launch Checklist

  • I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
  • I read the [Tree Hygiene] wiki page, which explains my responsibilities.
  • I read the [Flutter Style Guide] recently, and have followed its advice.
  • I signed the [CLA].
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is [test-exempt].
  • All existing and new tests are passing.

}

/// Finds all check suites that are associated with a given git [ref].
Future<Stream<github.CheckSuite>> listCheckSuitesForRef(
Copy link
Contributor

Choose a reason for hiding this comment

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

Tests for this method?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can you suggest how I should test this? I added a test for searchIssuesAndPRs to validate that it encodes the query properly, but for listCheckSuitesForRef and getPullRequest I can't think of anything since they just forward the call unconditionally.

@nehalvpatel
Copy link
Contributor Author

Setting to draft while I fix the scheduler test.

@nehalvpatel nehalvpatel marked this pull request as draft January 19, 2023 19:36
@nehalvpatel nehalvpatel marked this pull request as ready for review January 19, 2023 22:50
Copy link
Contributor

@godofredoc godofredoc left a comment

Choose a reason for hiding this comment

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

Can we manually release a version to test this change?

@nehalvpatel
Copy link
Contributor Author

Can we manually release a version to test this change?

I was able to deploy it and successfully perform a ci.yaml validation rerun on flutter/flutter#118690. 😄

The only hitch is that previously failed webhook events which requested to rerun ci.yaml keep being retried. The problem is that the PRs associated are already closed or have had a new commit, which invalidates the check suite. This causes the event processing to fail and is causing looping retries. I think we might have to drain those events.

@godofredoc
Copy link
Contributor

I think we might have to drain those events.

You can take a look at the subscription, it may already be configured to auto drop messages older than 24h

@nehalvpatel
Copy link
Contributor Author

Looks like it is set to 7 days.

Screenshot 2023-01-20 at 11 32 24 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants