New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 716271 link

Starred by 1 user
Status: Fixed
Owner:
█ dshi@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Consider capping offload size in gs_offloader

Reported by jrbarnette@chromium.org, Apr 28 2017 
Currently, when we offload test results in gs_offloader,
we unconditionally upload everything.  We should consider
putting a cap on the per job size, to prevent large results
from overwhelming a shard.

Comment 1 by jrbarnette@chromium.org, Apr 28 2017 

This is related to but different from  bug 716218 , which
suggests capping the data transferred on the DUT->shard
data path.  This bug should help protect against large
server-side results being copied.  It could also help
with keeping local shard storage under control.  Large
test result directories would be deleted more quickly
and reliably, rather than causing failures with gsutil.

Comment 2 by aut...@google.com, Jun 2 2017

Labels: -current-issue

Comment 3 by akes...@chromium.org, Jun 12 2017

Owner: dshi@chromium.org
Status: Assigned (was: Available)
Probably a dupe of another bug you're working on.

Comment 4 by dshi@chromium.org, Oct 6 2017

Status: Fixed (was: Assigned)
Taken care by result throttling already.

Comment 5 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 6 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)
►

Sign in to add a comment