Skip to content

release-24.1: workflows: double GitHub Actions Essential CI timeouts #144331

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

Conversation

rickystewart
Copy link
Collaborator

@rickystewart rickystewart commented Apr 12, 2025

Backport 1/1 commits from #144323 on behalf of @rickystewart.

/cc @cockroachdb/release


Due to EngFlow load, we're seeing timeouts sporadically. Increase timeouts (we're basically doubling everything, but examples_orms is going from 40 to 120 minutes to make things simpler.

Epic: DEVINF-1424
Release note: None


Release justification: Non-production code changes

Due to EngFlow load, we're seeing timeouts sporadically. Increase
timeouts (we're basically doubling everything, but `examples_orms` is
going from 40 to 120 minutes to make things simpler.

Epic: DEVINF-1424
Release note: None
@rickystewart rickystewart force-pushed the blathers/backport-release-24.1-144323 branch from 87e0574 to 696dd7a Compare April 12, 2025 00:07
@rickystewart rickystewart requested a review from a team as a code owner April 12, 2025 00:07
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Apr 12, 2025
Copy link

blathers-crl bot commented Apr 12, 2025

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues
    or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport
    policy
    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot requested a review from celiala April 12, 2025 00:07
@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Apr 12, 2025
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rickystewart rickystewart merged commit dd9f078 into cockroachdb:release-24.1 Apr 14, 2025
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. target-release-24.1.19
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants