190236 2018-10-02 23:01:05 -0700 [WinCairo][BuildBot] archive-test-results fails to delete pywebsocket.ws.log-err.txt 2018-10-03 19:46:26 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 190248 https://bugs.webkit.org/show_bug.cgi?id=188640 P2 Normal --- 1 fujii webkit-unassigned lforschler oldest_to_newest 1465922 0 fujii 2018-10-02 23:01:05 -0700 [WinCairo][BuildBot] archive-test-results fails to delete pywebsocket.ws.log-err.txt Since enable wpt in Bug 190129. https://build.webkit.org/builders/WinCairo%2064-bit%20WKL%20Release%20%28Tests%29/builds/1793 > Traceback (most recent call last): > File "./Tools/BuildSlaveSupport/test-result-archive", line 110, in <module> > sys.exit(main()) > File "./Tools/BuildSlaveSupport/test-result-archive", line 46, in main > return archive_test_results(options.configuration, options.platform, layoutTestResultsDir) > File "./Tools/BuildSlaveSupport/test-result-archive", line 94, in archive_test_results > shutil.rmtree(layoutTestResultsDir) > File "C:\tools\python\lib\shutil.py", line 266, in rmtree > onerror(os.remove, fullname, sys.exc_info()) > File "C:\tools\python\lib\shutil.py", line 264, in rmtree > os.remove(fullname) > WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'C:\\WebKit-BuildWorker\\wincairo-wkl-release-tests\\build\\layout-test-results\\pywebsocket.ws.log-err.txt' > program finished with exit code 1 1465923 1 fujii 2018-10-02 23:01:49 -0700 This looks similar with bug 188640. 1465929 2 fujii 2018-10-02 23:07:51 -0700 If I run wpt, some processes alway remain. https://github.com/WebKit/webkit/blob/e507125c68037bbdd74e7197da0d80c34d41765c/Tools/Scripts/webkitpy/layout_tests/servers/web_platform_test_server.py#L155 I guess this does't work as expected on Windows. 1465935 3 fujii 2018-10-02 23:40:17 -0700 Committed r236786: <https://trac.webkit.org/changeset/236786> 1466287 4 fujii 2018-10-03 19:46:26 -0700 Basuke is woking on this issue in Bug 190248. *** This bug has been marked as a duplicate of bug 190248 ***