/FrameworkBenchmarks

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

Simplify post-run steps for continuous benchmarking #2583

Merged
merged 1 commit into from Mar 7, 2017

Conversation

Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@michaelhixson @nbrady-techempower
@michaelhixson
Member

michaelhixson commented Mar 6, 2017

Create a zip of the results directory, and that's it, basically.

The previous behavior broke when we stopped using a "latest" results directory. This repairs and simplifies that behavior.
@michaelhixson
Simplify post-run steps for continuous benchmarking 
Put the entire results directory into a zip archive on the local disk.
Preserve the directory structure in the archive (previously the archive
was flat) and actually compress the contents (previous they were not
compressed).  Do not attempt to send an email.
fc7cd87

@nbrady-techempower nbrady-techempower merged commit f5a568a into TechEmpower:master Mar 7, 2017
1 check passed

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

zloster added a commit to zloster/FrameworkBenchmarks that referenced this pull request Mar 21, 2017

@michaelhixson @zloster
Simplify post-run steps for continuous benchmarking (#2583) 
Put the entire results directory into a zip archive on the local disk.
Preserve the directory structure in the archive (previously the archive
was flat) and actually compress the contents (previous they were not
compressed).  Do not attempt to send an email.
9e9026c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment