So, the errors are the same

# github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/blockblob
../gomodcache/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v1.0.0/blockblob/chunkwriting.go:273:15: undefined: mmb
../gomodcache/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v1.0.0/blockblob/chunkwriting.go:279:65: undefined: mmb
../gomodcache/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v1.0.0/blockblob/chunkwriting.go:281:22: undefined: mmb
../gomodcache/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v1.0.0/blockblob/chunkwriting.go:287:39: undefined: mmb
../gomodcache/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v1.0.0/blockblob/chunkwriting.go:293:18: undefined: newMMB
../gomodcache/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v1.0.0/blockblob/chunkwriting.go:303:37: undefined: mmb
• core: Total in 127.46s …
error running command: exit status 1

Exited with code exit status 1

When I said "fixed upstream" I meant that the issue I opened in the Azure repo above was closed as fixed with a commit, but I guess that fix hasn't made it into a release yet (I haven't checked).

So, the more general problem is that we (that includes me) don't test these build tags as part of the daily CI builds, so we end up getting these errors very late when we do a binary release. I will try to fix this on my end so I don't have to "revert go-cloud" so frequently.

azblob: fails to build on Dragonfly #3266

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions