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

Issue 691664 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

jetstream project unit test segfaults

Project Member Reported by ejcaruso@chromium.org, Feb 13 2017

Issue description

arkham has been failing since build 849 and whirlwind since build 1576 with a sigsegv in the UnitTest step (specifically, DeviceRegistrationInfoTest.RegisterDevice). Example logs are here: https://uberchromegw.corp.google.com/i/chromeos/builders/arkham-release/builds/849/steps/UnitTest/logs/stdio

Seems to be timed with this CL going in: https://chromium-review.googlesource.com/c/433081/ since the libweave version was r108 in passing builds.
 
Just ran another trybot, which failed in the same way but on a different test: https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/8981/steps/UnitTest/logs/stdio

Looks like we might be dealing with some kind of uninitialized memory or test order dependencies here.
Cc: benchan@chromium.org
Cc: -benchan@chromium.org ejcaruso@chromium.org
Owner: benchan@chromium.org
Status: Started (was: Untriaged)
Status: Fixed (was: Started)
Fixed in https://weave-review.googlesource.com/c/8651

Comment 5 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 6 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 7 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 8 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment