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

Issue 640373003: util_test Clock.SleepNanoseconds: don’t set an upper bound for the amount of time spent sleeping (Closed)

Created:
6 years, 2 months ago by Mark Mentovai
Modified:
6 years, 2 months ago
Reviewers:
Robert Sesek
CC:
crashpad-dev_chromium.org
Base URL:
https://chromium.googlesource.com/crashpad/crashpad@master
Project:
crashpad
Visibility:
Public.

Description

util_test Clock.SleepNanoseconds: don’t set an upper bound for the amount of time spent sleeping. Even with the slop, this wound up being flaky, specifically on virtual machines. And guess what our automated test infrastructure runs on? TEST=util_test Clock.SleepNanoseconds R=rsesek@chromium.org Committed: https://chromium.googlesource.com/crashpad/crashpad/+/8f23d3e475e736af68333d95ff78c48cc6c4d80c

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -6 lines) Patch
M util/misc/clock_test.cc View 1 chunk +2 lines, -6 lines 0 comments Download

Messages

Total messages: 4 (1 generated)
Mark Mentovai
6 years, 2 months ago (2014-10-10 17:04:18 UTC) #2
Robert Sesek
LGTM. Yes, testing time is difficult.
6 years, 2 months ago (2014-10-10 17:54:07 UTC) #3
Mark Mentovai
6 years, 2 months ago (2014-10-10 18:01:08 UTC) #4
Message was sent while issue was closed.
Committed patchset #1 (id:1) manually as
8f23d3e475e736af68333d95ff78c48cc6c4d80c (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698