Closed
Bug 1001166
Opened 10 years ago
Closed 10 years ago
Intermittent failing test, creating an event opening event in read view should not overflow title, location, or description
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 974731
2.0 S3 (6june)
People
(Reporter: kgrandon, Assigned: mmedeiros)
References
Details
Error: title: invalid content width at Object.Calendar.checkOverflow (/home/travis/build/mozilla-b2g/gaia/apps/calendar/test/marionette/lib/calendar.js:236:13) at Context.<anonymous> (/home/travis/build/mozilla-b2g/gaia/apps/calendar/test/marionette/create_event_test.js:68:11) at Test.Runnable.run (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runnable.js:211:32) at Runner.runTest (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:372:10) at /home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:448:12 at next (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:297:14) at /home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:307:7 at next (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:245:23) at /home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:269:7 at Hook.Runnable.run (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runnable.js:213:5) at next (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:257:10) at Object._onImmediate (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:274:5) at processImmediate [as _immediateCallback] (timers.js:330:15)
Reporter | ||
Comment 1•10 years ago
|
||
Disabled for too many failures: https://github.com/mozilla-b2g/gaia/commit/379261c195c77fd59e2d2188f38541f979225461
Keywords: leave-open
Assignee | ||
Comment 2•10 years ago
|
||
since I'm working on Bug 974731 I'll also go ahead and fix this. - fix ALL the marionette bugs!!!
Assignee: nobody → mmedeiros
Target Milestone: --- → 2.0 S3 (6june)
Assignee | ||
Comment 3•10 years ago
|
||
marking as a duplicate of Bug 974731 since it also fixed this. (easier to review a single patch and logic was basically the same)
You need to log in
before you can comment on or make changes to this bug.
Description
•