Issue metadata
Sign in to add a comment
|
device behind moblab test machine down |
||||||||||||||||||||||||
Issue descriptionhttp://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=58194226 From moblab_RunSuite.tgz in https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/58194226-chromeos-test/chromeos2-row5-rack10-host12/?debugUI=DEVELOPERS 192.168.231.102 did not reboot after "update"... """Updating from version 7834.42.0 to R49-7834.42.0.""" See /moblab_RunSuite/results/moblab_logs/results/hosts/192.168.231.102/3-provision/debug/autoserv.DEBUG
,
Apr 12 2016
192.168.231.102 is not pingable. It needs to be manually rebooted.
,
Apr 12 2016
It is not too frequent. The last 2 tries failed. It would be interesting to know why the DUT failed to reboot. Maybe ramoops will tell. Query for status of that moblab test: https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=spreadsheet_view&row=job_tag&column=reason&content=&show_incomplete=true&show_only_latest=false&condition=(%2560test_name%2560+%253D+%2527moblab_RunSuite%2527)+AND+(%2560hostname%2560+%253D+%2527chromeos2-row5-rack10-host12%2527)&show_invalid=false¶meterized_field_0_type=Test+label¶meterized_field_0_value=invalidated
,
Apr 26 2016
,
Nov 3 2016
Fixed the empty status.
,
Jun 8 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by autumn@chromium.org
, Apr 11 2016Status: (was: Untriaged)