Bug 54513 - new-run-webkit-tests: chromium DRT http/ tests crashes cmd.exe
Summary: new-run-webkit-tests: chromium DRT http/ tests crashes cmd.exe
Status: RESOLVED DUPLICATE of bug 58197
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-15 17:37 PST by Dirk Pranke
Modified: 2011-04-15 15:13 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Pranke 2011-02-15 17:37:19 PST
If I open a cmd.exe shell on Windows 7, and use the python version in depot_tools, set my PYTHONPATH to point to the WebKit\Tools\Scripts directory and run new-run-webkit-tests against the http tests, something happens that crashes not just DRT and the python binary, but cmd.exe itself. It seems to crash everything when the python code attempts to read the first line from DRT. 

This happens with either a debug or release build of DRT. the mock_drt python executable works fine. If you redirect the output, that works fine as well.

> set PYTHONPATH=d:\src\c\wtot\src\third_party\WebKit\Tools\Scripts
> d:\src\c\depot_tools\python.exe d:\src\c\wtot\src\third_party\WebKit\Tools\Scripts\new-run-webkit-tests --verbose --platform chromium-win http/tests/misc/401-alternative-content.php

When python attempts to read the first line of output from DRT, the whole thing crashes. If I run this in cygwin, or if I redirect either of stdout or stderr, it doesn't crash. Interestingly the only output from DRT is "PASS", so even that's not very suspicious. Also, if I run --platform mock-chromium-win instead (which uses the "mock" python binary instead), it also doesn't crash, so there's something about DRT that's weird.
Comment 1 Dirk Pranke 2011-04-15 15:13:49 PDT

*** This bug has been marked as a duplicate of bug 58197 ***