[Webkit-unassigned] [Bug 75499] New: Test results server is repeating runs

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jan 3 15:17:15 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=75499

           Summary: Test results server is repeating runs
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ojan at chromium.org
                CC: tony at chromium.org, jparent at google.com


http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=svg%2Fhixie%2Ftext%2F003.html

See for example the Webkit Mac10.6 (CG)(dbg) row. Each set of data for a run is repeated five times. The problem is that the data is successfully merging, but appengine is returning a 500 because we're exceeding the memory limit, so we retry and the same problem happens again. (see the 500s at the end http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Mac10.6%20%28CG%29%28dbg%29/builds/2310/steps/webkit_tests/logs/stdio)

As best I can tell here is the corresponding 500:
2012-01-03 13:48:34.411 /testfile/upload 500 39738ms 0kb Python-urllib/2.6
See details
74.125.248.75 - - [03/Jan/2012:13:48:34 -0800] "POST /testfile/upload HTTP/1.1" 500 0 - "Python-urllib/2.6" "test-results.appspot.com" ms=39739 cpu_ms=31712 api_cpu_ms=398 cpm_usd=0.993279 exit_code=105 instance=00c61b117c4a2afa8703f545ea5fa594fcd8e5d9
C 2012-01-03 13:48:34.387
Exceeded soft private memory limit with 156.695 MB after servicing 7 requests total
W 2012-01-03 13:48:34.387
While handling this request, the process that handled this request was found to be using too much memory and was terminated. This is likely to cause a new process to be used for the next request to your application. If you see this message frequently, you may have a memory leak in your application.

The long-term solution to this is to change the JSON data format to use less memory (e.g. use a single string as a run-length-encoding format, store data chunked by 100 runs at a time, etc). In the short-term we can add a check to make sure that the run currently being uploaded wasn't just uploaded.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list