run.filesystem.e2e_test: test_end_to_end failed

[flaky-bot]

Note: #7776 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

---

commit: 4762700
buildURL: Build Status, Sponge
status: failed

Test output

Traceback (most recent call last):
  File "/workspace/run/filesystem/e2e_test.py", line 39, in deployed_service
    subprocess.check_call(
  File "/usr/local/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['gcloud', 'builds', 'submit', '--config', 'cloudbuild.yaml', '--project', 'python-docs-samples-tests', '--substitutions=_SERVICE_NAME=filesystem-9e4789fc13b14f6da8ecc2b898721ee0,_FILESTORE_IP_ADDRESS=10.72.188.10,_CONNECTOR=run-connector']' returned non-zero exit status 1.

[flaky-bot]

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (4762700), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[rogerthatdev]

I will attempt to resolve this flakiness by adding retries to run/filesystem/e2e_test.py similar to #8286

[rogerthatdev]

After taking a closer look, this test failed because the build (31bc50ad) timed out waiting for a subsequent build (3b460d8d) that it triggered via gcloud run deploy command in its cloudbuild.yaml

That second build did complete but this was not captured by the original build. As a remedy, instead of adding retries, will try to consolidate build jobs into one job instead of splitting the test into 2.