New issue
Advanced search Search tips

Issue 798801 link

Starred by 2 users
Status: Closed
Owner: ----
Closed: Jan 20
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 3
Type: Bug



Sign in to add a comment

autorun script uses /dev/null before it's created

Project Member Reported by sergeyu@chromium.org, Jan 3 2018 
I often see the following message when running Fuchsia unittests locally:

[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent
[00001.603] 01444.01513> /system/cr_autorun: 3: /system/cr_autorun: cannot create /dev/null: Directory nonexistent

Usually there is about hundred of these and then they stop. Zircon starts cr_autorun while devmgr is still initializing and /dev/null may not exist at this point.
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 4 2018 

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

commit 5e5ad237237f7d2afd18eb06803a8b646ce9b518
Author: Sergey Ulanov <sergeyu@chromium.org>
Date: Thu Jan 04 00:21:07 2018

[Fuchsia] Workaround ping bug in runner scripts

Fuchsia exe runner script waits for "ping google.com" to succeed
before launching the target to ensure it's launched after network is
configured. Due to bug in Fuchsia (see NET-336) ping never succeeds.
Workaround this bug by running ping with -c0. This allows to wait for
DNS resolion to succeed without sending any pings.

Also added a sleep 1 to avoid log noise caused by  bug 798801 

Bug:  798801 
Change-Id: I2fb9f2a8e1608304ebf7007f767c6deb2b43b295
Reviewed-on: https://chromium-review.googlesource.com/848516
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#526867}
[modify] https://crrev.com/5e5ad237237f7d2afd18eb06803a8b646ce9b518/build/fuchsia/runner_common.py

Comment 2 by w...@chromium.org, Jan 20 (2 days ago)

Status: Closed (was: Untriaged)
No sign of this recently.
►

Sign in to add a comment