You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure why your pull request fixes this. But I needed some time to even notice that not the test fails but rather this is just output from an internal test.
If I run the test (go test -v -race -run TestSubtestPanic -failfast ./suite) on the branch from your 1502-PR, I see no difference in output. Is this correct?
Also wouldn't it be better to somehow manipulate/mark/remove the output from the internal tests? (If that's even possible)
Activity
dolmen commentedon Nov 1, 2023
@linusbarth Could you fix this? I suppose it is related to #1471.
linusbarth commentedon Nov 1, 2023
I'm not sure why your pull request fixes this. But I needed some time to even notice that not the test fails but rather this is just output from an internal test.
If I run the test (
go test -v -race -run TestSubtestPanic -failfast ./suite) on the branch from your 1502-PR, I see no difference in output. Is this correct?Also wouldn't it be better to somehow manipulate/mark/remove the output from the internal tests? (If that's even possible)
suite: fix TestSubtestPanic failure (#1501)
dolmen commentedon Nov 1, 2023
@linusbarth #1502 is just a fix for an issue I found thanks to your mistake, but is NOT the fix for 1501. #1503 IS the fix.
dolmen commentedon Nov 1, 2023
Well. I think that we need both #1502 and #1503. So I will just rebase #1503 on top of #1502.
dolmen commentedon Nov 1, 2023
We have another test failure in
suite:dolmen commentedon Nov 2, 2023
#1503 didn't work.
TestSubtestPanicwasn't the only test to have issues.#1504 is (hopefully) the real fix: use consistent subtest-like names for subtests when running them via testing.InternalTest and testing.RunTests.
suite: fix subtest names (fix stretchr#1501) (stretchr#1504)
merge: deps: update module github.com/stretchr/testify to v1.9.0