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 711519 - jsunit tests fail on powerpc
jsunit tests fail on powerpc
Status: RESOLVED FIXED
Product: gjs
Classification: Bindings
Component: general
1.38.x
Other Linux
: Normal normal
: ---
Assigned To: gjs-maint
gjs-maint
Depends on:
Blocks:
 
 
Reported: 2013-11-05 22:10 UTC by darkxst
Modified: 2014-09-29 22:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description darkxst 2013-11-05 22:10:59 UTC 
gjs 1.38.1 with mozjs17 fails to pass any of the jsunit tests on powerpc. The following log is the only info I have (I don't have access to a powerpc machine myself). 

laney@partch> GJS_USE_UNINSTALLED_FILES=1 ./jsunit -verbose --debug-log                                                         ~/gjs-1.38.1
{*LOG(binary):{/home/laney/gjs-1.38.1/.libs/lt-jsunit}:{R02Se50cf2d09c4e571f341b39bd0a1e9067}:LOG*}
{*LOG(start):{/js/0010basic}:LOG*}
/js/0010basic:    JS NATIVE: Registered native JS module 'byteArray'
   JS NATIVE: Registered native JS module '_gi'
   JS NATIVE: Registered native JS module 'gi'
   JS NATIVE: Registered native JS module 'cairoNative'
   JS NATIVE: Registered native JS module 'system'
   JS NATIVE: Registered native JS module 'console'
      JS CTX: Changing JavaScript version to 1.8 from default
   JS IMPORT: Initialized class GjsFileImporter prototype 0xf5f0a220
   JS IMPORT: Defining parent (nil) of 0xf5f0a240 'imports' is mod 0
      JS CTX: Script evaluation failed
      JS CTX: Script evaluation succeeded
{*LOG(error):{Gjs-FATAL-ERROR: JS_EvaluateScript() failed}:LOG*}

(/home/laney/gjs-1.38.1/.libs/lt-jsunit:9016): Gjs-ERROR **: JS_EvaluateScript() failed
Comment 1 Colin Walters 2013-11-08 14:09:03 UTC 
Hmmm...going to need more info than this.

Does the core "js" shell from mozjs17 work for you on ppc?
Comment 2 darkxst 2013-11-10 22:21:03 UTC 
Laney, can you check ^ that?
Comment 3 Iain Lane 2013-11-12 09:51:16 UTC 
Ok, basic stuff seems to work:

laney@partch> js17
js> print ("Hello world")
Hello world
js> 1330+7
1337
js> function foo(x) { return x * 5; }
js> foo(10)
50
Comment 4 Iain Lane 2013-11-12 09:55:56 UTC 
How can I run gjs-console manually on one of the test files?

I added some debugging print statements and tried:

laney@partch> ./gjs-console -I /home/laney/gjs-1.38.1/modules test0010basic.js
0
JS_EvaluateScript() failed

The "0" comes from one of those; relevant snippet:

,----
| print("0");
| const JSUnit = imports.jsUnit;
| print("1");
`----

So something goes wrong at "imports". Is that a problem with something I've done?
Comment 5 Michel Dänzer 2014-05-05 09:07:57 UTC 
If this is still an issue with 1.40.y, maybe try the patch from bug 729554.
Comment 6 Bastien Nocera 2014-09-29 18:02:56 UTC 
(In reply to comment #5)
> If this is still an issue with 1.40.y, maybe try the patch from bug 729554.

Which are all (including fixup) in 1.42.
Comment 7 darkxst 2014-09-29 22:32:32 UTC 
can confirm that all tests pass on our powerpc builders with 1.42