Fix the build report status script

[a-maurice]

Description

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

The log files name changed several months, so update the script to handle it.

---

Testing

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

https://github.com/firebase/firebase-cpp-sdk/actions/runs/16457849624

---

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.

[gemini-code-assist]

Summary of Changes

Hello @a-maurice, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a bug in the GitHub Actions build status reporting script. It updates the regular expressions used to parse log files, ensuring the script can correctly identify and extract crucial information, such as packaging run IDs and integration test results, following recent changes to the log file naming conventions.

Highlights

• Bug Fix: I've updated the regular expressions within the report_build_status.py script to correctly parse GitHub Actions log file names. This addresses a bug where the script failed to extract necessary information due to recent changes in how log files are named.
• Script Maintenance: The changes ensure the build status reporting script can accurately identify and extract critical data, such as packaging run IDs and integration test results, from the updated log file formats, maintaining the script's functionality.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request updates the script to handle the changed log file names by modifying the regex used to find the relevant log files. The regex expressions could be made more robust to handle slight variations in the file names.

[github-actions]

Integration test with FLAKINESS (succeeded after retry)

Requested by @a-maurice on commit 4086d40
Last updated: Wed Jul 23 15:46 PDT 2025
View integration test log & download artifacts

Failures	Configs
app_check	[TEST] [FLAKINESS] [iOS] [macos] [1/2 ios_device: ios_target] (2 failed tests)   FirebaseAppCheckTest.TestDatabaseSetAndGet   FirebaseAppCheckTest.TestDatabaseUpdateToken

Add flaky tests to go/fpl-cpp-flake-tracker