Hi, We're seeing a lot of 100% full disk space incidents recently on ci-cassndra from Jenkins builds and this is causing your build jobs to queue up and not be executed.
In particular, what stands out is that the Cassandra-trunk build directories have doubled in size in the last few days: 1.5G 2471 - May 12 21:19 3.2G 2476 - May 7 14:26 In the latter case, it seems most of the increased space usage comes from: ./archive/test/logs/_jdk* Can you confirm if this is the new normal for these builds, and thus more disk space will be required? Please also take any other actions you can in order to reduce the size of logs and other output from builds where such output / verbosity is not required. Thanks. Kind regards, -Bob Thomson. ASF Infrastructure
