Failure: Create Draft Release workflow about go-mod-vendor HOT 3 CLOSED

@paketo-buildpacks/go-maintainers this looks like an issue with the integration test assuming a given order of go mod vendor:

The tests expect one ordering (BurntSushi/toml, then satori/go.uuid)

                <string>"  Executing build process",
                <string>"    Running 'go mod vendor'",
                <*matchers.MatchRegexpMatcher | 0xc0004e8d20>{
                    Regexp: "      go: downloading github.com/BurntSushi/toml v.+",
                    Args: nil,
                },
                <*matchers.MatchRegexpMatcher | 0xc0004e8d50>{
                    Regexp: "      go: downloading github.com/satori/go.uuid v.+",
                    Args: nil,
                },

But the buildpack actually ran in a different order (satori/go.uuid followed by BurntSushi/toml)

              Executing build process
                Running 'go mod vendor'
                  go: downloading github.com/satori/go.uuid v1.1.0
                  go: downloading github.com/BurntSushi/toml v0.3.1

I think the test can most easily be fixed by having separate statements for each of the lines - essentially abandoning ordering.

This ordering is likely non-deterministic, hence why it passed in the PR.

from go-mod-vendor.

I am putting a pr together that changes the regex so that is expects one of those two in each slot allowing for both to be in either position.

from go-mod-vendor.

Another failure occurred: https://github.com/paketo-buildpacks/go-mod-vendor/actions/runs/6281163496

from go-mod-vendor.