143364 2015-04-03 02:26:48 -0700 [EFL] r182307 broke 87 layouttests 2017-03-11 10:40:43 -0800 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX https://bugs.webkit.org/show_bug.cgi?id=160117 P2 Normal --- 143360 1 ossy webkit-unassigned bdakin gyuyoung.kim mcatanzaro ossy thorton oldest_to_newest 1082490 0 ossy 2015-04-03 02:26:48 -0700 before: 65 failures https://build.webkit.org/builders/EFL%20Linux%2064-bit%20Release%20WK2/builds/20915 after: 152 failures https://build.webkit.org/builders/EFL%20Linux%2064-bit%20Release%20WK2/builds/20916 I have no idea if it is a regression or progression, just reported not to forget this bug. 1082491 1 ossy 2015-04-03 02:30:11 -0700 183 failures after one more build: https://build.webkit.org/builders/EFL%20Linux%2064-bit%20Release%20WK2/builds/20917 I don't think if 400 pixel width can be the expexted result. 1082492 2 thorton 2015-04-03 02:33:25 -0700 Hmm, the Mac bots seem fine, but the EFL bot seems to be getting into fixed layout mode and staying there? Hopefully someone from EFL can see what's up? 1082493 3 thorton 2015-04-03 02:34:54 -0700 If anything, I imagine that skipping the fixed-layout test would probably resolve this for now. 1082494 4 ossy 2015-04-03 02:38:08 -0700 Maybe it is related to bug137138 , EFL still has this very old flakey issue related to resizing. 1082496 5 ossy 2015-04-03 02:39:55 -0700 (In reply to comment #3) > If anything, I imagine that skipping the fixed-layout test would probably > resolve this for now. Good idea, let me check it. 1082500 6 ossy 2015-04-03 03:30:49 -0700 (In reply to comment #5) > (In reply to comment #3) > > If anything, I imagine that skipping the fixed-layout test would probably > > resolve this for now. > > Good idea, let me check it. Thanks, it helped, I skipped fixed-layout on EFL until we can fix this issue. ( http://trac.webkit.org/changeset/182311 ) 1286450 7 mcatanzaro 2017-03-11 10:40:43 -0800 Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.