Hi Prono, Thanks for letting us know. We had an issue earlier with one of our test: PulsarSinkE2ETes which was hanging and not finishing up due to one of the bug. Later we had fixed it and added the timeout to the test so, it should not generating big logs anymore. We have fixed this issue on 06/09 with PR: https://github.com/apache/incubator-pulsar/pull/1945 So, can you please confirm now, if we are still seeing log issue in the pipeline?
Thanks, Rajana On Wed, Jun 13, 2018 at 11:24 AM, Daniel Pono Takamori <[email protected]> wrote: > 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 > > [0] - https://builds.apache.org/job/pulsar-master/520/ > [1] - https://builds.apache.org/job/pulsar-master/522/ >
