Skip to content

Conversation

grooverdan
Copy link
Member

There where some failures. Might be a divering implemnation on output but eitherway, sha256sum can check directly without needed to do the comparision in bash.

Adjust path so the tarball can be found by sha256sum.

There where some failures. Might be a divering implemnation on
output but eitherway, sha256sum can check directly without needed
to do the comparision in bash.

Adjust path so the tarball can be found by sha256sum.
@RazvanLiviuVarzaru RazvanLiviuVarzaru self-requested a review July 25, 2024 06:57
Copy link
Collaborator

@RazvanLiviuVarzaru RazvanLiviuVarzaru left a comment

Choose a reason for hiding this comment

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

This change affects all builders , looks ok but after merge needs a regression test on DEV .
I suggest printing checksum's in standard output so we can track at runtime what is really happening.

@fauust
Copy link
Collaborator

fauust commented Jul 25, 2024

Looks OK but yes, it needs testing before merge in prod since it will impact every builder.

Copy link
Collaborator

@RazvanLiviuVarzaru RazvanLiviuVarzaru left a comment

Choose a reason for hiding this comment

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

Thanks for the addition Daniel,
after this merge let's schedule a full run on Dev and watch closely how all builders behave.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants