New issue
Advanced search Search tips

Issue 817586 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 3
Type: Bug



Sign in to add a comment

New test runner failing on fyi bots

Project Member Reported by scottmg@chromium.org, Feb 28 2018

Issue description

So, not looking good overall:

https://ci.chromium.org/buildbot/chromium.fyi/Fuchsia/?limit=200

Looks like it broke starting at the SDK roll: https://ci.chromium.org/buildbot/chromium.fyi/Fuchsia/14419

qemu-img: /b/s/w/ir/out/Release/fvm.blk.qcow2: Could not open '/b/s/w/ir/third_party/fuchsia-sdk/target/x86_64/fvm.blk': No such file or directory
Could not open backing image to determine size.

but those failures are a bit different than at head-ish: https://ci.chromium.org/buildbot/chromium.fyi/Fuchsia/14446 which look like this:

error: cannot open '/b/s/w/itou9xgy//b/s/w/ir/out/Release/ssh_key'
Failed to copy /b/s/w/itou9xgy//b/s/w/ir/out/Release/ssh_key to ::ssh/ssh_host_ed25519_key

I'm going to flip off --use-new-test-runner on those 4 tests for now.
 
TBRing https://chromium-review.googlesource.com/c/chromium/src/+/942039

Hunting for the build that reverted the sdk, which should have presumably put it back to working? Maybe there was a change in the middle the confused things.
This is the SDK roll back: https://ci.chromium.org/buildbot/chromium.fyi/Fuchsia/14427

And that is indeed when it switched to having trouble with the SSH key.

Comment 3 by w...@chromium.org, Mar 1 2018

Ah, sorry about that. I just rolled back the SDK, rather than the rest of
the changes.

I plan to re-roll SDK tonight to pull in the fdio fix, FWIW
Were there other changes? I didn't actually find anything, so I don't understand why reverting the SDK didn't get it going again.

Comment 5 by w...@chromium.org, Mar 1 2018

I reverted the SDK because the roll broke IPC marshalling of certain kinds of files, but it sounds like one of the changes in the roll was required for the v2 scripts to work correctly (perhaps the FVM migration)?

Comment 6 by w...@chromium.org, Mar 1 2018

Cc: scottmg@chromium.org
Owner: w...@chromium.org
Status: Assigned (was: Unconfirmed)
Assigned to self to roll SDK.
Project Member

Comment 7 by bugdroid1@chromium.org, Mar 1 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/26f4cdcf5fea1eb642e3cabd35c1bd1aaf502303

commit 26f4cdcf5fea1eb642e3cabd35c1bd1aaf502303
Author: Wez <wez@chromium.org>
Date: Thu Mar 01 07:39:27 2018

Roll Fuchsia SDK to 9d4016533477903c796470e7ab46c2e1dad31761.

- Removes sys/resource.h, requiring some additional conditionals around
  includes of that header under OS_POSIX.
- Improves the system PRNG implementation to reduce the potential for
  lock contention.

TBR: scottmg
Bug: 707030,  801353 ,  809660 , 738275,  817241 ,  817586 
Change-Id: I4e01a0b23ad66c060ac7a6776a45329775117886
Reviewed-on: https://chromium-review.googlesource.com/942685
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540093}
[modify] https://crrev.com/26f4cdcf5fea1eb642e3cabd35c1bd1aaf502303/build/fuchsia/update_sdk.py

Comment 8 by w...@chromium.org, Mar 1 2018

Status: Fixed (was: Assigned)

Sign in to add a comment