generate-prod: docfx-go-cloud.google.com failed

[flaky-bot]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.

---

commit: 1404e09
buildURL: Build Status, Sponge
status: failed

[tbpg]

This seems like a real issue with the YAML generated for this package.

Error:

[24-03-14 10:23:16.724]Error:[BuildCore.Build Document.Load.UniversalReferenceDocumentProcessor](obj/api/apiv1beta1/automlpb.yml)Unable to load file 'obj/api/apiv1beta1/automlpb.yml' via processor 'UniversalReferenceDocumentProcessor': (Line: 13923, Col: 9, Idx: 843787) - (Line: 13923, Col: 10, Idx: 843788): While scanning for the next token, find character that cannot start any token.

Here is the failing part:

13921         [gcs_destination][google.cloud.automl.v1beta1.OutputConfig.gcs_destination]
13922 
13923         !·······  must be set. Exported are CSV file(s) `tables_1.csv`,

(With !······· being a tab.)

I tried parsing it with yaml.safe_load in Python and got a more helpful error:

yaml.scanner.ScannerError: while scanning for the next token
found character '\t' that cannot start any token
  in "apiv1beta1/automlpb.yml", line 13923, column 9

If I add two spaces before the lines I quoted above (and the ones below it) so that they line up with the - For Translation: line above, it parses successfully.

[tbpg]

I deleted the blob for now.

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

[dandhlee]

Downgrading to P2.