Nightly Testing Report

[github-actions]

Nightly Testing Report

This issue(log) is generated at 09/28/2024 05:03 AM, fetching workflow runs triggered in the last 24 hrs.

Workflow	09/27
storage	failure
crashlytics	failure
sessions	failure

[github-actions]

Nightly Testing Report

This issue(log) is generated at 09/29/2024 05:03 AM, fetching workflow runs triggered in the last 24 hrs.

Workflow	09/28
storage	failure
crashlytics	failure
database	failure
installations	failure

[github-actions]

Nightly Testing Report

This issue(log) is generated at 09/30/2024 05:03 AM, fetching workflow runs triggered in the last 24 hrs.

Workflow	09/29
crashlytics	failure

[ncooke3]

I'll run the crashlytics tests locally on Xcode 16. They failed the last few days.

[github-actions]

Nightly Testing Report

This issue(log) is generated at 10/01/2024 05:03 AM, fetching workflow runs triggered in the last 24 hrs.

Workflow	09/30
storage	failure
zip	failure
messaging	failure
crashlytics	failure
functions	failure
spm	failure
release	failure

[paulb777]

Restarted - except the zip job which is failing similar to #13745 and needs the auth test updated in zip.yml
and release job which is failing because of testing 11.3 instead of 11.4 for VertexAI https://github.com/firebase/firebase-ios-sdk/actions/runs/11118940608/job/30893758883#step:5:1069

[github-actions]

Nightly Testing Report

This issue(log) is generated at 10/02/2024 05:03 AM, fetching workflow runs triggered in the last 24 hrs.

Workflow	10/01
storage	failure
remoteconfig	failure
installations	failure
release	failure

[paulb777]

Looking more closely at the release workflow, it's testing the previous release instead of the current release - https://github.com/firebase/firebase-ios-sdk/actions/runs/11138103991/job/30952916546#step:5:76

[paulb777]

Maybe related to nightly tag not being updated?

[ncooke3]

relevant line in determining the tag: https://github.com/firebase/firebase-ios-sdk/actions/runs/11138103991/job/30952584486#step:4:16

[ncooke3]

Ah, it's because of the --merged main bit. The 11.4 tag is not on main

[paulb777]

Good find. I missed that step. Thanks!

[ncooke3]

I think we should remove the --merged main line but leave it in a comment to let future us know that it can be used to prevent long running prerelease branches (e.g. ahead of major version release) from affecting the testing of the next release. WDYT?

[paulb777]

Agreed. The bug is me forgetting to update-tags after merging the version 11.4.0 PR. Doing the update-tags now