Skip to content
Go

Fix broken AnswerQueue behavior with chained pipeline calls #1064

Sign in to view logs

Fix broken AnswerQueue behavior with chained pipeline calls

Fix broken AnswerQueue behavior with chained pipeline calls #1064

Re-run triggered February 19, 2025 00:32
@lthibaultlthibault
#605
ObsidianMinor:fix/answerqueue
Status Success
Total duration 4m 46s
Artifacts –

go.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Go 1.22 GOARCH=386
Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.22.12-33207288eef7cc66dacd9d5d991f7c7d3dcf123799ee1171df9a07126e27ba38
Go 1.23 GOARCH=386
Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.23.6-33207288eef7cc66dacd9d5d991f7c7d3dcf123799ee1171df9a07126e27ba38
Go 1.22 GOARCH=amd64
Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.22.12-33207288eef7cc66dacd9d5d991f7c7d3dcf123799ee1171df9a07126e27ba38
Go 1.22 GOARCH=amd64
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Go 1.23 GOARCH=amd64
Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.23.6-33207288eef7cc66dacd9d5d991f7c7d3dcf123799ee1171df9a07126e27ba38
Go 1.23 GOARCH=amd64
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists