Fail the process if more than one log entry was found. #782
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix defect where if the Achilles log file contains one or more run
ERROR: no runtime found in log fileis recorded to theachilles_resultstable. Fix is to halt the process if this condition occurs and warn the user to delete the log file first.Ideally we wouldn't be reading back from our own log files, but at least with this tweak the process won't fail silently anymore.
In the event that we spot more than one performance log entry, we will print this error and quit.
Previously, without this tweak we would get these results
I can supply a log file if needed to recreate this issue if needed.