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

Issue 647542 link

Starred by 1 user
Status: Archived
Owner:
█ dschimmels@chromium.org
Last visit > 30 days ago
Closed: Jul 31
Cc:
aashuto...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[B1758] Install Sabin EVT and servo

Project Member Reported by tienchang@chromium.org, Sep 16 2016 
Steps:
  Verify device (asset tag: C058490) powers on and boots
  Switch to dev mode
  Install ToT test image
  Add servo and servo cable
  Install into open spot 
  Run network_WiFi_VerifyRouter
  Run platform_InstallTestImage
  Add to autotest with labels: sabin, board:sabin, pool:wificell, conductive:False, servo
  Update spreadsheet
  Update wifi_release script

Comment 1 by jongkyuj@google.com, Sep 21 2016 

Verify device (asset tag: C058490) powers on and boots Done
Switch to dev mode Done
Install ToT test image Done(Installed Kefka TOT image).

Comment 2 by jongkyuj@google.com, Sep 22 2016 

Add servo and servo cable Done
Run network_WiFi_VerifyRouter Done

-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -33
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -17
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -22
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -17
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -25
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -17
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -33
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -19
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -22
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -16
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -24
/tmp/test_that_results_ZYF9ze/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -21
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Comment 3 by jongkyuj@google.com, Sep 26 2016

Status: Started (was: Assigned)
Install into open spot Done
android1758-cros-rack1-host1

ongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host1
PING android1758-cros-rack1-host1.cros.corp.google.com (100.107.126.135) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-135.mtv.corp.google.com (100.107.126.135): icmp_seq=1 ttl=60 time=1.36 ms
64 bytes from dhcp-100-107-126-135.mtv.corp.google.com (100.107.126.135): icmp_seq=2 ttl=60 time=1.50 ms
64 bytes from dhcp-100-107-126-135.mtv.corp.google.com (100.107.126.135): icmp_seq=3 ttl=60 time=1.46 ms
^C
--- android1758-cros-rack1-host1.cros.corp.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.365/1.444/1.506/0.058 ms
jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host1-router
PING android1758-cros-rack1-host1-router.cros.corp.google.com (100.107.126.136) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-136.mtv.corp.google.com (100.107.126.136): icmp_seq=1 ttl=60 time=0.909 ms
64 bytes from dhcp-100-107-126-136.mtv.corp.google.com (100.107.126.136): icmp_seq=2 ttl=60 time=0.927 ms
64 bytes from dhcp-100-107-126-136.mtv.corp.google.com (100.107.126.136): icmp_seq=3 ttl=60 time=1.04 ms

Comment 4 by jongkyuj@google.com, Sep 26 2016 

Add to autotest with labels: sabin, board:sabin, pool:wificell, conductive:False, servo Done
Update spreadsheet Done

Comment 5 by jongkyuj@google.com, Sep 26 2016 

Run network_WiFi_VerifyRouter B1758 Done

-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -25
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -4
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -16
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -9
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -19
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -6
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -25
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -6
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -15
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -9
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -19
/tmp/test_that_results_VG7SC_/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -7
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Comment 6 by jongkyuj@google.com, Sep 27 2016 

Able to ping DUT/Router/Servo

jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host1
PING android1758-cros-rack1-host1.cros.corp.google.com (100.107.126.135) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-135.mtv.corp.google.com (100.107.126.135): icmp_seq=1 ttl=60 time=1.49 ms
64 bytes from dhcp-100-107-126-135.mtv.corp.google.com (100.107.126.135): icmp_seq=2 ttl=60 time=1.37 ms
^C
--- android1758-cros-rack1-host1.cros.corp.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1004ms
rtt min/avg/max/mdev = 1.378/1.438/1.498/0.060 ms
jongkyuj@jongkyuj0:~$ ^C
jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host1-router
PING android1758-cros-rack1-host1-router.cros.corp.google.com (100.107.126.136) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-136.mtv.corp.google.com (100.107.126.136): icmp_seq=1 ttl=60 time=1.03 ms
^C
--- android1758-cros-rack1-host1-router.cros.corp.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.035/1.035/1.035/0.000 ms
jongkyuj@jongkyuj0:~$ ^C
jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host1-servo
PING android1758-cros-rack1-host1-servo.cros.corp.google.com (100.107.126.137) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-137.mtv.corp.google.com (100.107.126.137): icmp_seq=1 ttl=60 time=1.36 ms
64 bytes from dhcp-100-107-126-137.mtv.corp.google.com (100.107.126.137): icmp_seq=2 ttl=60 time=0.662 ms
Project Member

Comment 7 by bugdroid1@chromium.org, Oct 5 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/crostestutils/+/1084d3a6d20056c9f2bb528a86bc76da4fdd98ba

commit 1084d3a6d20056c9f2bb528a86bc76da4fdd98ba
Author: jongkyuj <jongkyuj@google.com>
Date: Wed Oct 05 15:16:43 2016

Adding kefka/cave/sabin/asuka/kevin

BUG=chromium:648691, chromium:647545 , chromium:647543 , chromium:647542 , chromium:647544 
TEST=presubmit passes

Change-Id: I6dae7887a06391b0c47f760db039b7f2d880f4b1
Reviewed-on: https://chromium-review.googlesource.com/393408
Tested-by: Jong Kyu Jung <jongkyuj@google.com>
Reviewed-by: Tien Chang <tienchang@chromium.org>

[modify] https://crrev.com/1084d3a6d20056c9f2bb528a86bc76da4fdd98ba/provingground/run_wifi_release_suite.sh

Comment 8 by jongkyuj@google.com, Oct 5 2016

Status: Fixed (was: Started)
Update wifi_release script Done

Comment 9 by dchan@chromium.org, Oct 7 2016

Labels: VerifyIn-55

Comment 10 by aashuto...@chromium.org, Oct 10 2016

Status: Assigned (was: Fixed)
I was not able to find the device in cautotest.

Comment 11 by jongkyuj@google.com, Oct 18 2016

Status: Fixed (was: Assigned)
This host got moved to below host name:
chromeos9-row1-cart1-host1

jongkyuj@jongkyuj0:~$ ping chromeos9-row1-cart1-host1
PING chromeos9-row1-cart1-host1.cros.corp.google.com (100.115.97.1) 56(84) bytes of data.
64 bytes from 100.115.97.1: icmp_seq=1 ttl=60 time=1.02 ms
64 bytes from 100.115.97.1: icmp_seq=2 ttl=60 time=1.31 ms

Comment 12 by aashuto...@chromium.org, Oct 31 2016

Status: Assigned (was: Fixed)
chromeos9-row1-cart1-host1  is a kefka device. There is a mismatch between the wifi device cycle spreadsheet and autotest entry 
https://ubercautotest.corp.google.com/afe/#tab_id=view_host&object_id=5838

Can you check on this?

sshin chromeos9-row1-cart1-host1
Warning: Permanently added 'chromeos9-row1-cart1-host1.cros.corp.google.com' (RSA) to the list of known hosts.
localhost ~ # cat /etc/lsb-release 
CHROMEOS_RELEASE_APPID={2EDF7C6D-6586-D292-0B61-4A33B62E3BF6}
CHROMEOS_BOARD_APPID={2EDF7C6D-6586-D292-0B61-4A33B62E3BF6}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOOK
CHROMEOS_ARC_VERSION=3412574
CHROMEOS_RELEASE_BUILDER_PATH=kefka-release/R56-8947.0.0
GOOGLE_RELEASE=8947.0.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=kefka
CHROMEOS_RELEASE_BUILD_NUMBER=8947
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_CHROME_MILESTONE=56
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=8947.0.0 (Official Build) dev-channel kefka test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=8947.0.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2

Comment 13 by tienchang@chromium.org, Nov 7 2016

Owner: dschimmels@chromium.org
Reassigning to dschimmels@ to pass onto donator@. After these bugs are completed, we can file bugs with Buganizer and assign directly to donator@.

Comment 14 by briannorris@chromium.org, Jul 31

Status: Archived (was: Assigned)
►

Sign in to add a comment