-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 #17504 from JuliaLang/yyc/codegen/plt
Use `musttail` only as an optimization in the PLT.
- Loading branch information
Showing
1 changed file
with
10 additions
and
8 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
ee5e231
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.
Executing the daily benchmark build, I will reply here when finished:
@nanosoldier
runbenchmarks(ALL, isdaily = true)
ee5e231
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.
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels
ee5e231
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.
To any onlookers curious about these extreme changes: the comparison here is not actually against the previous day's build. Yesterday, an extra daily build was accidentally triggered from a PR (the comment which triggered it has since been deleted, it seems), overwriting the actual daily build. We should add a check in Nanosoldier.jl that disallows daily build submissions from PRs in the future (maybe even disallow daily build submissions from anybody besides @nanosoldier).
The right thing to do now is probably just to revert the commit which added the erroneous daily build in the report repository, restoring the correct daily build results. Then, we could just regenerate today's report (note that today's data is correct, and doesn't need to be regathered; only the report needs to be regenerated). I might not have time to take care of this today, but I'll put it on my to-do list.