Closed Bug 1910494 Opened 6 months ago Closed 6 months ago

TEST-UNEXPECTED-FAIL | test262/intl402/Temporal/PlainDate/prototype/with/cross-era-boundary.js

Categories

(Core :: JavaScript: Internationalization API, defect)

defect

Tracking

()

RESOLVED FIXED
130 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- fixed
firefox128 --- wontfix
firefox129 --- fixed
firefox130 --- fixed

People

(Reporter: glandium, Assigned: glandium)

References

Details

Attachments

(3 files)

When upgrading to rustc 1.80:

[task 2024-07-29T21:00:28.270Z] ## test262/intl402/Temporal/PlainDate/prototype/with/cross-era-boundary.js: rc = 3, run time = 0.045518
[task 2024-07-29T21:00:28.270Z] /builds/worker/checkouts/gecko/js/src/tests/test262/intl402/Temporal/PlainDate/prototype/with/cross-era-boundary.js:14:26 Error: internal error while computing calendar data
[task 2024-07-29T21:00:28.270Z] Stack:
[task 2024-07-29T21:00:28.270Z]   @/builds/worker/checkouts/gecko/js/src/tests/test262/intl402/Temporal/PlainDate/prototype/with/cross-era-boundary.js:14:26
[task 2024-07-29T21:00:28.270Z] TEST-UNEXPECTED-FAIL | test262/intl402/Temporal/PlainDate/prototype/with/cross-era-boundary.js | (args: "--dll /builds/worker/fetches/injector/libbreakpadinjector.so") [0.0 s]

This is caused by https://github.com/unicode-org/icu4x/issues/5039

Is the segmenter exposed to content on 128?

Flags: needinfo?(m_kato)
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/9e13a477e3cb Upgrade zerovec to 0.10.4. r=supply-chain-reviewers

(In reply to Mike Hommey [:glandium] from comment #2)

Is the segmenter exposed to content on 128?

Intl.Segmenter is already shipped, but this error seems to be Temporal.

anba, Temporal isn't shipped on stable yet, right?

Flags: needinfo?(m_kato) → needinfo?(andrebargull)
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch

(In reply to Makoto Kato [:m_kato] from comment #4)

(In reply to Mike Hommey [:glandium] from comment #2)

Is the segmenter exposed to content on 128?

Intl.Segmenter is already shipped, but this error seems to be Temporal.

The Segmenter seems to be using zerovec, though. We're not seeing problems in tests, but I can't guarantee it actually doesn't do bad things.

(In reply to Makoto Kato [:m_kato] from comment #4)

anba, Temporal isn't shipped on stable yet, right?

Correct. Temporal requires the configure flag --with-temporal-api to be set, which isn't yet enabled by default.

Flags: needinfo?(andrebargull)

The patch landed in nightly and beta is affected.
:glandium, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox129 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(mh+mozilla)

(In reply to Mike Hommey [:glandium] from comment #6)

The Segmenter seems to be using zerovec, though. We're not seeing problems in tests, but I can't guarantee it actually doesn't do bad things.

zerovec is used on ICU4X data marker, so it doesn't depends on segmenter only. Currently, I guess that we already use ICU4X for bidi, normalization of URL and etc

Ok, so this would need to be uplifted to ESR too... except ESR doesn't have bug 1899411, which updated zerovec from 0.10.1 to 0.10.2

Flags: needinfo?(mh+mozilla)
Attachment #9416878 - Flags: approval-mozilla-beta?

beta Uplift Approval Request

  • User impact if declined: Undefined behavior when some ICU4X data is used
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: N/A
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Straightforward addition of an attribute to a few structs
  • String changes made/needed: N/A
  • Is Android affected?: yes
Attachment #9416879 - Flags: approval-mozilla-esr128?
Attachment #9416878 - Flags: approval-mozilla-release?

esr128 Uplift Approval Request

  • User impact if declined: Undefined behavior when some ICU4X data is used
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: N/A
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Straightforward addition of an attribute to a few structs
  • String changes made/needed: N/A
  • Is Android affected?: yes
Attachment #9416878 - Flags: approval-mozilla-beta?
Attachment #9416878 - Flags: approval-mozilla-release? → approval-mozilla-release+
Attachment #9416879 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: