Nightly Testing Report

[github-actions]

Nightly Testing Report

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

Workflow	03/28
crashlytics	failure
instanceid	failure
prerelease	failure

[paulb777]

All three of these passed yesterday and there were no repo changes. Considering them transitory flakes unless they repeat tomorrow.

[github-actions]

Nightly Testing Report

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

Workflow	03/29
zip	failure
release	failure
segmentation	failure
cocoapods-integration	failure

[paulb777]

All of last night's failures are a result of yesterday's nanopb/GDT changes and I believe all infrastructure issues. I'll follow up with the resolution.

[paulb777]

Fixes for the nightly test failures in #7806, #7807, and #7808.

The release test is expected to fail because we don't want to use SpecsDev in release testing and master currently depends on it in advance of M93. We may want to rethink this ...

[github-actions]

Nightly Testing Report

This issue(log) is generated at 03/31/2021 06:08 AM, fetching workflow runs triggered in the last 24 hrs.

Workflow	03/30
storage	failure
zip	failure
database	failure
abtesting	cancelled

[paulb777]

I restarted storage, database, and abtesting.

It looks like #7807 is the wrong way to and SpecsDev as a repo to the zip test. @granluo, would you take a look?

[!] Unable to add a source with url `https://github.com/firebase/SpecsDev.git,https://github.com/firebase/SpecsStaging.git` named `firebase/specsdev.git,https://github.com/firebase`.
You can try adding it manually in `/Users/runner/.cocoapods/repos` or via `pod repo add`.
: file ZipBuilder/CocoaPodUtils.swift, line 217
scripts/build_zip.sh: line 35:  5376 Illegal instruction: 4  swift run zip-builder --keep-build-artifacts --update-pod-repo --local-podspec-path "${REPO}" --enable-carthage-build --output-dir "${OUTPUT_DIR}" --custom-spec-repos "${CUSTOM_SPEC_REPOS}"
Error: Process completed with exit code 132.