build(deps): Bump github.com/stretchr/testify from 1.7.2 to 1.7.3

[dependabot]

Bumps github.com/stretchr/testify from 1.7.2 to 1.7.3.

Commits

• 07dc7ee Bump actions/setup-go from 3.1.0 to 3.2.0 (#1191)
• c33fc8d Bump actions/checkout from 2 to 3 (#1163)
• 3c33e07 Added Go 1.18.1 as a build/supported version (#1182)
• e2b56b3 Bump github.com/stretchr/objx from 0.1.0 to 0.4.0
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[torao]

Thank you for reporting, dependabot.

However, it seems to cause SEGV in our environment for the same reason as stretchr/testify#1206.

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4a490a]
goroutine 69 [running]:
testing.tRunner.func1.2({0x110d280, 0x19b3270})
	/opt/hostedtoolcache/go/1.18.3/x64/src/testing/testing.go:1389 +0x366
testing.tRunner.func1()
	/opt/hostedtoolcache/go/1.18.3/x64/src/testing/testing.go:1392 +0x5d2
panic({0x110d280, 0x19b3270})
	/opt/hostedtoolcache/go/1.18.3/x64/src/runtime/panic.go:844 +0x258
sync.(*Mutex).Lock(0x0)
	/opt/hostedtoolcache/go/1.18.3/x64/src/sync/mutex.go:74 +0x2a
github.com/stretchr/testify/mock.(*Mock).AssertExpectations(0xc000237cc0, {0x14923d8, 0xc000b471e0})
	/home/runner/go/pkg/mod/github.com/stretchr/testify@v1.7.3/mock/mock.go:511 +0xa9

mock/mock.go(511)

Fortunately, this PR is not urgent and a newer version 1.7.4 that fixes this issue has been released, so I'm thinking of skipping this version and waiting for a new version to be reported. @tnasu @kokeshiM0chi plz check (if there's a problem, it'll reopen).

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.