(PE-36194) benchmark: when submitting multiple messages backdate timestamps #3818
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
austb
force-pushed
the
pe-36194/main/backdate-benchmark-commands
branch
from
f1f2ea7
to
4a059c5
Compare
jpartlow
reviewed
Jun 27, 2023
austb
force-pushed
the
pe-36194/main/backdate-benchmark-commands
branch
from
4a059c5
to
2111fa5
Compare
Previously these flags determined the "mode" that benchmark ran in. Now that will be decided exclusively by the presence or absence of the nummsgs option. We need both options because the amount of back-dating needed when submitting the first reports is effectively (now - (nummsgs * runinterval)).
…ng with nummsgs > 1
austb
force-pushed
the
pe-36194/main/backdate-benchmark-commands
branch
from
2111fa5
to
a2fa354
Compare
|
Tests Failed \o/ |
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.
No description provided.