Closed Bug 836369 Opened 7 years ago Closed 6 years ago
_history _tracker .js | test failed | true == false
https://tbpl.mozilla.org/php/getParsedLog.php?id=19287308&tree=Mozilla-Inbound Rev3 Fedora 12x64 mozilla-inbound opt test xpcshell on 2013-01-30 08:24:52 PST for push 7faec6303aa9 slave: talos-r3-fed64-019 TEST-UNEXPECTED-FAIL | /home/cltbld/talos-slave/test/build/xpcshell/tests/services/sync/tests/unit/test_history_tracker.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | /home/cltbld/talos-slave/test/build/xpcshell/tests/services/sync/tests/unit/test_history_tracker.js | true == false - See following stack:
CC mak: async visit change fallout? (on phone, apologies for brevity)
yes, it's possible and plausible, probably checking at the wrong time :(
Is this test using tps history.jsm? cause look like there we may have to wait habdleCompletion rather than handleResult. The change to test_history_tracker.js looks correct afaict...
Need to respond to Comment 4 after this phone call.
(In reply to Marco Bonardo [:mak] from comment #4) > Is this test using tps history.jsm? Nope, it's a standalone xpcshell test. > The change to test_history_tracker.js looks correct afaict... Yeah, this looks like some kind of tracker bug. Weird. Will investigate.
There are two oddities here: * There's a situation in which we might call run-next-test twice, but not in a way that should do any harm. * The tracker isn't supposed to be enabled at the point where the errant data is recorded, so I've added an explicit test for that. If that fails sooner, then something else is wrong.
Assignee: nobody → rnewman
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla21
Looks like this was fixed.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.