Inconsistent build failures due to go versions

What feels like at random times, my build will fail due to a go packaging issue. Here’s a section of deploy details that happen between two successful build and deploys:

10:06:15 AM: build-image version: 1ca34a93198b041e44214013884c57d146a23fed (focal)
10:06:15 AM: build-image tag: v4.16.4
10:06:15 AM: buildbot version: 2577a19e1559072eeb7a6727cec389b63b90401c
10:06:16 AM: Fetching cached dependencies
10:06:16 AM: Starting to download cache of 854.2MB
10:06:23 AM: Finished downloading cache in 6.978s
10:06:23 AM: Starting to extract cache
10:06:27 AM: Finished extracting cache in 4.163s
10:06:27 AM: Finished fetching cache in 11.229s
10:06:27 AM: Starting to prepare the repo for build
10:06:27 AM: Preparing Git Reference refs/heads/main
10:06:28 AM: Parsing package.json dependencies
10:06:29 AM: Different functions path detected, going to use the one specified in the Netlify configuration file: 'functions' versus '' in the Netlify UI
10:06:29 AM: Starting build script
10:06:29 AM: Installing dependencies
10:06:29 AM: Python version set to 2.7
10:06:29 AM: Started restoring cached Node.js version
10:06:30 AM: Finished restoring cached Node.js version
10:06:30 AM: v16.19.0 is already installed.
10:06:30 AM: Now using node v16.19.0 (npm v8.19.3)
10:06:30 AM: Enabling Node.js Corepack
10:06:30 AM: Started restoring cached build plugins
10:06:30 AM: Finished restoring cached build plugins
10:06:31 AM: Attempting Ruby version 2.7.2, read from environment
10:06:31 AM: Using Ruby version 2.7.2
10:06:31 AM: Using PHP version 8.0
10:06:31 AM: Started restoring cached corepack dependencies
10:06:31 AM: mv: cannot move '/opt/build/cache/.node/corepack' to '/opt/buildhome/.node/corepack': No such file or directory
10:06:31 AM: Finished restoring cached corepack dependencies
10:06:31 AM: Started restoring cached yarn cache
10:06:35 AM: Finished restoring cached yarn cache
10:06:35 AM: Installing Yarn version 1.22.10
10:06:35 AM: Preparing yarn@1.22.10 for immediate activation...
10:06:35 AM: No yarn workspaces detected
10:06:35 AM: Started restoring cached node modules
10:06:35 AM: Finished restoring cached node modules
10:06:36 AM: Installing npm packages using Yarn version 1.22.10
10:06:36 AM: yarn install v1.22.10
10:06:36 AM: [1/4] Resolving packages...
10:06:36 AM: success Already up-to-date.
10:06:36 AM: Done in 0.23s.
10:06:36 AM: npm packages installed using Yarn
10:06:36 AM: Started restoring cached go cache
10:06:36 AM: Finished restoring cached go cache
10:06:36 AM: Installing Go version 1.16.5 (requested 1.16.5)
10:06:40 AM: I don't have any idea what to do with '1.16.5'.
  (using download type 'binary')
10:06:40 AM: Failed to install Go version '1.16.5'
10:06:40 AM: Build was terminated: Build script returned non-zero exit code: 1
10:06:40 AM: Failing build: Failed to build site
10:06:40 AM: Failed during stage 'building site': Build script returned non-zero exit code: 1 (https://ntl.fyi/exit-code-1)
10:06:40 AM: Finished processing build request in 24.59s

My project doesn’t use go, I’m not trying to install any special versions of go.

Netlify site name: musical-llama-e41a2e

Build settings screenshot:
Screen Shot 2023-01-25 at 10.26.58 AM

Hi @zackseuberling,

This has been escalated to the devs and is being looked at.

1 Like

Hi @zackseuberling.

Sorry for the silence here, but this should be resolved. Looking at the deploy status, I don’t see any more of such failures, but please let us know if this is still an issue.