Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(483)

Unified Diff: content/browser/loader/upload_progress_tracker_unittest.cc

Issue 2574143003: Implement upload progress handling in Mojo loading (Closed)
Patch Set: android build fix Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/browser/loader/upload_progress_tracker_unittest.cc
diff --git a/content/browser/loader/upload_progress_tracker_unittest.cc b/content/browser/loader/upload_progress_tracker_unittest.cc
index 508368d41f1be66b57133cac8e29e079e2ac7c07..cf556db2c94ec8b2366a01218c5d16530662715a 100644
--- a/content/browser/loader/upload_progress_tracker_unittest.cc
+++ b/content/browser/loader/upload_progress_tracker_unittest.cc
@@ -190,7 +190,7 @@ TEST_F(UploadProgressTrackerTest, TimePassed) {
EXPECT_EQ(1, report_count_);
upload_progress_tracker_.set_current_time(base::TimeTicks::Now() +
- base::TimeDelta::FromSeconds(1));
+ base::TimeDelta::FromSeconds(5));
tzik 2017/01/19 11:53:09 Note: 1s is not enough to trigger the upload progr
// The third timer task calls ReportUploadProgress since it's been long time
// from the last report.
@@ -221,7 +221,7 @@ TEST_F(UploadProgressTrackerTest, Rewound) {
EXPECT_EQ(1, report_count_);
upload_progress_tracker_.set_current_time(base::TimeTicks::Now() +
- base::TimeDelta::FromSeconds(1));
+ base::TimeDelta::FromSeconds(5));
// Even after a good amount of time passed, the rewound progress should not be
// reported.

Powered by Google App Engine
This is Rietveld 408576698