Skip to content

generate_gradle_lockfiles is not run on CI #142475

Closed

Description

@bartekpacia

I think we should run generate_gradle_lockfiles on (pre/post – idk)submit tests.

Problems

Sometimes, regenerating gradle lockfiles results in git changes. I don't think that it should be happening, i.e. the running:

find . -type d -name 'android' | dart dev/tools/bin/generate_gradle_lockfiles.dart

should result in no git changes.

Sometimes, it fails altogether (often on different project - look at the logs carefully):

crash_logs_1.txt

crash_logs_2.txt

I didn't debug thse crashes further but usually re-reunning results in a different failure.

Activity

  1. added
    in triagePresently being triaged by the triage team
    platform-androidAndroid applications specifically
    toolAffects the "flutter" command-line tool. See also t: labels.
    team-toolOwned by Flutter Tool team
    and removed
    in triagePresently being triaged by the triage team
    on Jan 30, 2024
  2. added
    P2Important issues not at the top of the work list
    triaged-toolTriaged by Flutter Tool team
    on Jan 30, 2024
  3. removed their assignment
    on May 30, 2024
  4. christopherfujino commented on May 30, 2024

    @christopherfujino
    Contributor

    FYI @gmackall, if you end up running the script from the pub roller bot

  5. github-actions commented on Sep 9, 2024

    @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.

  6. locked as resolved and limited conversation to collaborators on Sep 9, 2024
  7. christopherfujino commented on Sep 9, 2024

    @christopherfujino
    Contributor

    Re-opening as it is still not working.

  8. unlocked this conversation on Sep 10, 2024
  9. github-actions commented on Oct 18, 2024

    @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.

  10. locked as resolved and limited conversation to collaborators on Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P2Important issues not at the top of the work listplatform-androidAndroid applications specificallyteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions