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

Issue 674263 link

Starred by 1 user
Status: Archived
Owner:
█ ngm@chromium.org
Last visit > 30 days ago
Closed: Dec 2016
Cc:
█ mtomasz@chromium.org
sonnyrao@chromium.org
semenzato@chromium.org
█ vbendeb@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

chromeos-ec unit test failed intermittently

Project Member Reported by akes...@chromium.org, Dec 14 2016

Comment 1 by benchan@chromium.org, Dec 14 2016

Cc: mtomasz@chromium.org semenzato@chromium.org sonnyrao@chromium.org
Owner: ngm@chromium.org
Status: Assigned (was: Untriaged)
This looks like a link error where libcryptoc wasn't compiled with SHA512 support, but ec expects that. But there is a recent change (https://chromium-review.googlesource.com/c/419327/) in platform/ec/chip/g/build.mk and third_party/cryptoc/Makefile that the issue may no longer exist.  +ngm to investigate/confirm


chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha384.o: In function `DCRYPTO_SHA384_init':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha384.c:13: undefined reference to `SHA384_init'
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha384.o: In function `DCRYPTO_SHA384_hash':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha384.c:19: undefined reference to `SHA384_hash'
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha512.o: In function `DCRYPTO_SHA512_init':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha512.c:13: undefined reference to `SHA512_init'
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha512.o: In function `DCRYPTO_SHA512_hash':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha512.c:19: undefined reference to `SHA512_hash'
chromeos-ec-0.0.1-r3505: collect2: error: ld returned 1 exit status
chromeos-ec-0.0.1-r3505: make[2]: *** [Makefile.rules:283: build/cr50/RW/ec.RW.elf] Error 1
chromeos-ec-0.0.1-r3505: make[2]: *** Waiting for unfinished jobs....
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha384.o: In function `DCRYPTO_SHA384_init':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha384.c:13: undefined reference to `SHA384_init'
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha384.o: In function `DCRYPTO_SHA384_hash':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha384.c:19: undefined reference to `SHA384_hash'
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha512.o: In function `DCRYPTO_SHA512_init':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha512.c:13: undefined reference to `SHA512_init'
chromeos-ec-0.0.1-r3505: build/cr50/RW/chip/g/dcrypto/sha512.o: In function `DCRYPTO_SHA512_hash':
chromeos-ec-0.0.1-r3505: /build/rambi/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3505/work/platform/ec/chip/g/dcrypto/sha512.c:19: undefined reference to `SHA512_hash'
chromeos-ec-0.0.1-r3505: collect2: error: ld returned 1 exit status
chromeos-ec-0.0.1-r3505: make[2]: *** [Makefile.rules:283: build/cr50/RW/ec.RW_B.elf] Error 1

Comment 2 by benchan@chromium.org, Dec 14 2016

Cc: vbendeb@chromium.org

Comment 3 by ngm@chromium.org, Dec 15 2016 

Does this issue persist?  I can't seem to reproduce this issue locally.

Comment 4 by benchan@chromium.org, Dec 15 2016

Status: Fixed (was: Assigned)
The issue seems to disappear after https://chromium-review.googlesource.com/c/419327/.

Closing this issue as fixed. Will reopen this issue if it happens again.

Comment 5 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

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

Labels: VerifyIn-59

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

Labels: VerifyIn-60

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

Labels: VerifyIn-61

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

Status: Archived (was: Fixed)
►

Sign in to add a comment