As of 2cb53ba1f4b6 (Aug 30, 2018), ChromeDownloadManagerDelegateTest.LastSavePath times out on linux when run with other tests.

See https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=unit_tests&tests=ChromeDownloadManagerDelegateTest.LastSavePath
or run out/Default/unit_tests '--gtest_filter=PageLoadCappingInfoBarDelegateTest.ClickingCreatesNewInfobar:ChromeDownloadManagerDelegateTest.LastSavePath'

The timeout happens if the test is run after any other test that instantiates the g_default_download_directory singleton, which happens to be any test that creates a TestingProfile (maybe others too). The LastSavePath test needs to override the value of the default download path preference, but it needs to be the one creating g_default_download_directory in order to do that. Because previous tests have already created the singleton, it will have the wrong value in the LastSavePath test, causing it to time out.