Specifically: mojo:view_manager_service_apptests_x64.nexe on Debug is taking > minute to complete. This is a major drag on my iteration times.
Whoever owns this test, is there anything we can do to speed it up?
Thanks,
John
Nick Bray
未讀,
2015年6月22日 下午3:46:462015/6/22
回覆作者
登入以回覆作者
轉寄
登入以轉寄訊息
刪除
你的權限不足,無法在這個群組刪除訊息
複製連結
檢舉訊息
登入以檢舉訊息
顯示原始貼文
該群組的電子郵件地址為匿名,或你需要檢視成員電子郵件地址的權限才能查看原始貼文
收件者:John Mccutchan、mojo...@chromium.org
The problem is that the test runner repeatedly tears down and reloads the entire executable and executable startup is slow due to design constraints. The simplest solutions are either to optimize the test runner or to move the test to a suite outside of normal iterations.
To unsubscribe from this group and stop receiving emails from it, send an email to mojo-dev+u...@chromium.org.
Viet-Trung Luu
未讀,
2015年6月22日 下午4:23:182015/6/22
回覆作者
登入以回覆作者
轉寄
登入以轉寄訊息
刪除
你的權限不足,無法在這個群組刪除訊息
複製連結
檢舉訊息
登入以檢舉訊息
顯示原始貼文
該群組的電子郵件地址為匿名,或你需要檢視成員電子郵件地址的權限才能查看原始貼文
收件者:Nick Bray、John Mccutchan、mojo...@chromium.org
Probably the right thing to do is to make those tests not leak state between tests (which forces us to run each test in a fresh shell). Unfortunately, no one owns the view manager right now. :(
(This is also a big hit when running tests on Android.)