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

Issue 728876 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

Shards hanging when retrieving test results

Project Member Reported by pho...@chromium.org, Jun 2 2017

Issue description

Running curl locally on the shard chromeos-server26 returns instantly:

chromeos-test@chromeos-server26:~$ curl localhost/results/120840699-chromeos-test/chromeos4-row12-rack11-host3/debug
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/120840699-chromeos-test/chromeos4-row12-rack11-host3/debug">here</a>.</p>
<hr>
<address>Apache/2.4.10 (Ubuntu) Server at localhost Port 80</address>
</body></html>

I'm not sure why it freezes when requested from my desktop or laptop.
Could this be some kind of network or firewall configuration change?
Cc: jrbarnette@chromium.org pprabhu@chromium.org shuqianz@chromium.org
Do we know when this happened?

I see that git versions on most of our servers changed around noon today: https://viceroy.corp.google.com/chromeos/deputy-view#_VG_OuDr13hG

Was there a push-to-prod?
I was just poking around this, and discovered that "https:" fails
as described, but "http:" works just fine.  I've observed this on
two separate hosts.


Following up:  I note that RPC uses "http:", so that's why we've
seen no lab failures being provoked by this problem.

re: #4, Yes, there was a push to prod.

autotest:
f4610bdd3 Revert "autotest: disable video power tests if AC state is unexpected"
e1729bb15 autotest: add `atest server list -N` option to list only hostnames
9857f8754 [moblab] Add new featutre to run suite to limit the tests run.
61060f8dc chrome_cr50: check ccd_lock at the end of the unlock process
5696954d3 autotest: add metric to track whether test_push passes
9a0ce5604 autotest: add test to cr50 responds to CCD disable flag
828e78005 autotest: temporarily remove autotest_SyncControl from push_to_prod
73fd8d86a Add testtracker_owner
568275829 Added required dtbo_a image for some Android devices

Chromite:
2ddf2434 Use USE_GOMA instead of USE.
1881f9dd metrics: Stop catching AttributeError.
3b8eaf1b Update config settings by config-updater.
I've speculatively marked two CLs: Verfied: -1

https://chromium-review.googlesource.com/c/514822/
https://chromium-review.googlesource.com/c/509211/

Could be that SSH update killed the DUTs completely.
#8 is unrelated to this bug. But it recover the CQ ;)
Status: WontFix (was: Started)
Also. https:// never worked, afaict.

Sign in to add a comment