Skip to content

chore: fix multiple failing tests on main#920

Merged
sofisl merged 64 commits intomainfrom
updateGo
Mar 12, 2026
Merged

chore: fix multiple failing tests on main#920
sofisl merged 64 commits intomainfrom
updateGo

Conversation

@sofisl
Copy link
Contributor

@sofisl sofisl commented Mar 5, 2026

  • latest version of nock was breaking gaxios, so had to pin it
  • had to update version of go for showcase tests
  • syncpack tests are failing; will address in another PR (fix: use compatible syncpack configuration #926)
  • had to change how we upload our gcp-metadata function since gcx was not passing a parameter to pass org constraints correctly
  • had to correctly install gcloud in our test runner to accommodate the new version of gcp-metadata test (instead of using gcx). installing gcloud stalled out our tests, so i removed kaniko to actually finish the installation and have it accessible for our tests
  • in all of this investigation of the failing tests, I found a bug that our cloudbuild triggers don't actually correspond to the right .yaml file. fixed it in here as well

@sofisl sofisl requested a review from a team as a code owner March 5, 2026 21:53
@sofisl sofisl changed the title chore: update go to 1.25 chore: multiple failing tests on main Mar 6, 2026
@sofisl sofisl changed the title chore: multiple failing tests on main chore: fix multiple failing tests on main Mar 6, 2026
@sofisl
Copy link
Contributor Author

sofisl commented Mar 6, 2026

#923

@quirogas quirogas requested review from quirogas and removed request for quirogas March 10, 2026 18:26
@quirogas quirogas assigned quirogas and sofisl and unassigned quirogas Mar 12, 2026
@quirogas quirogas self-requested a review March 12, 2026 18:31
} catch (e) {
console.error(`GCF_METADATA_CHECK: error=${e.message}`);
}
})();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(optional) Do we want to await this? Will the following code fail if the metadata isn't available? At the very least, it may guarantee the log message appears in a consistent place during execution.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

opts: {strip?: number; filter?: (file: any) => boolean},
callback: (err?: Error | null) => void,
) => {
const output = Math.floor(Math.random() * 1000000) + '.zip';

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(optional) Any reason not to use randomUUID for stuff like this?

console.log(`Downloading ${input} to ${output}...`);

const writeStream = fs.createWriteStream(output);
const stream = (got as unknown as got.Got).stream(input);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(optional) Does got not have types? Could we just install @types/got for added safety?

@sofisl sofisl merged commit 894c151 into main Mar 12, 2026
12 of 13 checks passed
@sofisl sofisl deleted the updateGo branch March 12, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants