Skip to content

Performance testing script: cleanup, bugfixes, new features #3517

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

Merged
merged 8 commits into from
Dec 18, 2018

Conversation

tautschnig
Copy link
Collaborator

In preparation of SV-COMP'19 several improvements to the script were due, overall also improving the maintainability of the code.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

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

✔️
Passed Diffblue compatibility checks (cbmc commit: 1fbd642).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/93295865

@tautschnig
Copy link
Collaborator Author

Marking "do not merge" - the "compare-to" code does not seem to be working as it should.

@tautschnig
Copy link
Collaborator Author

The comparison feature is now working as well, benchexec nicely produces tables to compare multiple runs.

Copy link
Contributor

@thk123 thk123 left a comment

Choose a reason for hiding this comment

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

Nothing objectionable in here, but I don't feel qualified to really give it a proper review

@@ -0,0 +1,35 @@
#!/bin/bash
Copy link
Contributor

Choose a reason for hiding this comment

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

⛏️ Add docs at the top for how to run this (e.g. it looks like it should be called ec2-terminate.sh start|status)

@@ -0,0 +1,35 @@
#!/bin/bash
### BEGIN INIT INFO
Copy link
Contributor

Choose a reason for hiding this comment

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

❓ I don't know what the next 8 lines of code do...? That aren't informative to me?

esac

# send instance-terminated message
# http://rogueleaderr.com/post/48795010760/how-to-notifyemail-yourself-when-an-ec2-instance/amp
Copy link
Contributor

Choose a reason for hiding this comment

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

❓ Is this the source of this code? Probably want to make it more obvious that's what this link is for, e.g.

# Code take from

@@ -0,0 +1,256 @@
#!/bin/bash
Copy link
Contributor

Choose a reason for hiding this comment

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

⛏️ This is a long bash file that looks to be mostly moved:

  • move in one commit, bug fixes and other changes in a separate one if possible
  • is bash the right language for something this long?

We need to manually upload to S3 rather than using CodeBuild's cache
configuration as each perf-test run creates new CodeBuild configurations and
thus also new keys to store the cache at.
This reduces overhead during package install.
This simplifies editing. Just upload them to S3 when setting up benchmarking and
download them from S3 onto the instance. Also fixed several bugs in the script.
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

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

✔️
Passed Diffblue compatibility checks (cbmc commit: 1614a5f).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/95125956

@tautschnig tautschnig merged commit a745405 into diffblue:develop Dec 18, 2018
@tautschnig tautschnig deleted the perf-test-cleanup branch December 18, 2018 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants