infra: update golang to latest minor version of 1.22

[catenacyber]

cc @guidovranken as I see cryptofuzz is using go1.22.7

Should fix ngolo-fuzzing build failure
https://issues.oss-fuzz.com/issues/379159151

go tool dist: go1.22.1 does not meet the minimum bootstrap requirement of go1.22.6 or later

[catenacyber]

@AdamKorcz would you know who can take this in ?

[catenacyber]

@DonggeLiu Can this PR get a review ?

[DonggeLiu]

Thanks @AdamKorcz

[DonggeLiu]

/gcbrun trial_build.py golang --fuzzing-engines libfuzzer --sanitizers coverage address

[catenacyber]

Trial build failure seems unrelated (centipede)

[DavidKorczynski]

The centipede build should be working

[DavidKorczynski]

/gcbrun trial_build.py golang --fuzzing-engines libfuzzer --sanitizers coverage address

[DavidKorczynski]

/gcbrun trial_build.py golang --fuzzing-engines libfuzzer --sanitizers coverage address

[catenacyber]

Why did the trial build fail ?

[DavidKorczynski]

I'm not sure why it failed, the log isn't showing any explicit issues as such. I see:

Step #1: Step #1: #11 sha256:55520b9d95ba838fedafe4514d6ec6e2c6ec484c7794d95d0ed2ddef3eaae1a5
Step #1: Step #1: #11 DONE 0.0s
Step #1: Step #1: 
Step #1: Step #1: #6 importing cache manifest from gcr.io/oss-fuzz-base/base-clang-testing-go-ngolo-1229
Step #1: Step #1: #6 sha256:2c343b2839d0c820056ee3d0b2dea4ed39b8d49984dd2fa10d40047212f05ce3
Step #1: Step #1: #6 ERROR: gcr.io/oss-fuzz-base/base-clang-testing-go-ngolo-1229:latest: not found
Step #1: Step #1: 
Step #1: Step #1: #4 importing cache manifest from gcr.io/oss-fuzz-base/base-clang

but I don't think is the issue -- later on it performs the same steps and it's okay.

[DavidKorczynski]

/gcbrun trial_build.py golang --fuzzing-engines libfuzzer --sanitizers coverage address

[catenacyber]

ERROR: (gcloud.builds.submit) INVALID_ARGUMENT: invalid build: invalid .steps field: build step #1 - "build-x86_64": the ID is not unique

gcbrun does not seem to work so well after a few tries...

What should we do ?

[DonggeLiu]

Strange that the errors are different, I don't think they are caused by this PR.
Rerunning the trial build just in case they are flaky.

[DonggeLiu]

/gcbrun trial_build.py golang --fuzzing-engines libfuzzer --sanitizers coverage address

[catenacyber]

@DonggeLiu the gcbrun seems to hit another unrelated error :
ERROR: (gcloud.builds.submit) INVALID_ARGUMENT: invalid build: invalid .steps field: build step #1 - "build-x86_64": the ID is not unique

What should we do to get this in and fix ngolo-fuzzing ?

[DavidKorczynski]

hmm, I think this may need rebasing

[DavidKorczynski]

/gcbrun trial_build.py golang --fuzzing-engines libfuzzer --sanitizers coverage address

[catenacyber]

Thanks for rebasing, what is the failure ? I do not have access to the logs on GC

[DavidKorczynski]

From the logs I can't see what the actual error is wrt. failed trial build. @oliverchang @DonggeLiu can you see anything that fails?

[DavidKorczynski]

So it looks like the problem is that no actual projects are tested:

Step #1: Failed builds: 0/0, {}

[DavidKorczynski]

perhaps because it's should be go rather than golang in the trial build

[DavidKorczynski]

/gcbrun trial_build.py go --fuzzing-engines libfuzzer --sanitizers coverage address

[DavidKorczynski]

perhaps because it's should be go rather than golang in the trial build

I think this is it.

[DavidKorczynski]

Yep, can confirm things are running now. Apologies for the delay @catenacyber -- this should be good to go once the trial build finishes

[catenacyber]

🤞

[catenacyber]

So is timed out good enough ?

[DavidKorczynski]

The only project failing is not due to this PR. This is good to go.

[catenacyber]

https://issues.oss-fuzz.com/issues/379159151 verified 🎉