Skip to content

Conversation

@jakebailey
Copy link
Member

RWC tests currently fail because one of the tests includes tsconfig in the input file set, so the harness double-reports errors. This is brand new after our new deprecations, but we didn't seem to notice as the RWC tests were still reporting baseline differences.

This sort of thing appears to already be worked around for lib.d.ts files, so, do something similar to tsconfig to get RWC passing again.

@typescript-bot typescript-bot added Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug labels Feb 17, 2023
@jakebailey
Copy link
Member Author

@typescript-bot test this

@typescript-bot
Copy link
Collaborator

typescript-bot commented Feb 17, 2023

Heya @jakebailey, I've started to run the extended test suite on this PR at e7b72db. You can monitor the build here.

@jakebailey
Copy link
Member Author

jakebailey commented Feb 17, 2023

The above passes, but now exposes the fact that RWC (unlike our other tests) doesn't reply with "everything looks good" or something. The only reason it's been replying with "here's a diff" is because it fails due to this assert and then sends an empty baseline change as a PR.

@jakebailey jakebailey merged commit 4587871 into microsoft:main Feb 21, 2023
@jakebailey jakebailey deleted the fix-rwc branch February 21, 2023 19:09
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants