After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757328 - test-suite fails on various architectures in testCallbackTransferFull
test-suite fails on various architectures in testCallbackTransferFull
Status: RESOLVED OBSOLETE
Product: gjs
Classification: Bindings
Component: general
1.44.x
Other Linux
: Normal normal
: ---
Assigned To: gjs-maint
gjs-maint
Depends on:
Blocks:
 
 
Reported: 2015-10-29 22:02 UTC by Michael Biebl
Modified: 2018-01-27 11:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace of test failure (5.23 KB, text/plain)
2015-11-06 06:43 UTC, darkxst
Details

Description Michael Biebl 2015-10-29 22:02:28 UTC
Version: 1.44.0

The test-suite for 1.44.0 fails on various architectures, like powerpc, mips and mipsel. The full build logs can be seen at https://buildd.debian.org/status/package.php?p=gjs

The test-suite fails running testCallbackTransferFull() which was added in commit
4663c59264c36251b9be107594699db91df314ac.

Reverting that commit makes the test-suite pass again.
Comment 1 Cosimo Cecchi 2015-10-30 00:01:09 UTC
Is there any way to access the buildroot and read the test stderr.log file?
Comment 2 Michael Biebl 2015-10-30 00:07:00 UTC
I can attach the full logs if you want. But there doesn't seem to be anything useful in there regarding testCallbackTransferFull:

...
Gjs-Message: JS LOG: running test testCallbackTransferFull
Terminated
<EOF>

In dmesg I see
[1304439.840021] lt-jsunit[31353]: unhandled signal 11 at 7f454c50 nip 0f080e3c lr 0f080e00 code 30001
Comment 3 Cosimo Cecchi 2015-10-30 00:08:45 UTC
Since this is architecture-specific, I am not sure I can easily reproduce it over here. Could you perhaps try to run the test manually under gdb and get a backtrace?
Comment 4 Michael Biebl 2015-10-30 00:11:27 UTC
Hi Cosimo,

I do have access to porterboxes (unfortunately it's not so easy to grant that to external users), so I can try to get you further information if you help me do so.
You should be able to reproduce that within a qemu VM. The mips emulation is rather slow though.
Comment 5 Cosimo Cecchi 2015-10-30 00:16:41 UTC
If you have accesss to the box, and you can install debug information for at least gjs, mozjs, gobject-introspection and glib, you can try to run the test under gdb with this command from the gjs buildroot:

libtool --mode=execute gdb --args ./jsunit -p /js/EverythingBasic

I am not sure I will have time to set up the qemu mips VM myself very soon, so this would be helpful.
Thanks!
Comment 6 darkxst 2015-11-06 06:43:25 UTC
Created attachment 314957 [details]
backtrace of test failure
Comment 7 Michael Biebl 2015-11-18 06:13:58 UTC
@cosimo: is the backtrace provided by darkxst sufficient or do you need more information?
Comment 8 Cosimo Cecchi 2015-12-10 21:26:51 UTC
Michael: yeah, that looks sufficient. I will take a look at it when I have some time.
Comment 9 Mattia Rizzolo 2016-01-16 18:55:43 UTC
Hi cosimo: did you find time to look at this?
Comment 10 GNOME Infrastructure Team 2018-01-27 11:59:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gjs/issues/93.