log not scrolling to first failure because server is too slow to respond with failure lines for task in 30 seconds
Categories
(Tree Management :: Treeherder: API, defect)
Tracking
(Not tracked)
People
(Reporter: aryx, Unassigned)
Details
Attachments
(1 file)
The log at https://treeherder.mozilla.org/logviewer?job_id=362971409&repo=autoland doesn't scroll to the first failure line because the request for the failure lines (text_log_errors endpoint) fails to respond in the first 30s and then returns and internal server failure. In a local test setup which queries the stage replica mysql server, the request for the mentioned tasks takes ~50s.
If the bug suggestions don't get added to each failure line, the request gets completed in ~4s.
Marco, Joel, does this endpoint get ingested by you and could the bug_suggestions data be dropped? The question also applies to matches, classified_failures and metadata (that one is an empty table).
|
||
Comment 1•4 years ago
|
||
I will leave that up to :marco, I don't use it for anything specifically.
|
||
Comment 2•4 years ago
|
||
We are not using the failure line yet, but we were planning to as an improvement for mozci in the future. We don't need the bug suggestions though.
From a user perspective, what will change if we drop that data?
|
Reporter | |
Comment 3•4 years ago
•
|
||
The data is not used. The bug suggestions shown are pulled from the faster bug_suggestions endpoint. The bug_suggestions attribute of the text_log_error endpoint was an export vehicle for an autoclassification experiment 6-7 years ago according to the commit history.
| Comment hidden (Intermittent Failures Robot) |
|
|
||
Comment 5•4 years ago
|
||
All right, dropping it sounds fine to me then.
|
||
Comment 6•4 years ago
|
||
Description
•