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

Issue 623147 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[B1758] Replace Lars DVT with PVT and setup conductive rig

Project Member Reported by tienchang@chromium.org, Jun 24 2016

Issue description

Steps:
  Verify device (asset tag: C051086) powers on and boots
  Switch dev mode
  Install ToT test image
  Confirm write-protect is disabled (flashrom -p host --wp-status; flashrom -p ec --wp-status; flashrom -p ec:dev=1 --wp-status)
  Check for servo debug header
  Install servo cable
  Install pigtails
  Verify no firmware screen on boot
  Install factory firmware (chromeos-firmwareupdate --mode=factory)
  Boot test image in dev mode (3 finger, insert USB w/ test image)
  Run chromeos-tpm-recovery to clear TPM; reboot
  Switch to normal mode (/usr/share/vboot/bin/setgbbflags.sh 0)
  Run network_WiFi_VerifyRouter on test-station
  Connect servo and run platform_InstallTestImage on test-station
  Replace device in B1758 at android1758-row4-rack3-host2
  Update autotest with labels: conductive:True (ask Tien or Aashutosh)
  Run network_WiFi_VerifyRouter in B1758
  Run platform_InstallTestImage in B1758
  Return Lars DVT to white cabinet (ask Tien or Aashutosh)
  Update spreadsheet (go/wifi-device-life-cycle)
 
Status: Started (was: Assigned)
Verify device (asset tag: C051086) powers on and boots Done
Switch dev mode Done
Install ToT test image Done

Comment 2 by jongkyuj@google.com, Jul 11 2016

Check for servo debug header DOne
Install servo cable Done
Install pigtails Done

Comment 3 by jongkyuj@google.com, Jul 14 2016

Confirm write-protect is disabled (flashrom -p host --wp-status; flashrom -p ec --wp-status; flashrom -p ec:dev=1 --wp-status) Done
Verify no firmware screen on boot Done
  Install factory firmware (chromeos-firmwareupdate --mode=factory) Done
  Boot test image in dev mode (3 finger, insert USB w/ test image) Done
  Run chromeos-tpm-recovery to clear TPM; reboot Done

Comment 4 by jongkyuj@google.com, Jul 14 2016

Run network_WiFi_VerifyRouter on test-station Done

/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -56
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -57
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -42
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -49
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -45
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -51
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -56
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -59
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -42
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -49
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -45
/tmp/test_that_results_y3Klmn/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -51
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Comment 5 by jongkyuj@google.com, Jul 15 2016

Connect servo and run platform_InstallTestImage on test-station Done


12:09:03 INFO | autoserv| Power cycling DUT through servo.
12:09:03 INFO | autoserv| Setting power_state to off
12:09:20 INFO | autoserv| Setting prtctl4_pwren to off
12:09:22 INFO | autoserv| Setting power_state to on
12:09:22 INFO | autoserv| Waiting for DUT to come back up.
12:10:46 INFO | autoserv| [stderr] mux_client_request_session: read from master failed: Broken pipe
12:10:46 INFO | autoserv| [stderr] Warning: Permanently added 'chromeos1-test-station.cros,172.27.214.175' (RSA) to the list of known hosts.
12:10:46 INFO | autoserv| GOOD  platform_InstallTestImage       platform_InstallTestImage       timestamp=1468602646    localtime=Jul 15 12:10:46       completed successfully
12:10:46 INFO | autoserv| END GOOD      platform_InstallTestImage       platform_InstallTestImage       timestamp=1468602646    localtime=Jul 15 12:10:46
12:10:46 INFO | autoserv| Finished processing control file
12:10:46 INFO | autoserv| Starting master ssh connection '/usr/bin/ssh -a -x -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_99kTr3ssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/tmp/tmpb_i4Ga -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=300 -l root -p 22 chromeos1-test-station.cros'
12:10:48 INFO | autoserv| Starting master ssh connection '/usr/bin/ssh -a -x   -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_69lIIqssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos1-test-station.cros'
12:10:48 INFO | autoserv| There are no orphaned crashes; deleting /tmp/test_that_results_woF2SN/results-1-platform_InstallTestImage/crashinfo.chromeos1-test-station.cros
12:10:50 INFO | autoserv| record_state_duration failed: job_or_task_id=None, hostname=chromeos1-test-station.cros, status=Running
-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_woF2SN/results-1-platform_InstallTestImage                           [  PASSED  ]
/tmp/test_that_results_woF2SN/results-1-platform_InstallTestImage/platform_InstallTestImage [  PASSED  ]
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Comment 6 by jongkyuj@google.com, Jul 15 2016

Switch to normal mode (/usr/share/vboot/bin/setgbbflags.sh 0) Done

Comment 7 by jongkyuj@google.com, Jul 18 2016

Update autotest with labels: conductive:True Done

Comment 8 by jongkyuj@google.com, Jul 19 2016

Status: Fixed (was: Started)
Replace device in B1758 at android1758-row4-rack3-host2 Done

jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host2
PING android1758-row4-rack3-host2.cros.corp.google.com (100.107.127.97) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-97.mtv.corp.google.com (100.107.127.97): icmp_seq=1 ttl=60 time=0.882 ms
64 bytes from dhcp-100-107-127-97.mtv.corp.google.com (100.107.127.97): icmp_seq=2 ttl=60 time=1.02 ms
^C
--- android1758-row4-rack3-host2.cros.corp.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.882/0.952/1.022/0.070 ms
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host2-router
PING android1758-row4-rack3-host2-router.cros.corp.google.com (100.107.127.98) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-98.mtv.corp.google.com (100.107.127.98): icmp_seq=1 ttl=60 time=0.647 ms
64 bytes from dhcp-100-107-127-98.mtv.corp.google.com (100.107.127.98): icmp_seq=2 ttl=60 time=0.913 ms
^C
--- android1758-row4-rack3-host2-router.cros.corp.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.647/0.780/0.913/0.133 ms
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host2-servo
PING android1758-row4-rack3-host2-servo.cros.corp.google.com (100.107.127.99) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-99.mtv.corp.google.com (100.107.127.99): icmp_seq=1 ttl=60 time=1.08 ms
64 bytes from dhcp-100-107-127-99.mtv.corp.google.com (100.107.127.99): icmp_seq=2 ttl=60 time=0.587 ms
^C
--- android1758-row4-rack3-host2-servo.cros.corp.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.587/0.837/1.088/0.252 ms
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host2-pcap
PING android1758-row4-rack3-host2-pcap.cros.corp.google.com (100.107.127.100) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-100.mtv.corp.google.com (100.107.127.100): icmp_seq=1 ttl=60 time=0.949 ms
64 bytes from dhcp-100-107-127-100.mtv.corp.google.com (100.107.127.100): icmp_seq=2 ttl=60 time=0.818 ms
^C
--- android1758-row4-rack3-host2-pcap.cros.corp.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.818/0.883/0.949/0.071 ms

Comment 9 by jongkyuj@google.com, Jul 19 2016

Run network_WiFi_VerifyRouter in B1758 Done


-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -40
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -60
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -80
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -52
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -44
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -53
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -40
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -60
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -81
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -53
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -44
/tmp/test_that_results_0dVaPC/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -53
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)
Update autotest with labels: conductive:True Done
Update spreadsheet (go/wifi-device-life-cycle) Done


Return Lars DVT to white cabinet Done

Updated missing labels. Will check matfunc if it is running all the test for verification. 

Sign in to add a comment