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

Issue 786762 link

Starred by 1 user
Status: Fixed
Owner:
█ kateso...@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
mbarbe...@chromium.org
infe...@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug



Sign in to add a comment

Predator didn't assign culprits for multiple testcases (too slow ? or breakage)

Project Member Reported by infe...@chromium.org, Nov 19 2017 
https://clusterfuzz.com/v2/testcase-detail/5329964571557888
https://clusterfuzz.com/v2/testcase-detail/5449968910598144

Looks like Predator is not pushing results fast enough, can you check why these testcases didn't get results in these hours.

Comment 1 by infe...@chromium.org, Nov 20 2017

Cc: st...@chromium.org
Another example
https://clusterfuzz.com/v2/testcase-detail/6370861975339008

Blame didn't get assigned for 5 hours after blame task is sent to Predator. This is very bad. Can you please prioritize fixing this.

Comment 2 by kateso...@chromium.org, Nov 20 2017 

The process time is less than a minute, but Predator frontend seems to be overwhelmed by the volume of requests (from all clients), it is also related to the DeadlineExceededError.

Comment 3 by kateso...@chromium.org, Dec 7 2017

Cc: mbarbe...@chromium.org infe...@chromium.org
Status: Fixed (was: Assigned)
I didn't see DeadlineExceededError any more.
►

Sign in to add a comment