Do not resolve apparent type of mapped types with a tuple constraint#52651
Conversation
|
@typescript-bot test this |
|
Heya @jakebailey, I've started to run the diff-based top-repos suite (tsserver) on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the diff-based top-repos suite on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the parallelized Definitely Typed test suite on this PR at be33c06. You can monitor the build here. |
|
Heya @jakebailey, I've started to run the perf test suite on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the diff-based user code test suite (tsserver) on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the diff-based user code test suite on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the extended test suite on this PR at be33c06. You can monitor the build here. |
|
@jakebailey Here are the results of running the user test suite comparing Everything looks good! |
1 similar comment
|
@jakebailey Here are the results of running the user test suite comparing Everything looks good! |
|
Heya @jakebailey, I've run the RWC suite on this PR - assuming you're on the TS core team, you can view the resulting diff here. |
|
@jakebailey Here they are:
CompilerComparison Report - main..52651
System
Hosts
Scenarios
TSServerComparison Report - main..52651
System
Hosts
Scenarios
StartupComparison Report - main..52651
System
Hosts
Scenarios
Developer Information: |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@jakebailey Here are the results of running the top-repos suite comparing Something interesting changed - please have a look. Detailsbackstage/backstageThat is a filtered view of the text. To see the raw error text, go to RepoResults4/backstage.backstage.rawError.txt in the artifact folder
|
|
@jakebailey Here are the results of running the top-repos suite comparing Everything looks good! |
|
@typescript-bot run dt but new and improved with more response post-backs |
|
Heya @weswigham, I've started to run the parallelized Definitely Typed test suite on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Hey @weswigham, it looks like the DT test run failed. Please check the log for more details. |
|
How can I see those failures? |
|
It's nothing you did; just a timeout. @typescript-bot run dt |
|
Heya @jakebailey, I've started to run the parallelized Definitely Typed test suite on this PR at be33c06. You can monitor the build here. Update: The results are in! |
|
Hey @jakebailey, the results of running the DT tests are ready. |
fixes #52650