Bug#1086298: mozjs128: FTBFS: js/src/tests/non262/Date/parse-dashed-numeric-date.js fails to parse a post-Y10K date

[Santiago Vila]

El 29/10/24 a las 20:10, Simon McVittie escribió:
> The only non-ignored test failure I can see in the full log
> https://people.debian.org/~sanvila/build-logs/202410/mozjs128_128.3.0-1_amd64-20241028T163547.508Z
> is this one:
> 
> ## non262/Date/parse-dashed-numeric-date.js: rc = 3, run time = 0.011593
> /<<PKGBUILDDIR>>/js/src/tests/non262/Date/parse-dashed-numeric-date.js:119:13 Error: Assertion failed: got 568962338400000, expected 568962313200000: "19999-09-12 22:00:00 GMT-0800" should be Sun Sep 12 19999 23:00:00 GMT+0000 (GMT) (got Mon Sep 13 19999 06:00:00 GMT+0000 (GMT)).
> Stack:
>    @/<<PKGBUILDDIR>>/js/src/tests/non262/Date/parse-dashed-numeric-date.js:119:13
>    inTimeZone@/<<PKGBUILDDIR>>/js/src/tests/non262/Date/shell.js:95:13
>    @/<<PKGBUILDDIR>>/js/src/tests/non262/Date/parse-dashed-numeric-date.js:7:11
> TEST-UNEXPECTED-FAIL | non262/Date/parse-dashed-numeric-date.js | (args: "") [0.0 s]
> 
> (Your guess is as good as mine...)

Thank you. I try to choose a good subject when I can. I do this
manually, so if you see "failing tests" it means it was not obvious.

In this case, the package built ok in the buildds several weeks ago
but it fails to build now, so I would bet it's something related to
the recent tzdata changes.

Thanks.