Because of Bug 558190, all our Talos memory size measurement has stopped reporting the size of mozilla-runtime, meaning we have a fake improvement in measurements like Tp RSS. Basically, we just need to s/mozilla-runtime/plugin-container/g in Talos.
Is there any reason to keep references mozilla-runtime around at all in talos? (old branches that still refer to it, for example?)
AFAIK there are no branches still using mozilla-runtime, we switched to plugin-container everywhere (except maybe lorentz, but that's dying soon).
Created attachment 438522 [details] [diff] [review] mozilla-runtime -> plugin-container for all branches
Attachment #438522 - Flags: review?(anodelman)
Attachment #438522 - Flags: review?(anodelman) → review+
Comment on attachment 438522 [details] [diff] [review] mozilla-runtime -> plugin-container for all branches Checking in bcontroller.py; /cvsroot/mozilla/testing/performance/talos/bcontroller.py,v <-- bcontroller.py new revision: 1.14; previous revision: 1.13 done Checking in cmanager_linux.py; /cvsroot/mozilla/testing/performance/talos/cmanager_linux.py,v <-- cmanager_linux.py new revision: 1.10; previous revision: 1.9 done Checking in cmanager_win32.py; /cvsroot/mozilla/testing/performance/talos/cmanager_win32.py,v <-- cmanager_win32.py new revision: 1.10; previous revision: 1.9 done Checking in run_tests.py; /cvsroot/mozilla/testing/performance/talos/run_tests.py,v <-- run_tests.py new revision: 1.62; previous revision: 1.61 done
Attachment #438522 - Flags: checked-in+
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.