Bug 30721

Summary: [GTK] DRT reports error in the wrong test
Product: WebKit Reporter: Alejandro G. Castro <alex>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, commit-queue, eric, jparent, ojan, xan.lopez, zecke
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
Proposed patch moving the flush to the end of the test
eric: review-
Added a function with the termination code none

Alejandro G. Castro
Reported 2009-10-23 11:27:45 PDT
DRT is closing the result output before doing the complete finalization of the test, basically the reset of the state before launching other tests is done after adding the EOF. In some situations this code is causing a crash and the crash is reported in the next test. We have to move the last flush after all the operations are finished. For instance this crash does not come from this test it comes from the opaque-base-url.html which was executed before: http://build.webkit.org/results/GTK Linux 64-bit Debug/r49969 (490)/fast/loader/plain-text-document-stderr.txt
Attachments
Proposed patch moving the flush to the end of the test (1.54 KB, patch)
2009-10-26 02:15 PDT, Alejandro G. Castro
eric: review-
Added a function with the termination code (1.80 KB, patch)
2009-11-20 10:35 PST, Alejandro G. Castro
no flags
Alejandro G. Castro
Comment 1 2009-10-23 11:29:57 PDT
(In reply to comment #0) > > [...] > > http://build.webkit.org/results/GTK Linux 64-bit Debug/r49969 > (490)/fast/loader/plain-text-document-stderr.txt Better link: http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r49969%20(490)/fast/loader/plain-text-document-stderr.txt
Alejandro G. Castro
Comment 2 2009-10-26 02:15:26 PDT
Created attachment 41855 [details] Proposed patch moving the flush to the end of the test
Holger Freyther
Comment 3 2009-10-26 06:32:09 PDT
Hmm. If dump() is not the right place to dump() maybe we call dump() at the wrong time?
Alejandro G. Castro
Comment 4 2009-10-26 07:04:15 PDT
(In reply to comment #3) > Hmm. If dump() is not the right place to dump() maybe we call dump() at the > wrong time? The problem is that after dump we do some "cleaning" of the webview state, and that cleaning is not part of the test but in some cases it causes a crash, currently it is happening if you check gtk+ debug bots; and because the EOF was already dumped the crash is reported in the next test. That code should not crash (actually I'm trying to check the problem in this case bug 30724) but if it crashes it must report the correct test. IMO this means that the test does not end until you stop using the webview, not after the last dump of the test. Maybe a cleaner option would be to add some support to the run tests script and the DRT to point out it is going to start checking the next test, currently it seems is just uses the results log.
Eric Seidel (no email)
Comment 5 2009-10-26 14:51:44 PDT
Comment on attachment 41855 [details] Proposed patch moving the flush to the end of the test Seems like this should be wrapped into a little helper function with a nice name. Leaving it bare as-is seems strange when adding it to runTests.
Eric Seidel (no email)
Comment 6 2009-10-28 15:06:24 PDT
Comment on attachment 41855 [details] Proposed patch moving the flush to the end of the test Chromium recently had similar troubles. I still think putting this in some nicely named function would make this much clearer. As-is, if we ever need to modify the "test shut down" procedure, it's difficult to tell where it is or what all of the code should be moved were this ever to move again. r- because I really think this needs to be put in a function with a nice name and called from this runTests() location. sendPixelResultsEOF() or something even more descriptive?
Alejandro G. Castro
Comment 7 2009-11-20 09:42:30 PST
(In reply to comment #6) > (From update of attachment 41855 [details]) > Chromium recently had similar troubles. I still think putting this in some > nicely named function would make this much clearer. As-is, if we ever need to > modify the "test shut down" procedure, it's difficult to tell where it is or > what all of the code should be moved were this ever to move again. r- because > I really think this needs to be put in a function with a nice name and called > from this runTests() location. > > sendPixelResultsEOF() or something even more descriptive? Right, refactoring the patch now ...
Alejandro G. Castro
Comment 8 2009-11-20 10:35:25 PST
Created attachment 43593 [details] Added a function with the termination code
Adam Barth
Comment 9 2009-11-30 12:34:49 PST
style-queue successfully ran check-webkit-style on attachment 43593 [details] without any errors
Eric Seidel (no email)
Comment 10 2009-11-30 22:10:18 PST
Comment on attachment 43593 [details] Added a function with the termination code LGTM.
WebKit Commit Bot
Comment 11 2009-11-30 22:41:23 PST
Comment on attachment 43593 [details] Added a function with the termination code Clearing flags on attachment: 43593 Committed r51525: <http://trac.webkit.org/changeset/51525>
WebKit Commit Bot
Comment 12 2009-11-30 22:41:28 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.