Austin Vazquez
Austin Vazquez
@dependabot rebase
@jwilder, lgtm. For the buildkite failure, just need a dco in your commit message.
The load snapshot integration test can sometimes fail with the following: ``` === CONT TestLoadSnapshot machine_test.go:2134: Error Trace: /local/home/buildkite-agent/builds/ip-10-0-0-177-12/firecracker-microvm/firecracker-go-sdk/machine_test.go:2134 /local/home/buildkite-agent/builds/ip-10-0-0-177-12/firecracker-microvm/firecracker-go-sdk/machine_test.go:2260 Error: Received unexpected error: dial tcp 10.168.0.3:22: connect: no route...
GitHub webhook was broken starting October 13th which allowed some pull requests to be merged without buildkite checks. Reverting this change because it is causing failures in main now that...
Even with #449 this change cannot be merged until we drop Go 1.14 and 1.15.
> I was thinking this would make it easier: https://github.com/buildkite-plugins/docker-buildkite-plugin I'll give it a try. I was hoping to have a proof of concept but looks like buildkite does not...
@dependabot rebase
We will not be able to update this further without dropping support for lower versions of Go.
@dependabot ignore this dependency
Discussion with @Kern-- offline, the pipeline is experiencing some build repro issues even with my attempt at a pinning versions, #93, because of the `go get -u` I used with...