mozjs91 ftbfs in the jammy release pocket

Bug #1976260 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mozjs91 (Ubuntu)
Fix Released
High
Jeremy Bícha
Jammy
Fix Released
High
Unassigned

Bug Description

as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away):

https://launchpadlibrarian.net/604217092/buildlog_ubuntu-jammy-amd64.mozjs91_91.7.0-2_BUILDING.txt.gz

[...]
## non262/Intl/DateTimeFormat/timeZone_version.js: rc = 3, run time = 0.014026
/<<PKGBUILDDIR>>/js/src/tests/non262/Intl/DateTimeFormat/timeZone_version.js:16:9 Error: Asserti
on failed: got "2022a", expected "2021a3"
Stack:
  @/<<PKGBUILDDIR>>/js/src/tests/non262/Intl/DateTimeFormat/timeZone_version.js:16:9
TEST-UNEXPECTED-FAIL | non262/Intl/DateTimeFormat/timeZone_version.js | (args: "") [0.0 s]
make[3]: *** [Makefile:63: check-jstests] Error 1

Tags: ftbfs dt-375

CVE References

Matthias Klose (doko)
tags: added: ftbfs rls-jj-incoming
Changed in mozjs91 (Ubuntu):
importance: Undecided → High
status: New → Triaged
assignee: nobody → Jeremy Bicha (jbicha)
tags: removed: rls-jj-incoming
Changed in mozjs91 (Ubuntu Jammy):
importance: Undecided → High
status: New → Triaged
tags: added: dt-375
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mozjs91 - 91.10.0-0ubuntu1

---------------
mozjs91 (91.10.0-0ubuntu1) jammy-security; urgency=medium

  [ Jeremy Bicha ]
  * SECURITY UPDATE: Multiple issues (LP: #1978961)
    - CVE-2022-28285: Incorrect AliasSet used in JIT Codegen
    - CVE-2022-31740: Register allocation problem in WASM on arm64
  * Drop Bug-1687417-MIPS32 patch: applied in new release

  [ Simon McVittie ]
  * Add a patch to fix test failure with vendored ICU (LP: #1976260)

 -- Jeremy Bicha <email address hidden> Thu, 16 Jun 2022 10:11:50 -0400

Changed in mozjs91 (Ubuntu Jammy):
status: Triaged → Fix Released
Jeremy Bícha (jbicha)
Changed in mozjs91 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.