RESOLVED FIXED Bug 63268
http/tests/multipart/win-boundary-crash.html flakey
https://bugs.webkit.org/show_bug.cgi?id=63268
Summary http/tests/multipart/win-boundary-crash.html flakey
Attachments
Jessie Berlin
Comment 1 2011-06-23 11:43:54 PDT
Added to the Windows skipped list in http://trac.webkit.org/changeset/89596
Adam Roben (:aroben)
Comment 3 2011-06-23 12:32:47 PDT
(In reply to comment #2) > I will move the entry to the mac Skipped list. Seems like you need it to be on both mac/Skipped and win/Skipped. (Windows WebKit1 doesn't use mac/Skipped.) Or maybe we should disable the test by renaming it.
Jessie Berlin
Comment 4 2011-06-23 12:35:14 PDT
(In reply to comment #3) > (In reply to comment #2) > > I will move the entry to the mac Skipped list. > > Seems like you need it to be on both mac/Skipped and win/Skipped. (Windows WebKit1 doesn't use mac/Skipped.) > > Or maybe we should disable the test by renaming it. I thought the win skipped list always inherited from the mac skipped list. Moved to the mac skipped list in http://trac.webkit.org/changeset/89600.
Jessie Berlin
Comment 5 2011-06-23 12:52:35 PDT
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > I will move the entry to the mac Skipped list. > > > > Seems like you need it to be on both mac/Skipped and win/Skipped. (Windows WebKit1 doesn't use mac/Skipped.) > > > > Or maybe we should disable the test by renaming it. > > I thought the win skipped list always inherited from the mac skipped list. > > Moved to the mac skipped list in http://trac.webkit.org/changeset/89600. Adam showed me that it was not, so I went ahead and just disabled the test in http://trac.webkit.org/changeset/89602
Tony Chang
Comment 6 2011-06-23 16:10:11 PDT
This is super weird. Here's the test html: http://trac.webkit.org/browser/trunk/LayoutTests/http/tests/multipart/win-boundary-crash.html-disabled 1 <html> 2 <head> 3 <script> 4 if (window.layoutTestController) 5 layoutTestController.dumpAsText(); 6 </script> 7 </head> 8 <body> 9 <p>Test for <i><a href="http://bugs.webkit.org/show_bug.cgi?id=14516">http://bugs.webkit.org/show_bug.cgi?id=14516</a> 10 crash loading multipart/x-mixed-replace data on windows safari</i></p> 11 <p>If WebKit does not crash when loading this img, then it passed.</p> 12 <img src="resources/multipart-nodashes.php" /> 13 </body> 14 </html> The diff shows that dumpAsText() didn't get called, but I don't see how that's possible. cc'ing abarth since this sounds similar to https://bugs.webkit.org/show_bug.cgi?id=63057 .
Adam Roben (:aroben)
Comment 7 2011-06-24 09:00:09 PDT
(In reply to comment #6) > The diff shows that dumpAsText() didn't get called, but I don't see how that's possible. No, the diff shows that the some other test got dumped instead. Look more closely and you'll see that the text is entirely different.
Tony Chang
Comment 8 2011-06-24 10:23:31 PDT
(In reply to comment #7) > (In reply to comment #6) > > The diff shows that dumpAsText() didn't get called, but I don't see how that's possible. > > No, the diff shows that the some other test got dumped instead. Look more closely and you'll see that the text is entirely different. Ah, sorry, you're right, it's the output from the previous test (stop-crash.html). This could be a problem with ORWT or maybe one of the previous tests has an http connection that's hanging or something.
Fujii Hironori
Comment 9 2023-10-23 16:53:56 PDT
EWS
Comment 10 2023-10-24 00:24:09 PDT
Test gardening commit 269704@main (237bd74e5ced): <https://commits.webkit.org/269704@main> Reviewed commits have been landed. Closing PR #19461 and removing active labels.
Fujii Hironori
Comment 11 2023-10-24 18:56:53 PDT
No flaky after 269704@main. https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fmultipart%2Fwin-boundary-crash.html Filed a new ticket for the GTK and WPE crashes. Bug 263629 – [GTK][WPE] http/tests/multipart/win-boundary-crash.html is crashing: soup_multipart_input_stream_read_headers: assertion 'got_lf' failed
Radar WebKit Bug Importer
Comment 12 2023-10-24 18:57:15 PDT
Note You need to log in before you can comment on or make changes to this bug.