2018-06-13 19:03:57 UTC - Matteo Merli: @Rajan Dhabalia there was this mail on dev@ list. Do you have any reason to suspect on that test?
``` Recently H34 ran out of disk and while looking for culprits I found 2 log files which seem to have been the same: 52G /home/jenkins/jenkins-slave/workspace/pulsar-master/pulsar-broker/target/surefire-reports/org.apache.pulsar.io.PulsarSinkE2ETest-output.txt 52G /tmp/stdout1630697337623691382deferred I believe something went wrong which caused build 520 [0] to have taken so long as well as use 100gb of disk (most build nodes have ~500gb). Job 522 [1] also hung after about 7 hours running (and continued running for 21 hours total), so I had to kill it this morning. While I went ahead and nuked the log file, there is reason to think that your build should be reviewed to see if there are any oddities performed by the job, or evidence of our build nodes misbehaving (this happens from time to time). Thanks for taking a look! -Pono on behalf of Infra ``` ---- 2018-06-13 19:42:01 UTC - Rajan Dhabalia: umm.. I think earlier this test was not finishing up while closing ManagedLedgerFactory and we had fixed by adding timeout in function: <https://github.com/apache/incubator-pulsar/pull/1945> this test uses Bk-Ensembles but I don't think it can consume this much space.. let me take a look on it.. ----
