New issue
Advanced search Search tips

Issue 815314 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 816620
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 3
Type: Bug

Blocking:
issue 738275



Sign in to add a comment

SharedBufferTest.CreateAndPassFromChildReadOnlyBuffer flaked in mojo_unittests on Fuchsia

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

Issue description

https://build.chromium.org/p/chromium.fyi/builders/Fuchsia%20%28dbg%29/builds/16582

https://chromium-swarm.appspot.com/task?id=3bdb38f8aaf6e110&refresh=10&show_raw=1

[00032.755] 03912.03961> [ RUN      ] SharedBufferTest.CreateAndPassFromChildReadOnlyBuffer
[00032.755] 03912.03961> [3:726406807:0223/112915.861622:32238702:WARNING:test_suite.cc(236)] Test launcher output path /tmp/.org.chromium.Chromium.cddhHl/test_results.xml exists. Not adding test launcher result printer.
[00032.756] 03912.03961> [3:603653323:0223/112915.939068:32316151:ERROR:shared_memory_fuchsia.cc(98)] zx_vmar_map failed, status=-30
[00032.756] 03912.03961> [3:603653323:0223/112916.171050:32548136:FATAL:mojo_test_base.cc(138)] Check failed: WaitForSignals(mp, MOJO_HANDLE_SIGNAL_READABLE) == MOJO_RESULT_OK (9 vs. 0)
#00: base::debug::StackTrace::StackTrace(unsigned long) at ??:?
#01: base::debug::StackTrace::StackTrace() at ??:?
#02: logging::LogMessage::~LogMessage() at ??:?
#03: pc 0x41ce1101216e (libbindings.so,0xbc2472f016e)
#04: pc 0x41ce11012e70 (libbindings.so,0xbc2472f0e70)
#05: pc 0x41ce10468d97 (libbindings.so,0xbc246746d97)
#06: pc 0x41ce10468685 (libbindings.so,0xbc246746685)
#07: pc 0x41ce104685a4 (libbindings.so,0xbc2467465a4)
#08: pc 0x41ce10468568 (libbindings.so,0xbc246746568)
#09: pc 0x41ce109fc9ce (libbindings.so,0xbc246cda9ce)
#10: pc 0x41ce109f3082 (libbindings.so,0xbc246cd1082)
#11: pc 0x41ce109de636 (libbindings.so,0xbc246cbc636)
#12: pc 0x41ce109df05d (libbindings.so,0xbc246cbd05d)
#13: pc 0x41ce109dfb1c (libbindings.so,0xbc246cbdb1c)
#14: pc 0x41ce109eac0b (libbindings.so,0xbc246cc8c0b)
#15: pc 0x41ce109fcaae (libbindings.so,0xbc246cdaaae)
#16: pc 0x41ce109f46d2 (libbindings.so,0xbc246cd26d2)
#17: pc 0x41ce109ea839 (libbindings.so,0xbc246cc8839)
#18: pc 0x41ce10ef0ed1 (libbindings.so,0xbc2471ceed1)
#19: pc 0x41ce10eedd6b (libbindings.so,0xbc2471cbd6b)
#20: pc 0x41ce1049e86d (libbindings.so,0xbc24677c86d)
#21: pc 0x41ce1049e7b4 (libbindings.so,0xbc24677c7b4)
#22: pc 0x41ce1049e765 (libbindings.so,0xbc24677c765)
#23: pc 0x41ce1049e6ac (libbindings.so,0xbc24677c6ac)
#24: pc 0x41ce1044968d (libbindings.so,0xbc24672768d)
#25: pc 0x41ce10eff6d7 (libbindings.so,0xbc2471dd6d7)
#26: pc 0x41ce10eff545 (libbindings.so,0xbc2471dd545)
#27: pc 0x41ce10516c77 (libbindings.so,0xbc2467f4c77)
#28: pc 0x672df605050e (libc.so,0x1350e)
[00032.767] 03912.03961>
[00032.768] 03912.03961> [135/969] SharedBufferTest.CreateAndPassFromChildReadOnlyBuffer (CRASHED)
 

Comment 1 by w...@chromium.org, Feb 23 2018

Components: Internals>Mojo>Core
Owner: w...@chromium.org
Status: Assigned (was: Unconfirmed)
This is another case of MOJO_RESULT_FAILED_PRECONDITION, which as per rockot@'s comment on  issue 810448  suggests that the channel was closed without anything being written, suggesting premature child process exit.

I wonder if we might have a race in the Channel implementation under Fuchsia, so that we might exit the process when async send of messages hasn't completed. I think we process simultaneous channel-close + message-received signals correctly, but I'll check that as well.

Aside from that, strange that we're missing symbols for libbindings.so; I'll look into that as well...
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 24 2018

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

commit 6bf8ea114ccf01e5722c4cc3d781e73d1e561106
Author: Scott Graham <scottmg@chromium.org>
Date: Sat Feb 24 04:21:13 2018

fuchsia: Disable SharedBufferTest.CreateAndPassFromChildReadOnlyBuffer

Flaked at:
https://build.chromium.org/p/chromium.fyi/builders/Fuchsia%20%28dbg%29/builds/16582.

TBR: wez@chromium.org
Bug:  815314 
Change-Id: I70e33cd6d91433e26f8f030b692a7ce7d8b52584
Reviewed-on: https://chromium-review.googlesource.com/935671
Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538986}
[modify] https://crrev.com/6bf8ea114ccf01e5722c4cc3d781e73d1e561106/testing/buildbot/filters/fuchsia.mojo_unittests.filter

Comment 3 by w...@chromium.org, Feb 26 2018

Mergedinto: 816620
Status: Duplicate (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 13 2018

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

commit 6a84b3ed1c97d1fad1ebf401dc937e806cc895b7
Author: Wez <wez@chromium.org>
Date: Tue Mar 13 00:16:23 2018

Un-filter some Mojo and IPC tests under Fuchsia.

These tests were flakey due to messages being dropped by the receiver
occasionally when the underlying plaform-specific Channel was closed.

Bug:  764015 ,  764018 ,  756112 ,  810448 ,  815314 ,  816620 
Change-Id: I2b6cfb105660a570c09b29555da7811541d49ec9
Reviewed-on: https://chromium-review.googlesource.com/959674
Commit-Queue: Wez <wez@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542661}
[modify] https://crrev.com/6a84b3ed1c97d1fad1ebf401dc937e806cc895b7/testing/buildbot/filters/fuchsia.ipc_tests.filter
[modify] https://crrev.com/6a84b3ed1c97d1fad1ebf401dc937e806cc895b7/testing/buildbot/filters/fuchsia.mojo_unittests.filter

Sign in to add a comment