Closed Bug 1082528 Opened 11 years ago Closed 11 years ago

[ku] Test failure "Expected window state has been reached - open" in testOpenClosePBKeyboardShortcut.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Version 2
x86
All
defect
Not set
normal

Tracking

(firefox34 affected)

RESOLVED DUPLICATE of bug 956661
Tracking Status
firefox34 --- affected

People

(Reporter: AndreeaMatei, Unassigned)

References

()

Details

(Whiteboard: [mozmill-test-failure])

This started to fail today with Beta 34.0 ku (I think we added this locale by mistake in the batches, cause it's listed in my blacklist patch which is on staging only now). Not sure if that locale is maintained anymore, I remember it wasn't last time we had issues with it.
Whiteboard: [mozmill-test-failure]
Looks pretty clear a locale shortcut conflict for ku Francesco, could you please confirm if ku is no longer maintained? We did have this discussion some time ago (maybe 1 year?), I'm wondering if there's any update on the ku locale. If this is still unmaintained, we'll keep this locale out of the ones we test. If there's someone maintaining it we'd be happy to include it in our regular tests.
Flags: needinfo?(francesco.lodolo)
Summary: Test failure "Expected window state has been reached - open" in testOpenClosePBKeyboardShortcut.js → [ku] Test failure "Expected window state has been reached - open" in testOpenClosePBKeyboardShortcut.js
Last changes are from 6 months ago, so it's pretty much unmaintained http://hg.mozilla.org/releases/l10n/mozilla-aurora/ku/shortlog I think it should be safe to ignore this locale, but I'm forwarding the NI to Jeff to make sure he agrees on this.
Flags: needinfo?(francesco.lodolo) → needinfo?(jbeatty)
Agreed, we haven't seen or heard from the Kurdish team in quite a while and are trying to determine where to go with the Kurdish locale. Safe to ignore.
Flags: needinfo?(jbeatty)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.