-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Perform structural fallbacks for reliable variance results less liberally #54754
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
base: main
Are you sure you want to change the base?
Perform structural fallbacks for reliable variance results less liberally #54754
Conversation
@typescript-bot test this |
Heya @weswigham, I've started to run the diff-based top-repos suite on this PR at 33729e6. You can monitor the build here. Update: The results are in! |
Heya @weswigham, I've started to run the parallelized Definitely Typed test suite on this PR at 33729e6. You can monitor the build here. Update: The results are in! |
Heya @weswigham, I've started to run the extended test suite on this PR at 33729e6. You can monitor the build here. |
Heya @weswigham, I've started to run the perf test suite on this PR at 33729e6. You can monitor the build here. Update: The results are in! |
@weswigham Here they are:
CompilerComparison Report - main..54754
System
Hosts
Scenarios
TSServerComparison Report - main..54754
System
Hosts
Scenarios
StartupComparison Report - main..54754
System
Hosts
Scenarios
Developer Information: |
@weswigham Here are the results of running the top-repos suite comparing Something interesting changed - please have a look. Details
|
Hey @weswigham, the results of running the DT tests are ready. Branch only errors:Package: backbone-relational
Package: wordpress__admin
Package: alloy
Package: backbone
Package: backbone.layoutmanager
Package: forms
Package: knockback
Package: backbone-associations
Package: backbone.localstorage
Package: backgrid
Package: backbone-fetch-cache
Package: backbone.marionette
Package: giraffe
Package: mongoose-promise
|
Only performing structural fallbacks of variance-based comparisons if the comparison that actually failed is the unreliable/unmeasurable one allows us to utilize variance results more often, which should be good for performance.
This does not, ultimately, fix #54542 in the case of lodash, unfortunately (I had to narrow the change a bit to fix an issue some tests caught, so I'm still back to looking at other ways to attack the underlying issue of "way too many instantiations required to check an insanely complicated type hierarchy"), but may fix (well, hide, really) other reports.