diff options
| author | Justin Seyster <justin.seyster@mongodb.com> | 2018-05-18 17:38:43 -0400 |
|---|---|---|
| committer | Justin Seyster <justin.seyster@mongodb.com> | 2018-05-22 18:29:41 -0400 |
| commit | cae95a2242cf5d359e474e819b3ea4a82696fc97 (patch) | |
| tree | 4e013d047c077a3847745bd37e93a6c967801205 /jstests/gle | |
| parent | a9deb701a7533b566a2eb703aff70bf2f03b147c (diff) | |
| download | mongo-cae95a2242cf5d359e474e819b3ea4a82696fc97.tar.gz | |
SERVER-35099 Increase wtimeout in get_last_error.js even more
So far, all of the getLastError timeouts in this test have been
increased to 2s, except for one lonely getLastError that is stuck at
an overly optimistic 50ms and another that's expected to time
out. Let's bump that 50ms getLastError to be 2s like all its friends.
Diffstat (limited to 'jstests/gle')
| -rw-r--r-- | jstests/gle/get_last_error.js | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/jstests/gle/get_last_error.js b/jstests/gle/get_last_error.js index 7a5e0f4b932..7d4c517ca82 100644 --- a/jstests/gle/get_last_error.js +++ b/jstests/gle/get_last_error.js @@ -26,8 +26,8 @@ if (gle.err === null) { assert.eq(gle.code, 2); } -gle = mdb.getLastErrorObj(1, 50); -print('Trying w=1, 50ms timeout'); +gle = mdb.getLastErrorObj(1, 2000); +print('Trying w=1, 2000ms timeout'); printjson(gle); assert.eq(gle.ok, 1); assert.eq(gle.err, null); |