Warning: a recent release failed

[failure-checker]

The following release PRs may have failed:

• #21 - The release job was triggered, but has not reported back success.
• #18 - The release job was triggered, but has not reported back success.
• #13 - The release job was triggered, but has not reported back success.

[Tim Sweña (Swast)]

I'm on it.

0.3.0 release failed due to mismatch in Kokoro config and our mult_scm name. Addressed by

• #16 (update build trigger)
• #17 (update kokoro config)

0.3.1 release failed because our release.sh file wasn't marked as executable, but also I noticed a mismatch in the directory name and the scm name:

• #20

Note: using owlbot would have likely fixed several of these issues. Filed #22 to address that separately.

[Tim Sweña (Swast)]

Update: 0.3.2 failed as well. #21

================================================================
2023-09-06T15:06:53Z: Running the tests in a Docker container. 
================================================================
ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'github/bigframes/.kokoro/requirements.txt'

I think it is time for owlbot, as this is becoming too much to track down.