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

Issue 659401 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Replace Kevin into grover cell and put Alex into Atlantis

Project Member Reported by tienchang@chromium.org, Oct 26 2016

Issue description

Please complete this by EOW.

Part 1:
Grover cells have 2 boxes - a DUT box and a router box. We'll only be moving the DUT out of the DUT box; please avoid touching the router box, as it is very finicky.

The purpose of Part 1 is to allow Aashutosh to run attenuated performance tests against Kevin.

Part 2:
With the Alex we remove from the grover setup, we'd like to test if  crbug.com/483349  is related to the testbed, the DUT, or something else. 

Part 1 Steps:
  - Lock chromeos9-row1-cart2-host2 and take Kevin to Crux
  - Take a picture of Alex in chromeos1-grover-host4 (take note of the connections - dongles, pigtails, etc)
  - Remove Alex from the setup and place Kevin into the setup (reconnect connections)
  - Run network_WiFi_VerifyAttenuator against the setup
  - Readd to autotest with labels: kevin, board:kevin, pool:groamer, groamercell, wificell

Part 2 Steps:
  - Replace the Falco with Alex in chromeos2-row6-rack1-host5.
  - Readd to autotest with labels: alex or x86-alex, board:alex or x86-alex, pool:wificell, wificell
  - Aashutosh to check test results
 

Comment 1 by jongkyuj@google.com, Oct 26 2016

Status: Started (was: Assigned)
Part 1 Steps:
  - Lock chromeos9-row1-cart2-host2 and take Kevin to Crux Done
  - Take a picture of Alex in chromeos1-grover-host4 (take note of the connections - dongles, pigtails, etc) Done
  - Remove Alex from the setup and place Kevin into the setup (reconnect connections) Done

Comment 2 by jongkyuj@google.com, Oct 26 2016

Readd to autotest with labels: kevin, board:kevin, pool:groamer, groamercell, wificell Done

Instead of replacing DUT, I think we should replace the stumpy with a whirlwind. As this mostly looks like a stumpy issue from the results below,
https://wmatrix.googleplex.com/unfiltered?releases=tot&suites=wifi_matfunc&days_back=20&platforms=falco

I was able to get similar issue resolved with winky recently doing the same. If this fails we can try Part 2. 
Also, while there in Atlantis, Can you check on chromeos2-row11-rack4-host5-servo which is down.

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

Status: Fixed (was: Started)
Replaced the stumpy with conductive Whirlwind router from chromeos2-row11-rack1-host5.
jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack1-host5-router
PING chromeos2-row11-rack1-host5-router.cros.corp.google.com (100.115.244.55) 56(84) bytes of data.
64 bytes from 100.115.244.55: icmp_seq=1 ttl=59 time=1.09 ms
64 bytes from 100.115.244.55: icmp_seq=2 ttl=59 time=0.913 ms
64 bytes from 100.115.244.55: icmp_seq=3 ttl=59 time=0.981 ms
Owner: aashuto...@chromium.org
Status: Assigned (was: Fixed)
keeping this open. 
Owner: jongkyuj@chromium.org
#3 does not seem to have worked. Can we do Part#2 as per Tien's suggestion, 
https://wmatrix.googleplex.com/unfiltered?releases=tot&suites=wifi_matfunc&days_back=5&platforms=falco 

All the testcases are failing with "Router at chromeos2-row11-rack1-host5-router is not pingable." 
ping chromeos2-row11-rack1-host5-router
PING chromeos2-row11-rack1-host5-router.cros.corp.google.com (100.115.244.55) 56(84) bytes of data.
^C
--- chromeos2-row11-rack1-host5-router.cros.corp.google.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4031ms

Note FYI: It could be also a bad ethernet cable or connection causing this. 
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@.

Sign in to add a comment