Skip to content

Conversation

@cpuguy83
Copy link

@cpuguy83 cpuguy83 commented Mar 8, 2016

Use -check.timeout=<duration string> to set a timeout period for each
check. If the timeout is reached, the test suite will panic.

@cpuguy83
Copy link
Author

cpuguy83 commented Mar 8, 2016

This is a replacement for #77 which had a really bad rebase.

@cpuguy83 cpuguy83 force-pushed the per_test_timeouts_orig branch from ceaa520 to e8041e6 Compare March 11, 2016 17:09
Use `-check.timeout=<duration string>` to set a timeout period for each
check. If the timeout is reached, the test suite will panic.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
@cpuguy83 cpuguy83 force-pushed the per_test_timeouts_orig branch from e8041e6 to fd56f06 Compare March 11, 2016 17:20
Copy link
Contributor

@niemeyer niemeyer left a comment

Choose a reason for hiding this comment

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

The idea and the flag looks good. We just need to move the panic to inside the forked call, so that the suite tear down takes place, which means it'll be properly logged and rest of the suite will continue executing.

As a minor, can we please use just testTimeout and TestTimeout instead of checkTimeout and CheckTimeout for the fields? Seems more aligned with existing conventions.

@thaJeztah
Copy link

ping @cpuguy83 PTAL

@cpuguy83 cpuguy83 closed this Jan 6, 2019
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.

3 participants