New issue
Advanced search Search tips

Issue 782965 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
vapier@chromium.org
pmalani@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

amd64-generic-asan builder failing peerd_* autotests

Project Member Reported by rahulchaudhry@chromium.org, Nov 8 2017 
The asan builder has been failing in VMTest stage.

Specifically, peerd_DiscoverServices/peerd_AdvertiseServices tests fail.

For example, see https://uberchromegw.corp.google.com/i/chromiumos/builders/amd64-generic-asan/builds/21877

/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-44-peerd_DiscoverServices                                          [  FAILED  ]
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-44-peerd_DiscoverServices                                            ERROR: Command <start peerd PEERD_LOG_LEVEL=3> failed, rc=1, Command returned non-zero exit status
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-44-peerd_DiscoverServices/peerd_DiscoverServices                   [  FAILED  ]
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-44-peerd_DiscoverServices/peerd_DiscoverServices                     ERROR: Command <start peerd PEERD_LOG_LEVEL=3> failed, rc=1, Command returned non-zero exit status
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-48-peerd_AdvertiseServices                                         [  FAILED  ]
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-48-peerd_AdvertiseServices                                           ERROR: Command <start peerd PEERD_LOG_LEVEL=3> failed, rc=1, Command returned non-zero exit status
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-48-peerd_AdvertiseServices/peerd_AdvertiseServices                 [  FAILED  ]
/tmp/cbuildbotiREHbD/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-48-peerd_AdvertiseServices/peerd_AdvertiseServices                   ERROR: Command <start peerd PEERD_LOG_LEVEL=3> failed, rc=1, Command returned non-zero exit status

Comment 1 by vapier@chromium.org, Nov 9 2017

Cc: vapier@chromium.org pmalani@chromium.org
Summary: amd64-generic-asan builder failing peerd_* autotests (was: amd64-generic-asan builder failing VMTest)
peerd tests were passing here:
https://uberchromegw.corp.google.com/i/chromiumos/builders/amd64-generic-asan/builds/21761

but unfortunately, after that, we had problems in buildpackages.  the first run after that was resolved had peerd failures:
https://uberchromegw.corp.google.com/i/chromiumos/builders/amd64-generic-asan/builds/21789

that gives us a range of 10082.0.0 to 10084.0.0:
https://crosland.corp.google.com/log/10082.0.0..10084.0.0

going to guess this CL in that run is the reason:
https://chromium-review.googlesource.com/740042

wifi_bootstrapping/peerd was turned off, but i guess the autotests are still enabled ?  that shouldn't be happening ...

those tests are part of chromeos-base/autotest-tests-peerd, and that package is pulled in by chromeos-base/autotest-all, but only under USE=peerd.  if we look at the build log, that flag isn't set:
[ebuild  rR    ] chromeos-base/autotest-all-0.0.1-r39::chromiumos to /build/amd64-generic/ USE="bluetooth buffet cellular cras cros_disks cros_p2p debugd power_management shill tpm -cheets -chromeless_tests -chromeless_tty -peerd -tpm2 -wifi_bootstrapping -wimax" 0 KiB

so why are these (stale?) autotests getting run ?

Comment 2 by dtapu...@chromium.org, Nov 9 2017

Components: OS>Systems>Network

Comment 3 by cmt...@chromium.org, Nov 9 2017

Cc: avakulenko@chromium.org keybuk@chromium.org
CC'ing the original test authors, to see if they can either help with this bug or assign it to the appropriate people.

Comment 4 by vapier@chromium.org, Nov 10 2017

Cc: -avakulenko@chromium.org -keybuk@chromium.org
neither of them are on CrOS anymore, and i don't think the peerd tests themselves are relevant.  the ebuild's shouldn't have enabled them in the first place which means it looks like a bug in common code.

Comment 5 by cmt...@chromium.org, Feb 5 2018

Components: Tools>ChromeOS-Toolchain

Comment 6 by manojgupta@chromium.org, Feb 15 2018

Status: WontFix (was: Untriaged)
No peerd fails on ToT.
►

Sign in to add a comment