-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
acceptance: TestDockerJava failed #58951
Comments
(acceptance).TestDockerJava failed on master@a786c51627fe66e47b4a4445c67b2a9077ae2a93:
MoreParameters:
See this test on roachdash |
(acceptance).TestDockerJava failed on master@6a51818a234d698afff870e99b705522f62f3b19:
MoreParameters:
See this test on roachdash |
(acceptance).TestDockerJava failed on master@81a2c26a104fa8cc7e8b530b837ffb6ff85ddc5a:
MoreParameters:
See this test on roachdash |
@nkodali Why was this added to the dev-inf board? |
Thank you for the context @nkodali. Removing from the dev inf board. |
(acceptance).TestDockerJava failed on master@75cd4a4937c4093cad8cf33009d630bf4088c43e:
MoreParameters:
See this test on roachdash |
(acceptance).TestDockerJava failed on master@ef900a2a4c83236426592f11ee64e6c3a9ba4140:
MoreParameters:
See this test on roachdash |
@nvanbenschoten what is the correct project board for this issue? |
(acceptance).TestDockerJava failed on master@d67d6ccf9604d0febc46512463dd8f1165872a03:
MoreParameters:
See this test on roachdash |
(acceptance).TestDockerJava failed on master@3e4d80ddb4b913d8af5d66a364b3870e1f7a49fa:
MoreParameters:
See this test on roachdash |
(acceptance).TestDockerJava failed on master@a77bf4410209740fa33428f648997d85185a549b:
MoreParameters:
See this test on roachdash |
(acceptance).TestDockerJava failed on master@ca60935df431525717592574475f34b5ed422ea9:
MoreParameters:
See this test on roachdash |
Caused by #58955 |
closing due to lack of re-occurrence. |
86815: insights: report high contention time r=matthewtodd a=matthewtodd This change aims to align with the logic for selecting transactions with "high contention time"[^1] in the transaction insights UI, but in practice, it's a best effort: Because of the sampling nature of tracing and because a transaction with "high" contention may be composed of many statements, each with only a little contention, there's not a guarantee that a highly contented transaction will be composed of highly contended statements. But, on balance, the best effort is still valuable, and we will call out actionable statements with high contention. [^1]: Note that the protobuf enum name change is safe here as we haven't yet deployed this code. Release justification: Category 2: Bug fixes and low-risk updates to new functionality. Release note: None 86846: storage: additional `TestMVCCHistories` cases for scan/get r=jbowens a=erikgrinaker Touches #86655. Release justification: non-production code changes Release note: None 86862: acceptance: fix spurious docker test failure `unexpected extra event &{0 die} (after [])` r=rickystewart,renatolabs a=knz Needed for #86049. The root cause of the issue is that the docker container for the DB nodes were crashing, because the test framework **was incorrectly deleting the data/log directory before shutting down the nodes**. However, this root cause was mostly hidden because of another mistake: the assertion that checks the health of the nodes was not doing its job properly in most cases. So it believed the nodes were healthy when in fact they were not. This PR fixes both problems. Informs #58955. Informs #58951. Informs #58218. Release justification: non-production code changes 86865: ttl: remove unused const expiredRowsPerRange r=knz a=ecwall fixes #86838 Release justification: Linter fix. Release note: None Co-authored-by: Matthew Todd <[email protected]> Co-authored-by: Erik Grinaker <[email protected]> Co-authored-by: Raphael 'kena' Poss <[email protected]> Co-authored-by: Evan Wall <[email protected]>
(acceptance).TestDockerJava failed on master@b9eb459b18369041f9e67c4830aa316e9d2ca0f0:
More
Parameters:
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: