Bug#873778: mozjs52: FTBFS on s390x and other big-endian machines

Simon McVittie smcv at debian.org
Thu Oct 12 00:31:08 UTC 2017


powerpc64 (pizzetti) gets the same test failures as s390x (zelenka),
suggesting that they are something that happens on big-endian 64-bit.
hppa doesn't seem to have a porterbox and sparc64's (notker) was
unresponsive, so I can't confirm that theory.

powerpc (partch) only gets one of those failures. I've left mozjs52
compiling on mips (minkus) overnight to see whether both big-endian
32-bit architectures behave the same.

On Thu, 12 Oct 2017 at 00:16:32 +0100, Simon McVittie wrote:
> ## ecma_6/TypedArray/sort_snans.js: rc = 3, run time = 0.055719
> ecma_6/shell.js:93:23 Error: Assertion failed: got -1.8938930325389462e+304, expected NaN at _[0]
> Stack:
>   assertSameValue at ecma_6/shell.js:93:23
>   check at ecma_6/shell.js:198:21
>   assertSameProps at ecma_6/shell.js:162:25
>   check at ecma_6/shell.js:213:25
>   assertDeepEq at ecma_6/shell.js:221:13
>   testFloat64NaNRanges at ecma_6/TypedArray/sort_snans.js:60:5
>   @ecma_6/TypedArray/sort_snans.js:68:1
> TEST-UNEXPECTED-FAIL | ecma_6/TypedArray/sort_snans.js | (args: "")

Also seen on powerpc (where it is the only failure) and on powerpc64

> ## ecma_6/TypedArray/Tconstructor-fromTypedArray-byteLength.js: rc = 3, run time = 0.025008
> ecma_6/TypedArray/Tconstructor-fromTypedArray-byteLength.js:8:9 Error: Assertion failed: got 3, expected 0
> Stack:
>   @ecma_6/TypedArray/Tconstructor-fromTypedArray-byteLength.js:8:9
> TEST-UNEXPECTED-FAIL | ecma_6/TypedArray/Tconstructor-fromTypedArray-byteLength.js | (args: "")

Also seen on powerpc64

> ## ecma_6/TypedArray/subarray.js: rc = 3, run time = 0.021673
> ecma_6/TypedArray/subarray.js:8:26 RangeError: attempting to construct out-of-bounds TypedArray on ArrayBuffer
> Stack:
>   @ecma_6/TypedArray/subarray.js:8:26
> TEST-UNEXPECTED-FAIL | ecma_6/TypedArray/subarray.js | (args: "")

Also seen on powerpc64

> ## ecma_6/TypedArray/indexOf-and-lastIndexOf.js: rc = 3, run time = 0.023659
> ecma_6/TypedArray/indexOf-and-lastIndexOf.js:53:9 Error: Assertion failed: got 0, expected 8
> Stack:
>   @ecma_6/TypedArray/indexOf-and-lastIndexOf.js:53:9
> TEST-UNEXPECTED-FAIL | ecma_6/TypedArray/indexOf-and-lastIndexOf.js | (args: "")

Also seen on powerpc64

> ## ecma_6/TypedArray/set-same-buffer-different-source-target-types.js: rc = 3, run time = 0.022477
> 896116: When setting a typed array from an overlapping typed array of different element type, copy the source elements into properly-sized temporary memory, and properly copy them into the target without overflow (of either source *or* target) when finished
> ecma_6/TypedArray/set-same-buffer-different-source-target-types.js:27:11 RangeError: attempting to construct out-of-bounds TypedArray on ArrayBuffer
> Stack:
>   @ecma_6/TypedArray/set-same-buffer-different-source-target-types.js:27:11
> TEST-UNEXPECTED-FAIL | ecma_6/TypedArray/set-same-buffer-different-source-target-types.js | (args: "")

Also seen on powerpc64

> ## ecma_6/ArrayBuffer/CloneArrayBuffer.js: rc = 3, run time = 0.021813
> 1264941: CloneArrayBuffer should be called with byteLength of source typedArray
> ecma_6/ArrayBuffer/CloneArrayBuffer.js:16:7 Error: Assertion failed: got 8, expected 0
> Stack:
>   test at ecma_6/ArrayBuffer/CloneArrayBuffer.js:16:7
>   @ecma_6/ArrayBuffer/CloneArrayBuffer.js:27:1
> TEST-UNEXPECTED-FAIL | ecma_6/ArrayBuffer/CloneArrayBuffer.js | (args: "")

Also seen on powerpc64

> ## js1_8_5/extensions/clone-errors.js: rc = -11, run time = 0.03348
>  PASSED! ok
> TEST-UNEXPECTED-FAIL | js1_8_5/extensions/clone-errors.js | (args: "")

Also seen on powerpc64

> ## js1_8_5/extensions/typedarray.js: rc = 0, run time = 0.167332
> BUGNUMBER: 532774
> STATUS: js typed arrays (webgl arrays)
> === FAILED ===
> check at js1_8_5/extensions/typedarray.js:62:22
> test at js1_8_5/extensions/typedarray.js:488:5
> @js1_8_5/extensions/typedarray.js:17:1
> 
> ==============
> === FAILED ===
> check at js1_8_5/extensions/typedarray.js:62:22
> test at js1_8_5/extensions/typedarray.js:489:5
> @js1_8_5/extensions/typedarray.js:17:1
> 
> ==============
> === FAILED ===
> check at js1_8_5/extensions/typedarray.js:62:22
> test at js1_8_5/extensions/typedarray.js:490:5
> @js1_8_5/extensions/typedarray.js:17:1
> 
> ==============
> === FAILED ===
> check at js1_8_5/extensions/typedarray.js:62:22
> test at js1_8_5/extensions/typedarray.js:491:5
> @js1_8_5/extensions/typedarray.js:17:1
> 
> ==============
> done
>  FAILED! [reported from test()] typed array tests : Expected value '0', Actual value '4'

Also seen on powerpc64

> ## js1_8_5/extensions/clone-transferables.js: rc = 3, run time = 0.022512
> js1_8_5/extensions/clone-transferables.js:42:17 Error: Assertion failed: got 0, expected NaN
> Stack:
>   test at js1_8_5/extensions/clone-transferables.js:42:17
>   @js1_8_5/extensions/clone-transferables.js:111:1
> TEST-UNEXPECTED-FAIL | js1_8_5/extensions/clone-transferables.js | (args: "")

Also seen on powerpc64

> ## js1_8_5/extensions/clone-many-transferables.js: rc = -11, run time = 0.783352
>  PASSED! ok
> TEST-UNEXPECTED-FAIL | js1_8_5/extensions/clone-many-transferables.js | (args: "")

Also seen on powerpc64



More information about the pkg-gnome-maintainers mailing list