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

Issue 655849 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Run signer unittests in the PreCQ and/or CQ.

Project Member Reported by dgarr...@chromium.org, Oct 13 2016

Issue description

I recently broke the signers with the following bad CL.

https://chrome-internal-review.googlesource.com/#/c/293136/

Fix:
https://chrome-internal-review.googlesource.com/#/c/296096/


Test Fix)

We should update those tests to include the code path I broke. Possibly the network tests which I didn't run would have caught the problem.


PreCQ)

It would be nice to run the signer unittests when submitting changes. Maybe we could setup a PreCQ builder that runs them (including the network tests), and test/submit signer CLs with only PreCQ verification (the CQ doesn't add any more value).

 

Comment 1 by vapier@chromium.org, Oct 14 2016

signing_unittest.py caught the error.  it's not run as part of preupload because it's way too slow -- it actually signs images.

i don't think we want to run the tests as part of the normal flow as the tests can take like 15 minutes on an unloaded system, and requires root access (to mount images and such).  adding a specific precq bot that we could list in the repo's COMMIT-QUEUE.ini should be fine though.
I'm trying to decide how to best run the tests.

How about a makefile or script in cros-signing, just so the builder doesn't have to have a hard coded list of tests to run?

Comment 3 by vapier@chromium.org, Oct 14 2016

adding a run_tests runner akin to chromite shouldn't be a problem.  the bigger question is how the bot runs.  i guess we create a new simple bot that just runs the code ?  we don't need a chroot or anything ...
Exactly what I was thinking. That's fairly easy to do now, and we have several of them.

Comment 5 Deleted

Comment 6 Deleted

Project Member

Comment 7 by bugdroid1@chromium.org, Oct 14 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/cros-signing/+/97176ab56c384ab61ded295bfb7e5f1ab7486ff1

commit 97176ab56c384ab61ded295bfb7e5f1ab7486ff1
Author: Mike Frysinger <vapier@chromium.org>
Date: Fri Oct 14 03:24:15 2016

Labels: -current-issue
Owner: dgarr...@chromium.org
Looks like the first part (run_tests runner) is done, I'll assign to Don for now the second part (how the bot runs).


Project Member

Comment 9 by bugdroid1@chromium.org, Nov 11 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/cros-signing/+/6969a5227826d529b0b3ca1c7303de24efbad4d1

commit 6969a5227826d529b0b3ca1c7303de24efbad4d1
Author: Mike Frysinger <vapier@chromium.org>
Date: Wed Nov 02 20:22:57 2016

Project Member

Comment 10 by bugdroid1@chromium.org, Nov 11 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/cros-signing/+/6969a5227826d529b0b3ca1c7303de24efbad4d1

commit 6969a5227826d529b0b3ca1c7303de24efbad4d1
Author: Mike Frysinger <vapier@chromium.org>
Date: Wed Nov 02 20:22:57 2016

Project Member

Comment 11 by bugdroid1@chromium.org, Nov 11 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/cros-signing/+/736f764cafe4387915b6bbcbb0c3c08fd7d924eb

commit 736f764cafe4387915b6bbcbb0c3c08fd7d924eb
Author: Don Garrett <dgarrett@google.com>
Date: Sat Oct 15 02:19:19 2016

Project Member

Comment 12 by bugdroid1@chromium.org, Nov 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/00ab44da049c4916b2386f3cdc7fe23c3f197faa

commit 00ab44da049c4916b2386f3cdc7fe23c3f197faa
Author: Don Garrett <dgarrett@google.com>
Date: Sat Oct 15 02:21:04 2016

signer-pre-cq: Create new signer unittests precq builder.

Create a new build config, build class, test stage, and test command all
dedicated to running the cros-signing unittests. After we test that this
builder works correctly, we can use it to verify signer changes via a
COMMIT-QUEUE.ini for that git repository.

CQ-DEPEND=CL:*297397
BUG= chromium:655849 
TEST=run_tests
     cbuildbot --buildbot --debug --nobootstrap --noreexec \
       --buildroot <dir> -g *297397 signer-pre-cq

Change-Id: I5e46f9b63d83338c502eb0be44c4108b22d2e6e2
Reviewed-on: https://chromium-review.googlesource.com/399583
Commit-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/00ab44da049c4916b2386f3cdc7fe23c3f197faa/cbuildbot/commands.py
[modify] https://crrev.com/00ab44da049c4916b2386f3cdc7fe23c3f197faa/cbuildbot/chromeos_config.py
[modify] https://crrev.com/00ab44da049c4916b2386f3cdc7fe23c3f197faa/cbuildbot/config_dump.json
[modify] https://crrev.com/00ab44da049c4916b2386f3cdc7fe23c3f197faa/cbuildbot/stages/test_stages.py
[modify] https://crrev.com/00ab44da049c4916b2386f3cdc7fe23c3f197faa/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/00ab44da049c4916b2386f3cdc7fe23c3f197faa/cbuildbot/builders/test_builders.py

Status: Started (was: Untriaged)
Project Member

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

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/cros-signing/+/f18b8cb313993421a2016189f293fa8b5ab0315b

commit f18b8cb313993421a2016189f293fa8b5ab0315b
Author: Don Garrett <dgarrett@google.com>
Date: Wed Nov 16 22:47:24 2016

Status: Fixed (was: Started)
We now test and submit signer CLs from the PreCQ.
thanks!

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

Labels: VerifyIn-58

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

Labels: VerifyIn-59

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

Labels: VerifyIn-60
Labels: VerifyIn-61

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

Status: Archived (was: Fixed)

Sign in to add a comment