storage uniform bucket-level access preserves bucket/file ACL over uniform bucket-level access on/off: should preserve file ACL failed

[flaky-bot]

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

---

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

Test output

Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
Error: Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
    at new ApiError (build/src/nodejs-common/util.js:76:15)
        -> /workspace/src/nodejs-common/util.ts:262:11
    at Util.parseHttpRespBody (build/src/nodejs-common/util.js:211:38)
        -> /workspace/src/nodejs-common/util.ts:463:32
    at Util.handleResp (build/src/nodejs-common/util.js:152:117)
        -> /workspace/src/nodejs-common/util.ts:396:20
    at /workspace/build/src/nodejs-common/util.js:496:22
        -> /workspace/src/nodejs-common/util.ts:826:16
    at onResponse (node_modules/retry-request/index.js:228:7)
    at /workspace/node_modules/teeny-request/build/src/index.js:226:13
        -> /workspace/node_modules/teeny-request/src/index.ts:333:11
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

[JesseLovelace]

in #1844, @ddelgrosso1 mentioned adding a follow up if this resurfaces, assigning to him

[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 (aab390c), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).