Closed Bug 618233 Opened 14 years ago Closed 12 years ago

intermittent TEST-UNEXPECTED-FAIL | test_jpakeclient.js | Shouldn't have aborted!jpake.error.wrongmessage

Categories

(Firefox :: Sync, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
blocking2.0 --- -

People

(Reporter: dbaron, Unassigned)

References

Details

(Keywords: intermittent-failure)

Since the JPAKE tests landed earlier today they've been intermittently failing on Windows. (Logs to be linked in next comment.)
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1291956764.1291961095.14460.gz Rev3 WINNT 6.1 mozilla-central opt test xpcshell (and that was on the changeset in which the tests landed) http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1291955225.1291960652.12211.gz Rev3 WINNT 6.1 mozilla-central debug test xpcshell
This test failure happened on landing a beta8 / fennec-b3 bug. Is this something that needs to be fixed before we ship?
blocking2.0: --- → ?
tracking-fennec: --- → ?
(In reply to comment #3) > Is this something that needs to be fixed before we ship? At this point it looks like it's a random orange (albeit with a high rate). Will disable for now until I can look into it tomorrow on my Windows box.
(In reply to comment #13) > dtownsend%oxymoronical.com > http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1292009391.1292010122.30038.gz > Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test xpcshell on 2010/12/10 > 11:29:51 > > s: talos-r3-snow-034 > TEST-UNEXPECTED-FAIL | > /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/services/sync/tests/unit/test_jpakeclient.js > | test failed (with xpcshell return code: 0), see following log: > TEST-UNEXPECTED-FAIL | > /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/services/sync/tests/unit/test_jpakeclient.js > | > {"type":"receiver1","payload":{"gx1":"25E1DF67C850F2C1591C24BEDFA4326943E9F71D46E33A3C4C2D14B1A11E41BDEB81208DE0D527621570D1080F6F8ADD052641C2989629305AC2D983B2EB194CE67C15B0CA0C4E0AB8D62E6BDFB9525D23E42670CBA1D62E73B75BBFBEAE166228E84A3297B45F1706071D58139F908CDE16730C98857F00CEDF2D34CAB58AACEB09D0BE4C0C550E5B86F07F17EC94C704DCDBC385F64F8AC269E601BBE83EBE889BDA04D9E66EA5AD2709EC0A9CA9DFC6CDA1202B8C76433582D47E08E7052040FBCC58F80DBEF83CB6BAFE6FD3B0C80E7E4759F84E96D5BBF00B3B05DFB7B7CD6EBAC3D89E9A86BCED5E6FC9BF3367A8B5D3E530260F8DD69F289DC8FBDC5ED3A197D846A76FB512C0FAC8846E9341605DD4915C87E35A1533CEFE91CC284E4A011C1454DECD03FC146DC9A5A95204C81784A7129BB4BF95770E0DA72ECEFE9AA6638AA20F8D9EF6ECDE45D8759290C445C5BB67AEFAC16E56E4C6CDFE124A76ACFAE88141DBE2143E9A4C6AC456AA7BE1F4376190C6C3386E2F5A524B8E66","gx2":"841E93C44F26F72E08233CAB44FB1645B0F010FE20EE8638E0CC5543F37E62571FDBB4FCFDC573DAE4F38C66678670826F3829AD068541631B7D83F85F19FB483BD49FC759CEEEBE6DDEF09C90B9E0F5F4B86D2462E5EA25097BFBCDD7D2B92EF216640BBDE640A24FC0CA7DA402892472FC187DD93D70E1BED776F4198D38D95037C64E6C02B0EE01B756FF6D095EE144591BB2805921450876ADFC490DCA1AF9D5752D9844AD8B0BFC14C73B0E76DF94E959C0F47F915A0F87C3616388B9B615FA181FD7DDABDC29AFF436EE7F1C01CF919D0794F9B6522E12333654EA9754E33FF3DD32F87E48E1845A0A3353927ED89ED222F22D2101830F68EDAB66079F378ED0FAAD4A56E0F216FAB38F09A3463E41AA8ED6E912A03E4CA038459E053A29AFC0FAA1D522C9C9F079F0D5C8E8C2A2A3C13645CAD28040A3470C715321703C4CAD672024A91D305A030BAEF7D239E3ED7A2F734DE3E7F223CBA7EBCA4C7B187BB57D2B95C798BE037214296CEE90F82A6044FE28D0D6A03E89685304EF55","zkp_x1":{"gr":"44951F703A3D912E67B31CCCF3175974EB4386BD0EA0440D1710EAEEF1CA0D7AE2EFEEEA86EF6A622071BEF9531B182F7ADA985C30E8078B48FC000BB68E256B5B64E489CB231FE7CC098BA91C3AE341122C6F245D5EF4CEC0758709109E09A6E5AFFD7F41AD155EC0514C82D34AD91C428795C3318E26D4C45FF18C30E6E970B074AA02E6297FCA7E8AA30C7F060EAA488A3980874FAF6F5FBD8318D6DB7F87AD229F86D2432088134A3CC13FB0221C9A69040508F667F74DF0972CA3430F6C26C06E8BAC89CAA5CB02509C792FCF9BB3C76FAF2D33FDBA6E4461A4FECBC90A788CB99716267AFE20FE07AB84DB9915CC7C56D8B158D4165CFFFA2D1C8D884F8B52F2A15EB11FCEDADFC31EE1927EE20E0F0369DE28029164D425250F31B0CD2FDE6F967D431DE385E4E4A8FF703434E672CAD2A31FF590250D166A0C3780DD6C44B9B2A785446D5B86FEAC268CA5529525DEAD964BF1A55840B58A5C13C0A54717E56069E77B7F7E39CFBD215E9F327A345E2483958E64B6B74F3B7AE0884A","b":"6C0B481DFF8CFCCD6D663FB9A5173D39D4E93505CF19145F9C05494AAE4DBBE7","id":"receiver"},"zkp_x2":{"gr":"4F75E90467DBFCCEA8F90ACEF5D02D0C9D1C871A86D03904C4142096B812B6D59DC5B58FBAC2C16FD40D72189A4051FDB5C68A2DF806110740BB1A6A5EC09CAAE4196DEFA29A888C7A4D0CFA6A5857735CA4CF41523DB6F8EF1C6DF8F5B8686DA6BE5863C796E3B7B4403C8A1D859189ED440FFCE4C16CFD520BFBE0319D3DC69CADC5161C81EEE3AFE82A1152EA0656BCD5D4EACDC4AF21F15CCE728489B43D7F79CA82E50297BF45A44DCDB315274934D507355D417B97DE02971FEA9AE4770FD2E2E68CBB2808CA866D6443D9B19F7CFD5F0A64556474CD385DD5DD1F208DD16850AE927A3C9305374A5F851418876CF2BC3E13497CE0F42BE31C80BFA3AF40A11A1D03818E11847AC90C173710057CC68316303D9B8BBA6B5A3EAF1460B723CE18498E9014490C709C1FF61B36A54875B98941F9D35132B5201B5D44869E44562E828D315FC6AFCEEB83E4A25FF7DC6487754AC715574B84D095C8F0ADE6688DC8B2BDCC2BAF3FA070933BB1E7D83D0CF4182402BEA13E60BCF83CBB8832","b":"52CD77924879A2D41F4EA785B2C44E4DA0E31D10CFB456A9DB60AF9D105FF1CB","id":"receiver"}}} > == undefined - See following stack: I filed bug 618400 for this as it seems a little different
Yes, this bug is about about Windows. The failure in comment 13 is on OSX.
blocking2.0: ? → beta9+
tracking-fennec: ? → 2.0b4+
not blocking fennec.
tracking-fennec: 2.0b4+ → ---
blocking2.0: beta9+ → betaN+
We disabled the test on m-c. JPAKE is definitely working on Windows, so the test is probably doing something wrong. We should looking into it, but it doesn't feel like a blocker to me at this point. Renominating for blocking, suggesting minus.
blocking2.0: betaN+ → ?
(In reply to comment #17) > We disabled the test on m-c. JPAKE is definitely working on Windows, so the > test is probably doing something wrong. We should looking into it, but it > doesn't feel like a blocker to me at this point. Renominating for blocking, > suggesting minus. Do we have any regular test coverage of JPAKE on windows right now (automated or otherwise)? I'd be wary of shipping when we have no way to verify if future changes break anything.
(In reply to comment #18) > Do we have any regular test coverage of JPAKE on windows right now (automated > or otherwise)? I'd be wary of shipping when we have no way to verify if future > changes break anything. We don't. I feel the same way. But I don't think we absolutely cannot ship Firefox 4 without this test being enabled. Other people may disagree, which is why I renominated and not removed blocking. If this gets blocking status again, I think should be a [softblocker]. Btw, test passes locally on my Win7 dev box so for now I have no way of reproducing what tinderboxes are seeing.
Tony, can we add a litmus test for J-PAKE on Windows for the time being?
Flags: in-litmus?
Flags: in-litmus? → in-litmus?(twalker)
This makes me sad, but I agree with the logic.
blocking2.0: ? → -
Whiteboard: [orange] → [orange][softblocker]
Whiteboard: [orange][softblocker] → [orange]
We have J-pake test in-litmus
Flags: in-litmus?(twalker) → in-litmus+
I am going to re-enable this test on Windows to try to tease out some failures for triage.
Re-disabled in s-c.
Whiteboard: [orange]
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of: {random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open} There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Component: Firefox Sync: Crypto → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.