Skip to content

ci.yaml changes aren't applied before tests run post-submit #95037

Closed

Description

@Hixie

A PR like #93086 that makes significant changes to ci.yaml will pass presubmits but fail postsubmits because of some delay in the infrastructure.

The scheduler should avoid scheduling tests when there's a pending infrastructure change that needs to roll out for the tests to pass.

Activity

  1. CaseyHillers commented on Dec 10, 2021

    @CaseyHillers
    Contributor

    This is blocked on #81795

    Once that's implemented, we'll roll out the cocoon scheduler to be used by all the Flutter repos instead of the LUCI scheduler. ETA is migration will be complete by end of January.

  2. self-assigned this
    on Dec 10, 2021
  3. added
    P1High-priority issues at the top of the work list
    and removed on Mar 22, 2022
  4. godofredoc commented on Mar 22, 2022

    @godofredoc
    Contributor

    Moving as P3, this is a nice to have but it is not currently blocking anything.

  5. CaseyHillers commented on Jul 28, 2022

    @CaseyHillers
    Contributor

    Cocoon scheduler migration is complete, and everything should be tested based on what's in the ci.yaml for that repo.

  6. github-actions commented on Aug 11, 2022

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

  7. locked as resolved and limited conversation to collaborators on Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listteam-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions