-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1230 from veg/develop
2.5.19
- Loading branch information
Showing
54 changed files
with
8,519 additions
and
2,351 deletions.
There are no files selected for viewing
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
Oops, something went wrong.
7310a28
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible performance regression was detected for benchmark 'Benchmark.js Benchmark'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
2
.IntermediateProtein.bf
5.986375010476157
secs/op (±1.760118%
)null
secs/op (±0.000000%
)Infinity
This comment was automatically generated by workflow using github-action-benchmark.
CC: @klevitz
7310a28
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible performance regression was detected for benchmark 'Benchmark.js Benchmark'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
2
.IntermediateProtein.bf
7.5451767457652705
secs/op (±0.976922%
)null
secs/op (±0.000000%
)Infinity
This comment was automatically generated by workflow using github-action-benchmark.
CC: @klevitz
7310a28
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Performance Alert is a false positive:
-The previous test of null secs/op is because the .bf file was edited at some point and failing to properly pass its own tests. This resulted in the benchmark recording a shorter/null time due to the .bf file erroring/failing to complete.
-With the latest test the .bf ran successfully which resulted in a non-zero time. This caused the comparison to compare 7.5 secs/op to 0 secs/op.
To address this I would recommend not editing the active production .wbf/.bf files that the benchmark references until they are known to pass.
If this issue presents in the future another fix is to remove 0 second job entries within the below table:
https://github.com/veg/hyphy/blob/gh-pages/dev/bench/data.js
Though, ideally, the test cases will be checked before running via the benchmark to avoid this problem in the future.