Some Mac and iOS testers include spindumps. These are very large when extracted out to the results folder on build.webkit.org. (multiple terabytes) We should leave these compressed on disk. simply pre-compressing them on the client, before we create the results archive would be sufficient.
<rdar://problem/34397653>
Created attachment 320654 [details] v1 patch for review
Attachment 320654 [details] did not pass style-queue: ERROR: Tools/ChangeLog:1: ChangeLog entry has no bug number [changelog/bugnumber] [5] Total errors found: 1 in 2 files If any of these errors are false positives, please file a bug against check-webkit-style.
Created attachment 320655 [details] correct ChangeLog to include the bugzilla entry
Comment on attachment 320655 [details] correct ChangeLog to include the bugzilla entry View in context: https://bugs.webkit.org/attachment.cgi?id=320655&action=review looks good assuming you have tested it. > Tools/BuildSlaveSupport/test-result-archive:50 > + shutil.copyfileobj(f_in, f_out) does this compress the file?
Comment on attachment 320655 [details] correct ChangeLog to include the bugzilla entry View in context: https://bugs.webkit.org/attachment.cgi?id=320655&action=review >> Tools/BuildSlaveSupport/test-result-archive:50 >> + shutil.copyfileobj(f_in, f_out) > > does this compress the file? Yes... this is straight from the python docs, so it seems to be the standard way of doing it. https://docs.python.org/2/library/gzip.html
Committed revision 221985.