-
Notifications
You must be signed in to change notification settings - Fork 625
Make publish-unit-test-result-action always run #7090
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?
Conversation
This change ensures that the step that publishes unit test results always runs, even if previous steps in the job have failed. This is useful for ensuring that test results are always available for inspection, regardless of the outcome of the tests themselves.
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Firebase AI Mock Responses Check
|
Test Results 1 058 files + 1 016 1 058 suites +1 016 36m 13s ⏱️ + 34m 51s Results for commit b7ead57. ± Comparison against base commit 2886218. ♻️ This comment has been updated with latest results. |
Size Report 1Affected ProductsNo changes between base commit (2886218) and merge commit (28f413a).Test Logs |
Coverage Report 1Affected Products
Test Logs |
This change ensures that the step that publishes unit test results always runs, even if previous steps in the job have failed. This is useful for ensuring that test results are always available for inspection, regardless of the outcome of the tests themselves.