-
Notifications
You must be signed in to change notification settings - Fork 934
Ensure e2e tests fail on TS errors #7184
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
Conversation
|
Size Report 1Affected ProductsNo changes between base commit (965396d) and merge commit (077e73c).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (965396d) and merge commit (077e73c).Test Logs |
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.
LGTM
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.
LGTM
Use
noEmitOnError
TS config flag to ensure karma E2E tests fail if TS has a compile error.Also getting a warning about actions/setup-node@v2 being deprecated - we should update this in all workflows.
Otherwise TS failures like the one in this E2E job are non-blocking and the workflow is considered passing https://github.com/firebase/firebase-js-sdk/actions/runs/4550223341