Skip to content

ci.yaml validation fails with "generateGitHubToken failed" #94635

Closed
flutter/cocoon
#1524

Description

@gspencergoog

I saw one instance of this error when pushing a change to #94616 (doesn't include ci.yaml changes). I can't repro it.

ci_yaml_fail

cc @CaseyHillers

Activity

  1. self-assigned this
    on Dec 6, 2021
  2. CaseyHillers commented on Dec 8, 2021

    @CaseyHillers
    Contributor

    https://cs.opensource.google/flutter/cocoon/+/main:app_dart/lib/src/service/config.dart;l=287-313;drc=c9a5c6d022f2067cd9d8bce52372e729d2901cbb somewhere here is failing to generate a string. I'm not sure it's the datastore related fields, and it may be due to the JwtBuilder timing out. I'll look into adding some debug logs to better understand where we're getting to.

  3. CaseyHillers commented on Dec 8, 2021

    @CaseyHillers
    Contributor

    Another instance - https://github.com/flutter/flutter/pull/89451/checks?check_run_id=4461162168

    Based on the logs, this seems to happen a few times a day

  4. changed the title [-]ci.yaml check sometimes fails with null check failure[/-] [+]ci.yaml validation fails with "generateGitHubToken failed"[/+] on Dec 10, 2021
  5. CaseyHillers commented on Dec 14, 2021

    @CaseyHillers
    Contributor

    The issue is we're being rate limited (so you'll see this in short bursts)

    {
      "documentation_url": "https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits",
      "message": "You have exceeded a secondary rate limit. Please wait a few minutes before you try again."
    }
    
  6. gspencergoog commented on Dec 14, 2021

    @gspencergoog
    ContributorAuthor

    Ahh, that makes sense.

  7. CaseyHillers commented on Dec 15, 2021

    @CaseyHillers
    Contributor

    I'm deploying a new release now. Should be fixed in ~10 minutes.

  8. github-actions commented on Dec 29, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  9. locked as resolved and limited conversation to collaborators on Dec 29, 2021
  10. moved this from Verified to To be archived in [DEPRECATED] Infra Ticket Queueon Jun 26, 2023
  11. added
    P0Critical issues such as a build break or regression
    and removed on Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P0Critical issues such as a build break or regressionteam-infraOwned by Infrastructure team

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions