GOMA uploads too many gomacc.*.INFO.* files to server, which is slow. |
||||
Issue descriptionIn case of some unexpected failing case, gomacc outputs gomacc.*.INFO.* log files per process, which means we have many gomacc log files. For future investigation, these are being uploaded to cloud storage. However, it can take time (>10mins). Practically, those files are small, so we'd probably want to archive them, and upload it as one .tgz file, to reduce uploading duration. Note: According to offline chat with shinyak@, in some cases, only a few gomacc log file may contain important info, so filtering won't work and it is necessary to upload all the files. This is turned out during the goma support on ChromeOS bot, but it is not limited to ChromeOS.
,
May 12 2017
,
Oct 4 2017
taking
,
Oct 10 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/0890b0faa4b9551788d3f18f0ea26e591137726e commit 0890b0faa4b9551788d3f18f0ea26e591137726e Author: Shinya Kawanaka <shinyak@chromium.org> Date: Tue Oct 10 12:31:03 2017 Upload gomacc logs Uploading gomacc logs was disabled before (revision 7d62f59) since the number of gomacc logs is large and uploading one by one takes long time. In this patch, we make a tarball for gomacc logs, and upload it. BUG= chromium:719843 TEST=Ran goma_util_unittest Change-Id: Ie0fe37ff34b8e4b8f163b3ba798ef67883d571b2 Reviewed-on: https://chromium-review.googlesource.com/702082 Commit-Ready: Shinya Kawanaka <shinyak@chromium.org> Tested-by: Shinya Kawanaka <shinyak@chromium.org> Reviewed-by: Hidehiko Abe <hidehiko@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/0890b0faa4b9551788d3f18f0ea26e591137726e/cbuildbot/goma_util.py [modify] https://crrev.com/0890b0faa4b9551788d3f18f0ea26e591137726e/cbuildbot/goma_util_unittest.py
,
Feb 28 2018
now gomacc logs are uploaded with zipping |
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, May 11 2017