Bug 75708 - Concurrent instances of DRT on Windows can stomp on each other's databases etc.
Summary: Concurrent instances of DRT on Windows can stomp on each other's databases etc.
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar, PlatformOnly
Depends on: 116729
Blocks: 38756
  Show dependency tree / graph
 
Reported: 2012-01-06 09:16 PST by Adam Roben (:aroben)
Modified: 2013-11-18 10:41 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 2012-01-06 09:16:58 PST 
http://trac.webkit.org/changeset/57328 (bug 36899) changed DumpRenderTree to use a DUMPRENDERTREE_TEMP environment variable for storing databases, etc., so that concurrent instances of DRT won't stomp on each other. But this support was never added to Windows. We need to support this on Windows if we want to run multiple copies of DRT in parallel.
Comment 1 Radar WebKit Bug Importer 2012-01-06 09:17:15 PST 
<rdar://problem/10654679>
Comment 2 Brent Fulgham 2013-05-24 10:55:16 PDT 
It looks like WebKit on Windows uses either CSIDL_LOCAL_APPDATA or CSIDL_APPDATA (depending on context) to store database and URL cache information.
Comment 3 Brent Fulgham 2013-05-24 16:11:07 PDT 
See Bug 116729 for an implementation that uses CFPreferences to store the current application's desired storage paths.  This is the technique being used in the OS X port, which seems to work properly in a concurrent run environment.
Comment 4 Brent Fulgham 2013-06-03 13:21:25 PDT 
For now, we will use new-run-webkit-tests hard-coding it to use a single worker.  This will ensure we don't have any problems running concurrently.

As a second step we will loosen this restriction once we've determined that the changes on Bug 116729 resolve the problem.
Comment 5 Brent Fulgham 2013-11-18 10:41:18 PST 
Fixed by use of separate environments per build process (Bug 116729).