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

mzbuild: Don't try to build on non-builder CI machines #29681

Merged
merged 1 commit into from
Sep 21, 2024

Conversation

def-
Copy link
Contributor

@def- def- commented Sep 20, 2024

They won't succeed anyway, better to fail the test than time out while uselessly building. Seen in https://buildkite.com/materialize/test/builds/90870

Also retry longer (~1 minute) and not just with a 1s sleep inbetween

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

assert max_retries > 0

deps_to_build = [dep for dep in self if not dep.try_pull(max_retries)]
deps_to_build = [
dep for dep in self if not dep.publish or dep.try_pull(max_retries)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to try to pull an image that we never publish, becomes slower with this PR

print(
f"+++ Expected builds to be available, the build probably failed, so not proceeding: {expected_deps}"
)
sys.exit(5)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unique return code, so far not used, but in the future we could do auto-retries in mkpipeline.py based on it.

@def- def- force-pushed the pr-build-ci branch 2 times, most recently from e929e60 to 6c05954 Compare September 21, 2024 06:35
@def- def- requested a review from a team as a code owner September 21, 2024 06:35
They won't succeed anyway, better to fail the test than time out while
uselessly building. Seen in https://buildkite.com/materialize/test/builds/90870

Also retry longer (~1 minute) and not just with a 1s sleep inbetween
@def- def- merged commit 00edd5d into MaterializeInc:main Sep 21, 2024
75 checks passed
@def- def- deleted the pr-build-ci branch September 21, 2024 09:57
@github-actions github-actions bot locked and limited conversation to collaborators Sep 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants