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

fix: upload fuzz output to s3 when test fails #4694

Merged
merged 3 commits into from
Aug 8, 2024
Merged

fix: upload fuzz output to s3 when test fails #4694

merged 3 commits into from
Aug 8, 2024

Conversation

jouho
Copy link
Contributor

@jouho jouho commented Aug 7, 2024

Resolved issues:

There was a mistake in #4678
The output is being uploaded to s3 when the test is "negative" (e.g. running s2n_memory_leak_negative_test.c)
Instead it should be uploaded when the test actually fails.

Description of changes:

The output will be uploaded to s3 when the test fails, not when the test is negative

Call-outs:

Testing:

Test run with the new batch build: link to CodeBuild job

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions github-actions bot added the s2n-core team label Aug 7, 2024
@jouho jouho marked this pull request as ready for review August 7, 2024 22:34
fi

# Store generated output files in the S3 bucket.
if [ "$ARTIFACT_UPLOAD_LOC" != "none" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious where $ARTIFACT_UPLOAD_LOC is getting set? In the job definition?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it's defined by environment variable in the job.

@jouho jouho enabled auto-merge (squash) August 8, 2024 16:24
@jouho jouho merged commit b356b86 into main Aug 8, 2024
38 checks passed
@jouho jouho deleted the s3-upload-fix branch August 8, 2024 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants