Ticket #739 (new defect)
HTML logs do not get compressed
| Reported by: | marcusl | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | 0.8.+ |
| Version: | 0.7.12 | Keywords: | |
| Cc: |
Description
I recently started adding HTML logs from my buildsystem to buildbot, and these are between 1 and 5 mb per buildstep.
They do not seem to be compressed at all, so there is quite a lot of memory and disk-space taken up by these log files. (One of my masters is using 450mb)
Having the logs gzipped would be neat, since they could then be sent raw to clients who accept gzipped html (most browsers nowadays).
Either that, or we fold the HTML-log and text-log into a generic logging store (with mime-type or something).
Change History
comment:2 Changed 23 months ago by dustin
- Milestone changed from undecided to 0.8.1
If you can decode one of those pickles and find where the logfile is stuck, that should be easy to fix. I'll be happy to backport that to the 0.8.0 release branch.
Compressing them .. harder, but a good project.
comment:3 Changed 18 months ago by dustin
- Priority changed from major to critical
marcus, are you still having this problem? Can you send me a build pickle?
comment:5 Changed 17 months ago by marcusl
Uh. Sorry for the quietness. I didn't see your comments.
I'll get back to this once we update our buildbot install to 0.8.x at work. (within a few months..)
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Also, the build-pickle seems to contain all logs as well (the 555 file is about the size of the sum of all logs below, similar results for other builds:)
I'll try to get some time to test the 0.8 beta and see if it helps, but some initial advice would be nice.