You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On each PR, build twice the firmware for each operating system, removing the crypto_data directory and copying the sample_crypto_data between the two builds and ensure that the hashes remain the same. This should block PR and tell us that we have something wrong.
On merge, instead of checking the hashes against a reference, this should generate the new hashes and text outputs and automatically push a new commit with the this as a reference.
Actual Behavior
Currently the two behaviors are mixed up and don't allow us to stop when a build is actually not reproducible.
Steps to Reproduce the Problem
N/A
Specifications
Version: N/A
Platform: N/A
The text was updated successfully, but these errors were encountered:
Expected Behavior
We should have 2 different workflows:
crypto_data
directory and copying thesample_crypto_data
between the two builds and ensure that the hashes remain the same. This should block PR and tell us that we have something wrong.Actual Behavior
Currently the two behaviors are mixed up and don't allow us to stop when a build is actually not reproducible.
Steps to Reproduce the Problem
N/A
Specifications
The text was updated successfully, but these errors were encountered: