Fraud Report Final Touches 🎉

[trajan0x]

Description

Tracking in: #1280 (comment)

• Implement some optimizations suggested in cmd/go: support compiling all tests without running golang/go#15513 (tbh, I'm not even sure if these do anything. Can re-evaluate)
• Re-enable pyroscope
• Fix codecov
• Get script to fail if any test fails (see here. Test fails, but actin passes just w/ lower coerage

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (feat/fraud-reports@6031092). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files

@@                   Coverage Diff                    @@
##             feat/fraud-reports       #1339   +/-   ##
========================================================
  Coverage                      ?   48.24479%           
========================================================
  Files                         ?         278           
  Lines                         ?       22305           
  Branches                      ?           0           
========================================================
  Hits                          ?       10761           
  Misses                        ?       10366           
  Partials                      ?        1178           

Flag	Coverage Δ
cctp-relayer	63.33333% <0.00000%> (?)
core	58.76250% <0.00000%> (?)
explorer	24.92882% <0.00000%> (?)
git-changes-action	53.94265% <0.00000%> (?)
omnirpc	53.19635% <0.00000%> (?)
promexporter	41.02564% <0.00000%> (?)
release-copier-action	19.33333% <0.00000%> (?)
scribe	51.47151% <0.00000%> (?)
tools	21.72452% <0.00000%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[trajan0x]

Explanation: Why the Script Didn't Stop on Errors

The provided script looped through each package and ran a series of commands on each package. If any command failed during this process, the script would simply continue to the next package in the list without stopping.

This behavior is due to the default nature of bash scripting. By default, a bash script won't terminate or exit just because a command inside it fails. Instead, it will continue executing subsequent commands.

If you want a bash script to exit immediately when a command fails, you need to add the set -e directive at the beginning of the script. The set -e directive instructs the shell to exit immediately if any command in the script returns a non-zero exit status (indicating failure).

Without the set -e directive, your script will continue running subsequent commands even if one of them fails, which is the behavior you observed.