Bug#877428: mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300

2017-10-20 Thread Michael Biebl
Looking at the latest build log, the failures are down to one: > ## ecma_6/Array/for_of_1.js: rc = 3, run time = 0.345637 > ecma_6/Array/for_of_1.js:100:5 Error: Assertion failed: got 150, expected 300 > Stack: > TestChangeArrayPrototype@ecma_6/Array/for_of_1.js:100:5 >

Bug#877428: mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300

2017-10-12 Thread Simon McVittie
On Thu, 12 Oct 2017 at 01:37:51 +0100, Simon McVittie wrote: > On mips64el there are a couple of timeouts (knowing mips*, probably > an arbitrary timeout is just too short): > > TEST-UNEXPECTED-FAIL | js1_5/Array/regress-157652.js | (args: "") | (TIMEOUT) > TEST-UNEXPECTED-FAIL |

Bug#877428: mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300

2017-10-11 Thread Simon McVittie
Control: retitle 877428 mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300 [Re-sending to the correct clone, sorry for the noise] On Sun, 01 Oct 2017 at 19:03:46 +0100, Simon McVittie wrote: > On Sat, 23 Sep 2017 at