diff options
| author | petewil@chromium.org <petewil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-09 05:20:40 +0000 |
|---|---|---|
| committer | petewil@chromium.org <petewil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-09 05:20:40 +0000 |
| commit | 0f7fcf0e3837f15d6d4fef7a1fb17416f0e48ea1 (patch) | |
| tree | f351b87bdd8759a9baa76d270a8c3e419d526726 /chrome/browser/ui/browser_tabstrip.cc | |
| parent | ca98bd3267d0da56c4ca59243de39f7daeebbf80 (diff) | |
| download | chromium_src-0f7fcf0e3837f15d6d4fef7a1fb17416f0e48ea1.zip chromium_src-0f7fcf0e3837f15d6d4fef7a1fb17416f0e48ea1.tar.gz chromium_src-0f7fcf0e3837f15d6d4fef7a1fb17416f0e48ea1.tar.bz2 | |
Test code to see if a timer fixes the issue for the majority of cases.
Our Push Messaging test fails a fraction of the time (perhaps 10-20% of the
time). The way that the push messaging test works is that it is a buildbot
which builds the source and then runs the test, so to test this I need to check
the source code in for the buildbot to run the test for me, even though the code
is not final.
The current theory is that the Push Messaging Canary Test is exiting immediately
after recieving the push message from the wire. The invalidation code (Push
Messaging relies on A sync invalidation service, which has a library that
reports reciept of the message back the server. It seems that the reports back
to the server are not reliable, so the server thinks the client is flaky.
To investigate a fix to this, I'll add code which delays the time test by two
seconds to allow the ack to propagate back to the invalidation service.
BUG=229038
Review URL: https://chromiumcodereview.appspot.com/13483025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@193015 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/ui/browser_tabstrip.cc')
0 files changed, 0 insertions, 0 deletions