GH-51285: [CI] Fix AMD64 Conda Integration Test failure

[hiroyuki-sato]

Rationale for this change

AMD64 Conda Integration Test failure

https://github.com/apache/arrow/actions/runs/34469696916/job/102846552090?pr=51284

  ++ uname
  + go_lib=arrow_go_integration.so
  + go build -buildvcs=false -tags cdata_integration,assert -buildmode=c-shared -o arrow_go_integration.so .
  package github.com/apache/arrow-go/v18/arrow/internal/cdata_integration: build constraints exclude all Go files in /arrow/go/arrow/internal/cdata_integration
  
  Error: `docker compose --file=/home/runner/work/arrow/arrow/compose.yaml run --rm -e ARCHERY_DEFAULT_BRANCH=main -e ARCHERY_INTEGRATION_WITH_DOTNET=1 -e ARCHERY_INTEGRATION_WITH_GO=1 -e ARCHERY_INTEGRATION_WITH_JAVA=1 -e ARCHERY_INTEGRATION_WITH_JS=1 -e ARCHERY_INTEGRATION_WITH_NANOARROW=1 -e ARCHERY_INTEGRATION_WITH_RUST=1 -e RUST_BACKTRACE=1 conda-integration` exited with a non-zero exit code 1, see the process log above.

The Conda integration test requires cgo, but mamba install go currently selects the nocgo variant by default.

What changes are included in this PR?

Selects the cgo-enabled Go package for the Conda integration test.

Before this change, mamba selected the nocgo variant:

go  1.27.1  nocgo_h8a70693_5  conda-forge
go version go1.27.1 linux/amd64
CGO_ENABLED=0
CC=/dev/null

After this change, mamba installs the Go package with cgo support:

go  1.27.1  cgo_haf5475a_5  conda-forge
go version go1.27.1 linux/amd64
CGO_ENABLED=1
CC=x86_64-conda-linux-gnu-cc

Are these changes tested?

Yes.

Are there any user-facing changes?

No.

• GitHub Issue: [CI] AMD64 Conda Integration Test failure #51285

[github-actions]

⚠️ GitHub issue #51285 has been automatically assigned in GitHub to PR creator.

[github-actions]

⚠️ GitHub issue #51285 has no components, please add labels for components.

[pitrou]

@zeroshade Could you or one of your fellow Go maintainers help on this? (if only by reviewing)

[hiroyuki-sato]

It looks like mamba install go is now installing the nocgo variant of Go, so we may need to explicitly install the cgo-enabled variant. I’ll try that later.

go  1.27.1  nocgo_h8a70693_5  conda-forge
go version go1.27.1 linux/amd64
CGO_ENABLED=0
CC=/dev/null

[hiroyuki-sato]

Starting with build 5, the cgo and nocgo variants are explicitly
identified in the build string.

Currently, mamba install go selects the nocgo variant:

Go version	Build	Build number	Notes
1.27.1	nocgo_h8a70693_5	5	Current nocgo variant
1.27.1	cgo_haf5475a_5	5	Current cgo variant
1.27.1	haac8767_4	4	Previous build
1.27.1	h0bf09dd_4	4	Previous build
1.27.1	h0bf09dd_3	3	Previous build
1.27.1	haac8767_3	3	Previous build
1.27.1	h0bf09dd_2	2	Previous build
1.27.1	haac8767_2	2	Previous build
1.27.1	he1b14cc_1	1	Previous build
1.27.1	h1a1113d_1	1	Previous build
1.27.1	h1a1113d_0	0	Initial build
1.27.1	he1b14cc_0	0	Initial build

podman run -it --rm condaforge/miniforge3:latest mamba repoquery search 'go=1.27.1' --json |   jq -r '.result.pkgs[] | "\(.name) \(.version) \(.build) \(.subdir)"' | perl -pe 's/^\s+//'
go 1.27.1 nocgo_h8a70693_5 linux-64
go 1.27.1 cgo_haf5475a_5 linux-64
go 1.27.1 haac8767_4 linux-64
go 1.27.1 h0bf09dd_4 linux-64
go 1.27.1 h0bf09dd_3 linux-64
go 1.27.1 haac8767_3 linux-64
go 1.27.1 h0bf09dd_2 linux-64
go 1.27.1 haac8767_2 linux-64
go 1.27.1 he1b14cc_1 linux-64
go 1.27.1 h1a1113d_1 linux-64
go 1.27.1 h1a1113d_0 linux-64
go 1.27.1 he1b14cc_0 linux-64

[github-actions]

⚠️ GitHub issue #51285 has no components, please add labels for components.

[lidavidm]

It's not clear to me but maybe go-cgo is the preferred way to get this? https://anaconda.org/channels/conda-forge/packages/go-cgo/overview (although this talks about recipes)

[hiroyuki-sato]

@lidavidm Thanks for the review. I'll try go-cgo as well, just in case.

[lidavidm]

It appears integration passes!

[hiroyuki-sato]

@lidavidm Thanks. AMD64 Conda Integration Test has passed with mamba install go-cgo.

[kou]

+1