fix(ci): install the Go the module asks for when building the site (#… #9872
mudlerimage.yml
on: push
changes
10s
Matrix: core-image-build
Matrix: gh-runner
Matrix: hipblas-jobs
core-image-merge
/
merge
36s
gpu-vulkan-image-merge
/
merge
36s
gpu-nvidia-cuda-12-image-merge
/
merge
26s
gpu-nvidia-cuda-13-image-merge
/
merge
21s
gpu-intel-image-merge
/
merge
21s
nvidia-l4t-arm64-image-merge
/
merge
21s
nvidia-l4t-arm64-cuda-13-image-merge
/
merge
25s
gpu-hipblas-image-merge
/
merge
32s
Annotations
20 errors
|
gh-runner (cublas, 12, 0, linux/arm64, auto, -nvidia-l4t-arm64, nvcr.io/nvidia/l4t-jetpack:r36.4.... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
gh-runner (cublas, 12, 0, linux/arm64, auto, -nvidia-l4t-arm64, nvcr.io/nvidia/l4t-jetpack:r36.4.... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (vulkan, linux/arm64, arm64, auto, -gpu-vulkan, ubuntu-24.04-arm, ubuntu:24.04, ... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (vulkan, linux/arm64, arm64, auto, -gpu-vulkan, ubuntu-24.04-arm, ubuntu:24.04, ... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (linux/arm64, arm64, auto, ubuntu:24.04, ubuntu-24.04-arm, --jobs=4 --output-syn... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (linux/arm64, arm64, auto, ubuntu:24.04, ubuntu-24.04-arm, --jobs=4 --output-syn... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
hipblas-jobs (hipblas, linux/amd64, auto, -gpu-hipblas, rocm/dev-ubuntu-24.04:7.2.1, ubuntu-lates... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
hipblas-jobs (hipblas, linux/amd64, auto, -gpu-hipblas, rocm/dev-ubuntu-24.04:7.2.1, ubuntu-lates... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
gh-runner (cublas, 13, 0, linux/arm64, auto, -nvidia-l4t-arm64-cuda-13, ubuntu:24.04, ubuntu-24.0... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
gh-runner (cublas, 13, 0, linux/arm64, auto, -nvidia-l4t-arm64-cuda-13, ubuntu:24.04, ubuntu-24.0... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (cublas, 12, 8, linux/amd64, auto, -gpu-nvidia-cuda-12, ubuntu-latest, ubuntu:24... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (cublas, 12, 8, linux/amd64, auto, -gpu-nvidia-cuda-12, ubuntu-latest, ubuntu:24... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (vulkan, linux/amd64, amd64, auto, -gpu-vulkan, ubuntu-latest, ubuntu:24.04, fal... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (vulkan, linux/amd64, amd64, auto, -gpu-vulkan, ubuntu-latest, ubuntu:24.04, fal... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (linux/amd64, amd64, auto, ubuntu:24.04, ubuntu-latest, --jobs=4 --output-sync=t... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (linux/amd64, amd64, auto, ubuntu:24.04, ubuntu-latest, --jobs=4 --output-sync=t... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (intel, linux/amd64, auto, intel/oneapi-basekit:2025.3.2-0-devel-ubuntu24.04, -g... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (intel, linux/amd64, auto, intel/oneapi-basekit:2025.3.2-0-devel-ubuntu24.04, -g... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (cublas, 13, 0, linux/amd64, auto, -gpu-nvidia-cuda-13, ubuntu-latest, ubuntu:24... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
|
core-image-build (cublas, 13, 0, linux/amd64, auto, -gpu-nvidia-cuda-13, ubuntu-latest, ubuntu:24... / reusable_image-build
Command failed: go env GOPATH\n\nThe workflow pinned setup-go to 1.22 while go.mod declares go 1.26.0, so\nthe `go run ./.github/ci/modelslist.go` step that generates the gallery\npage had to fetch the real toolchain from proxy.golang.org first. That\nfetch is not reliably reachable from the runner, which is why the deploy\nalternated between passing and failing rather than failing outright.\n\nTrack go.mod instead of a literal. The version the module needs is then\ninstalled directly and there is no toolchain download to fail.\n\nThis matters beyond CI noise: the docs and the site, including the\nrelease blog post, ship through this workflow.\n\nScoped deliberately to gh-pages, the workflow with the observed failure.\ntest-extra.yml pins 1.25.4 in a dozen places and is below go.mod for the\nsame reason, so those jobs also download a toolchain, but they are\ncurrently green and rewriting twelve pins on a hunch risks more than it\nfixes. Worth a follow-up.\n\n\nAssisted-by: Claude Code:claude-opus-5 [Read] [Edit] [Bash]\n\nSigned-off-by: Ettore Di Giacinto <mudler@localai.io>\nCo-authored-by: Ettore Di Giacinto <mudler@localai.io>",
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
digests-localai-core--amd64
Expired
|
244 Bytes |
sha256:07319e3fe184a2589774ce02f429668bf6c2e49cdc8ec1f09a0bf6a00c872b5e
|
|
|
digests-localai-core--arm64
Expired
|
244 Bytes |
sha256:09818a58efb77c311c4efb6c7a2106c074eeb46747e239dac8e44a0f7594d6a3
|
|
|
digests-localai-gpu-hipblas--single
Expired
|
244 Bytes |
sha256:7e16676d63705c9b5871df34cb37798fa378a45fba70cdd41a28e3c17988f047
|
|
|
digests-localai-gpu-intel--single
Expired
|
244 Bytes |
sha256:eea3ac7b324d5948ac7ef54bd754b3461e34d7551b9d9f12124c0f0cca8905d8
|
|
|
digests-localai-gpu-nvidia-cuda-12--single
Expired
|
244 Bytes |
sha256:83f042df4e9625c16a413db73da658e1653e80ff4a637b422eaf6b3cd7cca465
|
|
|
digests-localai-gpu-nvidia-cuda-13--single
Expired
|
244 Bytes |
sha256:0bb4b30036e99fc604ee827a9036cf60e4ce26a4f0bc994d9f577b4aca2f77f6
|
|
|
digests-localai-gpu-vulkan--amd64
Expired
|
244 Bytes |
sha256:a869fe72e36af4549de8a471af51f7f7ff984de8081b590e012e96ec513440e5
|
|
|
digests-localai-gpu-vulkan--arm64
Expired
|
244 Bytes |
sha256:c0af23d95ae37eb555b805239f1e873bf05532bc8d9e40bdb17670fdb062d0c3
|
|
|
digests-localai-nvidia-l4t-arm64--single
Expired
|
244 Bytes |
sha256:717185104a9606390135847b20bf8275095c32bb9fa12dbb59160bc91734fc1a
|
|
|
digests-localai-nvidia-l4t-arm64-cuda-13--single
Expired
|
244 Bytes |
sha256:1a66c4f809c4f45878120654f3496dd85b79b46f4cb73fcac76bc00ff931489b
|
|
|
mudler~LocalAI~79ZRB4.dockerbuild
|
127 KB |
sha256:e68250d03550e70dc0e380b0612b46633f1d7e795dc2a4f1049ea558a341a31a
|
|
|
mudler~LocalAI~E4EZEW.dockerbuild
|
142 KB |
sha256:8d8db76eaff48e606b3f7e089d63db60c8ed2dd588aa3963aabe23c66ececa27
|
|
|
mudler~LocalAI~IR6ZJM.dockerbuild
|
127 KB |
sha256:d6b4db2f84ad86314fffd535cf765c4c1fda69576a2ffac85cb240d52d4c6728
|
|
|
mudler~LocalAI~J4L7O4.dockerbuild
|
125 KB |
sha256:d440a64f9ca5c1308b2691139f1fd3b3504e7d54e11fd456df100b1086e005f0
|
|
|
mudler~LocalAI~M6VT8J.dockerbuild
|
125 KB |
sha256:6791d001d685d92cbef7813d75d2146c7938e2c710372b7a455f5c566c2992d9
|
|
|
mudler~LocalAI~NNX3CO.dockerbuild
|
181 KB |
sha256:0c9b5baf4bc775913642cd9ddd241cd670bbfeceed5602ef6e8e98fd1359f8d7
|
|
|
mudler~LocalAI~URNZKA.dockerbuild
|
129 KB |
sha256:8227be0b4bf48ab1fa23a83426a784b6f0f8d6583cbde3f4b6185e874b378b09
|
|
|
mudler~LocalAI~UYO6U6.dockerbuild
|
138 KB |
sha256:dd73c620f1ff1fb5d65a0c21b62d1ce8bee2ade474871e39f912dad08886937c
|
|
|
mudler~LocalAI~YN2SDX.dockerbuild
|
129 KB |
sha256:45bc51fb4de98178418ad352f405cb4253ae28d3b7529d2ec8da9774b3294ee2
|
|
|
mudler~LocalAI~Z86LEL.dockerbuild
|
126 KB |
sha256:7effea3e4994bdaf7f0bc7461683cc01a0c8f646a0014425ff52c9b17573d5e6
|
|