Skip to content

[CI] 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

Merged
merged 3 commits into from
Jul 3, 2025

Conversation

rlazo
Copy link
Collaborator

@rlazo rlazo commented Jun 27, 2025

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.

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.
@rlazo rlazo requested review from VinayGuthal and davidmotson June 27, 2025 07:13
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

Copy link
Contributor

Firebase AI Mock Responses Check ⚠️

A newer major version of the mock responses for Firebase AI unit tests is available. update_responses.sh should be updated to clone the latest version of the responses: v14.1

Copy link
Contributor

github-actions bot commented Jun 27, 2025

Test Results

 1 096 files  + 38   1 096 suites  +38   36m 47s ⏱️ +41s
 5 986 tests ±  0   5 963 ✅ ±  0  22 💤 ±0  1 ❌ ±0 
12 685 runs  +650  12 640 ✅ +650  44 💤 ±0  1 ❌ ±0 

For more details on these failures, see this check.

Results for commit b7f6bd7. ± Comparison against base commit 4744473.

♻️ This comment has been updated with latest results.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 27, 2025

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 27, 2025

Coverage Report 1

Affected Products

  • firebase-database

    Overall coverage changed from 50.16% (4744473) to 50.21% (8639c20) by +0.04%.

    FilenameBase (4744473)Merge (8639c20)Diff
    ChildChangeAccumulator.java83.33%96.67%+13.33%
  • firebase-messaging

    Overall coverage changed from 84.10% (4744473) to 84.21% (8639c20) by +0.11%.

    FilenameBase (4744473)Merge (8639c20)Diff
    FirebaseMessaging.java75.60%76.80%+1.20%
  • firebase-sessions

    Overall coverage changed from 66.56% (4744473) to 66.67% (8639c20) by +0.11%.

    FilenameBase (4744473)Merge (8639c20)Diff
    RemoteSettings.kt87.32%88.73%+1.41%
  • firebase-storage

    Overall coverage changed from 83.96% (4744473) to 84.37% (8639c20) by +0.42%.

    FilenameBase (4744473)Merge (8639c20)Diff
    StorageException.java65.45%69.09%+3.64%
    StorageTask.java83.38%83.99%+0.60%
    UploadTask.java81.52%83.50%+1.98%

Test Logs

  1. https://storage.googleapis.com/firebase-sdk-metric-reports/87NOm9046V.html

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 27, 2025

Startup Time Report 1

The report is too large (122,579 chars) to be displayed on GitHub. Please check this report on GCS.

  1. https://storage.googleapis.com/firebase-sdk-metric-reports/hsSLVidc6A/index.html

@rlazo
Copy link
Collaborator Author

rlazo commented Jun 30, 2025

Friendly ping

@rlazo rlazo changed the title Make publish-unit-test-result-action always run [CI] Make publish-unit-test-result-action always run Jun 30, 2025
@rlazo rlazo merged commit 689cf5a into main Jul 3, 2025
429 of 433 checks passed
@rlazo rlazo deleted the always-publish-test-results branch July 3, 2025 15:08
@firebase firebase locked and limited conversation to collaborators Aug 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants