Skip to content

Increase valid starting times for github report#1849

Merged
AustinBenoit merged 2 commits intomainfrom
missingfix
Apr 28, 2026
Merged

Increase valid starting times for github report#1849
AustinBenoit merged 2 commits intomainfrom
missingfix

Conversation

@AustinBenoit
Copy link
Copy Markdown
Contributor

@AustinBenoit AustinBenoit commented Apr 28, 2026

Description

Provide details of the change, and generalize the change in the PR title above.

The github actions that run as a part of our nightly reports often start later than expected. We previously allowed for a 20 minute delay. Now we should just care about which hour in which the job was started. Recently we have had delays up to 45 minutes.


Testing

Describe how you've tested these changes. Link any manually triggered Integration tests or CPP binary SDK Packaging Github Action workflows, if applicable.

...


Type of Change

Place an x the applicable box:

  • Bug fix. Add the issue # below if applicable.
  • New feature. A non-breaking change which adds functionality.
  • Other, such as a build process or documentation change.

Notes

  • Bug fixes and feature changes require an update to the Release Notes section of release_build_files/readme.md.
  • Read the contribution guidelines CONTRIBUTING.md.
  • Changes to the public API require an internal API review. If you'd like to help us make Firebase APIs better, please propose your change in a feature request so that we can discuss it together.

The github actions that run as a part of our nightly
reports often start later than expected. We previously allowed
for a 20 minute delay but now we can allow for a 59 minute delay.
59 minutes is the longest possible delay that should still not cause
confusion when reporting the results.
@AustinBenoit AustinBenoit added the skip-release-notes Skip release notes check label Apr 28, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the test_time_minute_range from 20 to 59 in the build status reporting script. Feedback suggests that setting this value to 59 makes the subsequent minute check redundant and highlights a potential logic flaw where tests delayed past the hour boundary might be missed, recommending a more robust time-delta comparison.

Comment thread scripts/gha/report_build_status.py Outdated
@AustinBenoit AustinBenoit marked this pull request as ready for review April 28, 2026 16:18
@AustinBenoit AustinBenoit merged commit 3fe6b6e into main Apr 28, 2026
29 checks passed
@github-actions github-actions Bot added the tests: in-progress This PR's integration tests are in progress. label Apr 28, 2026
@github-actions
Copy link
Copy Markdown

⏳  Integration test in progress...

Requested by @AustinBenoit on commit 3fe6b6e
Last updated: Tue Apr 28 12:45 PDT 2026
View integration test log & download artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-release-notes Skip release notes check tests: in-progress This PR's integration tests are in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants