Closed cockroach-teamcity closed 5 days ago
This is the same with #3635; we increased the per-run timeout but this happened again. #3681 tracks an operation timeout - the underlying cause could be the same.
[07:31:54 ](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_NightlyPebbleMetamorphicCrossversion/15792224?buildTab=log&focusLine=6466&logView=flowAware&linesState=6466) ERROR: signal: killed
[07:31:54 ](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_NightlyPebbleMetamorphicCrossversion/15792224?buildTab=log&focusLine=6467&logView=flowAware&linesState=6467)
[07:31:54 ](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_NightlyPebbleMetamorphicCrossversion/15792224?buildTab=log&focusLine=6468&logView=flowAware&linesState=6468) 58 runs completed, 1 failures, over 3h20m22s
And
Failed to publish artifacts: java.lang.OutOfMemoryError: Java heap space
Oh, https://github.com/cockroachdb/cockroach/pull/125892 increased the timeout but not for this particular build.
Timeout here happened at 20m:
56 runs so far, 0 failures, over 3h0m20s
57 runs so far, 0 failures, over 3h0m25s
...
57 runs so far, 0 failures, over 3h20m20s
. failed with artifacts on refs/heads/master @ ff83363e89ce:
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
/cc @cockroachdb/test-eng
This test on roachdash | Improve this report!