We had one of our jenkins test get into an endless loop during restructuring our source base.
The test would print one line per 10 seconds. The build log file grew endless, until the disk was full.

After the user quota of the filesystem was filled up, jenkins would continue to fill the root reserve by issuing repetive syslog messages that the disk was full (for the user).

Jenkins did not abort the job.

There should be a way to limit the output file size of the build log like a quota; once it reaches that (or no more space is available) it should abort the job.