-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unit test/ci: report when unit test is using either TestServer/TestCluster API #111366
Labels
A-testing
Testing tools and infrastructure
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-testeng
TestEng Team
Comments
cc @cockroachdb/test-eng |
I've made a quick & dirty patch to extract the info. using call stack frames. The diff is below. I am also attaching the resulting tests, which use TestServer/TestCluster, at this time, on master.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-testing
Testing tools and infrastructure
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-testeng
TestEng Team
To enable better tracking of flaky tests which rely on TestServer/TestCluster API [1], we'd like to surface a new parameter in GH issues. E.g., [2] is a unit test which failed during the nightly
stress
run; this test happens to useTestCluster
API. See [3] for private slack discussion.[1] https://cockroachlabs.atlassian.net/wiki/spaces/CRDB/pages/3155427384/TestServer+and+TestCluster
[2] #110187
[3] https://cockroachlabs.slack.com/archives/C023S0V4YEB/p1695754554482619
Jira issue: CRDB-31874
The text was updated successfully, but these errors were encountered: