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

Issue 845588 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression

Blocked on:
issue 845619



Sign in to add a comment

No results in Stainless since 2018-05-20

Project Member Reported by derat@chromium.org, May 22 2018

Issue description

I don't see test results in Stainless newer than May 20; see e.g. http://stainless/search?view=matrix&row=model&col=build&first_date=2018-05-20&last_date=2018-05-22&test=desktopui_ChromeSanity&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true

There were similar symptoms a bit more than a week ago: http://b/79648769,  issue 842279 

Is there any monitoring for ci_results_archiver (if that's failing again), or at least something that checks that the Stainless frontend is displaying recent results?
 

Comment 1 by derat@chromium.org, May 22 2018

(maybe this is http://g/chromeos-infra-discuss/TnmWSSS64Ek)

Comment 2 by derat@chromium.org, May 22 2018

Internal bug: http://b/80138348
There have been multiple canary failures for various boards since 5/19
or 5/20.  Many/most of the failures are attributable to known bugs that
are already dealt with, or in progress.

Owner: shuqianz@chromium.org
Status: Assigned (was: Untriaged)
There _have_ been ongoing internal alerts regarding "ArchiverExportRateLow".

shuqianz@ - please investigate the following:
  * What's causing the alerts, how to fix them, and whether they're
    contributing to the problem here.
  * Whether there have been any Infra related canary failures
    for the runs after the weekend outage was fixed:
        https://uberchromegw.corp.google.com/i/chromeos/builders/master-release/builds/4241
        https://uberchromegw.corp.google.com/i/chromeos/builders/master-release/builds/4242
        https://uberchromegw.corp.google.com/i/chromeos/builders/master-release/builds/4243

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
Copy from an email thread:

From the linked graph, it looks like the afe_jobs table isn't getting exproted.
Looking at logs under /var/log/ci_results_archiver on the sentinel server, afe_jobs table is exporting 0 entries each time:

INFO 2018-05-22 09:20:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 09:40:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 10:00:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 10:20:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 10:40:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 11:00:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 11:20:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 11:40:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 12:00:03 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 12:20:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 12:40:02 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.
INFO 2018-05-22 13:00:03 afe_jobs [archive_builder.py:173] Success: Exported 0 entries, updated 0 entries.

This suggests that the DB connection to AFE isn't returning correct data to ci_results_archiver.

File a separate bug for the ci_result_archiver service, which I guess is the cause of this issue.
Blockedon: 845619

Comment 8 by ihf@chromium.org, May 22 2018

Cc: ihf@chromium.org
The ci_results_archiver service was broken since 5/20 due to the lab outage we had this Monday. The slave has been recovered, and the ci_results_archiver service is back to normal. Stainless should get test results slowly. 

Comment 10 by pwang@chromium.org, May 22 2018

Cc: pwang@chromium.org

Comment 11 by ihf@chromium.org, May 23 2018

Cc: kinaba@chromium.org

Sign in to add a comment