Skip to content

Conversation

@dnephin
Copy link
Member

@dnephin dnephin commented Jun 30, 2023

Fixes #266
Closes #265 (those commits are included in this PR)

dolmen and others added 4 commits June 11, 2023 23:26
The test TestRun of the gty-migrate-from-testify tool apparently needs
to have the original packages available to run. So let's install them
("go get" in GOPATH mode, in a temporary directory) before running the
migration test.
…-check

Fix incorrect import path for go-check in gty-migrate-from-testify test:
github.com/go-check/check => gopkg.in/check.v1
…test

Fix test to use the gopkg.in/check.v1 API correctly.

The func TestWithChecker(c *check.C) was incompatible with "go test".
goGet(t, "gopkg.in/check.v1")
goGet(t, "github.com/stretchr/testify/assert")
goGet(t, "github.com/stretchr/testify/require")

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dnephin Why did you revert e4fe373 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like the idea of having to exec the go get command from inside a test. There's nothing special about this test that should require running extra commands which are going to be relatively slow and will fail when there is no network.

I'd like to understand why only the Go1.19 job is failing in CI, that's really surprising to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define a separate Go module for the testify migration tool

3 participants