Tests failing under ARM; Unsupported syscall: 366

Bug #1084635 reported by Product Strategy Coverity Bug Uploader on 2012-11-29
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Online Accounts: libsignon-glib
New
Undecided
Unassigned
Session Menu
Invalid
Undecided
Unassigned
The Sync Menu
Invalid
High
Charles Kerr
qemu-linaro (Ubuntu)
Undecided
Unassigned
Precise
Undecided
Unassigned

Bug Description

Seeing this failure under armhf on Jenkins, will attach a full log. We've found qemu to be flaky in some of these tests; this bug may serve as a placeholder if the cause isn't under our control.

task-0: Running main() from gtest_main.cc

task-0: [==========] Running 9 tests from 1 test case.

task-0: [----------] Global test environment set-up.

task-0: [----------] 9 tests from ClientTest

task-0: [ RUN ] ClientTest.TestNullDesktop

qemu: Unsupported syscall: 366
Unsupported ancillary data: 1/2
task-0: [ OK ] ClientTest.TestNullDesktop (467 ms)

task-0: [ RUN ] ClientTest.TestAccessors

qemu: Unsupported syscall: 366
Unsupported ancillary data: 1/2
task-0: [ OK ] ClientTest.TestAccessors (248 ms)

task-0: [ RUN ] ClientTest.TestGObjectAccessors

qemu: Unsupported syscall: 366
Unsupported ancillary data: 1/2
task-0: [ OK ] ClientTest.TestGObjectAccessors (141 ms)

task-0: [ RUN ] ClientTest.TestCanStartService

qemu: Unsupported syscall: 366
Unsupported ancillary data: 1/2
Activating service name='com.canonical.indicator.sync'
qemu: Unsupported syscall: 366
Unsupported ancillary data: 1/2
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Activated service 'com.canonical.indicator.sync' failed: Process /tmp/buildd/indicator-sync-12.10.5/src/service/indicator-sync-service received signal 11

** (process:27136): ERROR **: unable to create service proxy: Error calling StartServiceByName for com.canonical.indicator.sync: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /tmp/buildd/indicator-sync-12.10.5/src/service/indicator-sync-service received signal 11
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
/bin/bash: line 5: 27136 Trace/breakpoint trap ${dir}$tst
task-0: cleaning up pid 28099

task-0: FAIL: test-client

task-0: ===================

task-0: 1 of 4 tests failed

task-0: ===================

Revision history for this message
Product Strategy Coverity Bug Uploader (coverity-uploader) wrote :
summary: - Tests failing under ARM
+ Tests failing under ARM; Unsupported syscall: 366
Revision history for this message
Product Strategy Coverity Bug Uploader (coverity-uploader) wrote :

Attaching indicator-session log, similar error.

Revision history for this message
Allan LeSage (allanlesage) wrote :

Apologies; I filed this bug in disguise.

Revision history for this message
Francis Ginther (fginther) wrote :

Also see this error signature when building lp:dee on arm with qemu.

Revision history for this message
Allan LeSage (allanlesage) wrote :

Having run a few test builds today, this no longer happens for indicator-session, marking 'incomplete' for that project.

Changed in indicator-session:
status: New → Incomplete
Revision history for this message
Alberto Mardegan (mardy) wrote :
Revision history for this message
Alberto Mardegan (mardy) wrote :

If my investigation is correct, the syscall 366 is accept4(). This will be fixed with qemu 1.3, and a patch is already available here:
https://bugzilla.redhat.com/show_bug.cgi?id=855162

Ted Gould (ted) on 2013-10-14
Changed in indicator-session:
status: Incomplete → Invalid
Changed in indicator-sync:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.