51787 2010-12-31 14:04:10 -0800 [Windows 7 Release Tests] media/video-element-other-namespace-crash.html failing since introduction in r74787 2023-10-13 08:33:15 -0700 1 1 1 Unclassified WebKit Media 528+ (Nightly build) All Windows 7 RESOLVED CONFIGURATION CHANGED InRadar, LayoutTestFailure, PlatformOnly P2 Normal --- 1 jberlin webkit-unassigned abarth ahmad.saleem792 eric inferno jberlin webkit.review.bot oldest_to_newest 328218 0 jberlin 2010-12-31 14:04:10 -0800 The test introduced in http://trac.webkit.org/changeset/74787 appears to be timing out on the Windows 7 Release Test bot: http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r74833%20(7845)/media/video-element-other-namespace-crash-pretty-diff.html Chromium apparently was having similar issues due to not having the necessary codecs: http://trac.webkit.org/changeset/74790 http://trac.webkit.org/changeset/74819 I will be landing the failing expected results soon in order to get the Windows 7 Release Test bot green. 328221 1 jberlin 2010-12-31 14:12:38 -0800 Landed the failing results in http://trac.webkit.org/changeset/74837 328231 2 jberlin 2010-12-31 16:50:22 -0800 Darin pointed out the correct temporary fix was to add the test to the skipped list in the case where the test consistenly times out. Added to the skip list in http://trac.webkit.org/changeset/74840 328234 3 webkit.review.bot 2010-12-31 17:40:05 -0800 http://trac.webkit.org/changeset/74840 might have broken Leopard Intel Debug (Tests) 328240 4 jberlin 2010-12-31 18:35:59 -0800 (In reply to comment #3) > http://trac.webkit.org/changeset/74840 might have broken Leopard Intel Debug (Tests) I highly doubt that, seeing as that patch only affected Windows. However, I don't see what could have caused that test to fail. Maybe it is just flakey? 328243 5 abarth 2010-12-31 18:44:13 -0800 There's some serious flakiness on the bot right now. :( 339173 6 jberlin 2011-01-24 12:16:36 -0800 <rdar://problem/8908389> 1984899 7 ahmad.saleem792 2023-10-13 08:33:15 -0700 video-element-other-namespace-crash <- It is only skipped in Mac-wk1 port but have reference to newer bug. AppleWin port is gone and we only have this tracked on one platform with newer bug. I don't think much here to do. Marking this as 'RESOLVED CONFIGURATION CHANGED'.