Chrome profiles not cleaned up after running full layout tests |
||||||
Issue descriptionWhen I run all the LayoutTests on my local Linux box: python third_party/WebKit/Tools/Scripts/run-webkit-tests --target=Optimized --additional-driver-flag=--enable-blink-features=LayoutNG --num-retries=1 I end up with ~800 Chrome profiles in my /tmp directory. The way I noticed this was by running out of disk space every few days. The profiles are named: .org.chromium.Chromium.XXXXXXX I was unable to located responsible code and fix this myself.
,
Oct 2 2017
I haven't yet observed those in my /tmp directory on my Linux workstation... if you clear your /tmp directory and run the layout tests once, do you get ~800 of these profile directories every time?
,
Oct 2 2017
Yep. Ran the full suite today: src (abspos_layoutng)> ls -a /tmp | grep Chromium | wc 995 995 29850
,
Nov 29 2017
Does anyone know anyone who this can be assigned to?
,
Nov 29 2017
Unfortunately, I don't think there's anyone to assign this to now, since nobody in particular is responsible for run-webkit-tests. But if anybody can add more information about this (e.g. under what circumstances these profiles in /tmp are added) it may be helpful for investigating this later.
,
Nov 30
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 30
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jeffcarp@chromium.org
, Oct 2 2017