The failures on the try run are due to the event and task tabs not closing at the end of the test. When running this single test locally they close just fine. Running more than just the single test locally and a dialog appears asking if you want to save the event (and task) before closing it. So that must be what's happening on the try run. It's strange because usually if you don't modify the event or task (and we don't in the test) then the tab just closes and you don't get that save dialog. (I even tried using the same tabmail.closeTab() method that we use in the test in the console, and the tab closed with no dialog.) Probably related to the mysterious save prompt appearances mentioned in bug 1590682. I tried adding the savePromptObserver code from that bug to comm/calendar/test/browser/head.js so it would work for this test. Then when I ran the whole set of calendar tests, things froze just before the task and event tabs were closed, but no save prompt appeared. Then when I killed the test in the terminal the log showed: FAIL Unexpected save prompt appeared - JS frame :: chrome://mochitests/content/browser/comm/calendar/test/browser/head.js So looks like this test won't pass reliably until we figure out these mysterious save prompt appearances.
Bug 1297426 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The failures on the try run are due to the event and task tabs not closing at the end of the test. When running this single test locally they close just fine. When running more than just the single test locally a dialog appears asking if you want to save the event (and task) before closing it. So that must be what's happening on the try run. It's strange because usually if you don't modify the event or task (and we don't in the test) then the tab just closes and you don't get that save dialog. (I even tried using the same tabmail.closeTab() method that we use in the test in the console, and the tab closed with no dialog.) Probably related to the mysterious save prompt appearances mentioned in bug 1590682. I tried adding the savePromptObserver code from that bug to comm/calendar/test/browser/head.js so it would work for this test. Then when I ran the whole set of calendar tests, things froze just before the task and event tabs were closed, but no save prompt appeared. Then when I killed the test in the terminal the log showed: FAIL Unexpected save prompt appeared - JS frame :: chrome://mochitests/content/browser/comm/calendar/test/browser/head.js So looks like this test won't pass reliably until we figure out these mysterious save prompt appearances.