Details
-
Improvement
-
Resolution: Won't Do
-
Major - P3
-
None
-
None
-
None
-
None
-
Server Development Platform
Description
The line numbers from where a failure originates is also part of important info; this is missing currently from the feature added by SERVER-70718.
For example, the following exception
[js_test:move_primary_recipient_cmds] uncaught exception: Error: command failed: {
|
[js_test:move_primary_recipient_cmds] "ok" : 0,
|
[js_test:move_primary_recipient_cmds] "errmsg" : "Timestamp can't be null",
|
[js_test:move_primary_recipient_cmds] "code" : 2,
|
[js_test:move_primary_recipient_cmds] "codeName" : "BadValue",
|
[js_test:move_primary_recipient_cmds] "$clusterTime" : {
|
[js_test:move_primary_recipient_cmds] "clusterTime" : Timestamp(1680047888, 57),
|
[js_test:move_primary_recipient_cmds] "signature" : {
|
[js_test:move_primary_recipient_cmds] "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
|
[js_test:move_primary_recipient_cmds] "keyId" : NumberLong(0)
|
[js_test:move_primary_recipient_cmds] }
|
[js_test:move_primary_recipient_cmds] },
|
[js_test:move_primary_recipient_cmds] "operationTime" : Timestamp(1680047888, 56)
|
[js_test:move_primary_recipient_cmds] } with original command request: {
|
[js_test:move_primary_recipient_cmds] "_movePrimaryRecipientSyncData" : 1,
|
[js_test:move_primary_recipient_cmds] "returnAfterReachingDonorTimestamp" : Timestamp(0, 0),
|
[js_test:move_primary_recipient_cmds] "migrationId" : UUID("bcd423fb-7c1b-4547-9ad8-a07c771a3585"),
|
[js_test:move_primary_recipient_cmds] "databaseName" : "move_primary_recipient_cmds",
|
[js_test:move_primary_recipient_cmds] "fromShardName" : "move_primary_recipient_cmds-rs0",
|
[js_test:move_primary_recipient_cmds] "toShardName" : "move_primary_recipient_cmds-rs1",
|
[js_test:move_primary_recipient_cmds] "lsid" : {
|
[js_test:move_primary_recipient_cmds] "id" : UUID("6728254e-7641-4976-84e7-012fd1ffe680")
|
[js_test:move_primary_recipient_cmds] },
|
[js_test:move_primary_recipient_cmds] "$clusterTime" : {
|
[js_test:move_primary_recipient_cmds] "clusterTime" : Timestamp(1680047888, 56),
|
[js_test:move_primary_recipient_cmds] "signature" : {
|
[js_test:move_primary_recipient_cmds] "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
|
[js_test:move_primary_recipient_cmds] "keyId" : NumberLong(0)
|
[js_test:move_primary_recipient_cmds] }
|
[js_test:move_primary_recipient_cmds] }
|
[js_test:move_primary_recipient_cmds] } on connection: connection to ip-10-122-9-152:20041 :
|
[js_test:move_primary_recipient_cmds] _getErrorWithCode@src/mongo/shell/utils.js:24:13
|
[js_test:move_primary_recipient_cmds] doassert@src/mongo/shell/assert.js:18:14
|
[js_test:move_primary_recipient_cmds] _assertCommandWorked@src/mongo/shell/assert.js:766:25
|
[js_test:move_primary_recipient_cmds] assert.commandWorked@src/mongo/shell/assert.js:860:16
|
[js_test:move_primary_recipient_cmds] @jstests/sharding/move_primary/move_primary_recipient_cmds.js:39:8
|
[js_test:move_primary_recipient_cmds] @jstests/sharding/move_primary/move_primary_recipient_cmds.js:58:3
|
[js_test:move_primary_recipient_cmds] failed to load: jstests/sharding/move_primary/move_primary_recipient_cmds.js
|
[js_test:move_primary_recipient_cmds] exiting with code -3
|
is floated as
[resmoke] 23:58:31.979Z Summary of sharding suite: 3 test(s) ran in 29.56 seconds (2 succeeded, 0 were skipped, 1 failed, 0 errored)
|
The following tests failed (with exit code):
|
jstests/sharding/move_primary/move_primary_recipient_cmds.js (253 Failure executing JS file)
|
[FIRST Part of Exception]
|
uncaught exception: Error: command failed: {
|
"ok" : 0,
|
"errmsg" : "Timestamp can't be null",
|
"code" : 2,
|
"codeName" : "BadValue",
|
"$clusterTime" : {
|
"clusterTime" : Timestamp(1680047888, 57),
|
"signature" : {
|
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
|
"keyId" : NumberLong(0)
|
If you're unsure where to begin investigating these errors, consider looking at tests in the following order:
|
jstests/sharding/move_primary/move_primary_recipient_cmds.js
|
[resmoke] 23:58:31.980Z Exiting with code: 1
|
However, one still need to check the line number in the failing test which is present in the last few lines:
[js_test:move_primary_recipient_cmds] _getErrorWithCode@src/mongo/shell/utils.js:24:13
|
[js_test:move_primary_recipient_cmds] doassert@src/mongo/shell/assert.js:18:14
|
[js_test:move_primary_recipient_cmds] _assertCommandWorked@src/mongo/shell/assert.js:766:25
|
[js_test:move_primary_recipient_cmds] assert.commandWorked@src/mongo/shell/assert.js:860:16
|
[js_test:move_primary_recipient_cmds] @jstests/sharding/move_primary/move_primary_recipient_cmds.js:39:8
|
[js_test:move_primary_recipient_cmds] @jstests/sharding/move_primary/move_primary_recipient_cmds.js:58:3
|
[js_test:move_primary_recipient_cmds] failed to load: jstests/sharding/move_primary/move_primary_recipient_cmds.js
|
[js_test:move_primary_recipient_cmds] exiting with code -3
|
Attachments
Issue Links
- is related to
-
SERVER-70718 Resmoke on error should float the most important info to end of log.
-
- Closed
-