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

Integration test improvements #2858

Merged
merged 11 commits into from
Mar 7, 2024
Prev Previous commit
Next Next commit
fix sentry send event
  • Loading branch information
hubertdeng123 committed Mar 6, 2024
commit 07c059e46ebaaf75fd64a78e8d465d8d0cf101d3
5 changes: 3 additions & 2 deletions _integration-test/run.sh
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,12 @@ teardown() {
DID_TEAR_DOWN=1

if [ "$1" != "EXIT" ]; then
set +x
error_msg="An error occurred, caught SIG$1 on line $2"
echo "$error_msg"
dsn="https://[email protected]/6627632"
sentry_cli="docker run --rm -v /tmp:/work -e SENTRY_DSN=$dsn getsentry/sentry-cli"
$sentry_cli send-event -m "$error_msg" --logfile "$log_file"
local sentry_cli="docker run --rm -v $(pwd):/work -e SENTRY_DSN=$dsn getsentry/sentry-cli"
Copy link
Contributor

Choose a reason for hiding this comment

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

Odd to me that we set REPORT_ISSUES=0 above, but then send an envelope here anyway? Maybe I am misunderstanding something, but why would we not just do REPORT_ISSUES=1, and maybe figure out some way to configure it to send to an "integration tests" or similar project on our actual dogfood instance?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure, I can incorporate this into the existing logic for REPORT_ISSUES I believe.

$sentry_cli send-event -m "$error_msg" --logfile $log_file
fi

echo "Tearing down ..."
Expand Down
Loading