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

Move postsubmit build scheduling from LUCI to cocoon #92300

Closed
19 tasks done
godofredoc opened this issue Oct 22, 2021 · 5 comments
Closed
19 tasks done

Move postsubmit build scheduling from LUCI to cocoon #92300

godofredoc opened this issue Oct 22, 2021 · 5 comments
Assignees
Labels
from: postmortem Issues identified as part of a postmortem team-infra Owned by Infrastructure team

Comments

@godofredoc
Copy link
Contributor

godofredoc commented Oct 22, 2021

This will allow to remove the current 45 minutes propagation time.

Migration

Features

@godofredoc godofredoc added team-infra Owned by Infrastructure team from: postmortem Issues identified as part of a postmortem postmortem labels Oct 22, 2021
@CaseyHillers
Copy link
Contributor

This is blocked on the scheduler supporting postsubmit triggers (tracked in #81795). Once that is complete, there will be a migration plan to move tests from LUCI to Cocoon.

@CaseyHillers
Copy link
Contributor

The migration ran into a blocker as a few DeviceLab tasks checkout Cocoon as soon as the task starts, and flutter/flutter takes ~30 seconds to mirror. This was causing #100866

I have a few ideas:

  1. Move the dependencies downloads and checks to being the first step (this unblocks the current steps, but causes race conditions down the line)
  2. Add longer retries to the source checkouts (a minute would suffice). The engine gclient can retry up to 2 hours
  3. Separate the scheduling logic to be triggered on the git-on-borg mirror (more complicated)

@keyonghan
Copy link
Contributor

Blocker #107599 before migrating non-bringup targets.

@keyonghan
Copy link
Contributor

Now everything is in cocoon.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
from: postmortem Issues identified as part of a postmortem team-infra Owned by Infrastructure team
Projects
None yet
Development

No branches or pull requests

4 participants