[SERVER-33734] Improve jsTestLog filterability Created: 07/Mar/18  Updated: 29/Oct/23  Resolved: 15/Mar/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.15, 3.6.5, 3.7.4

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6, v3.4
Sprint: Repl 2018-03-26
Participants:

 Description   

jsTestLog usually shows different sections of a test and would be useful to catch in one filter. There is no special formatting for each log line of a jsTestLog, just for the line at the beginning and at the end. Rewriting:

[js_test:resync] 2018-03-07T17:18:27.622+0000 ----
[js_test:resync] 2018-03-07T17:18:27.622+0000 Restarting node B
[js_test:resync] 2018-03-07T17:18:27.622+0000 ----

as this (or something similar) would make it more filterable in lobster. (By filtering on "----")

[js_test:resync] 2018-03-07T17:18:27.622+0000 --------
[js_test:resync] 2018-03-07T17:18:27.622+0000 ---- Restarting node B
[js_test:resync] 2018-03-07T17:18:27.622+0000 --------



 Comments   
Comment by Githook User [ 19/Apr/18 ]

Author:

{'email': 'judah@mongodb.com', 'username': 'judahschvimer', 'name': 'Judah Schvimer'}

Message: SERVER-33734 Improve jsTestLog filterability

(cherry picked from commit 54dc55063a25fdcae65356c2515e55768181dc80)
Branch: v3.6
https://github.com/mongodb/mongo/commit/0ddbfab435ea98ce9a8070fca6eabb4004f80d08

Comment by Githook User [ 18/Apr/18 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-33734 Improve jsTestLog filterability

(cherry picked from commit 54dc55063a25fdcae65356c2515e55768181dc80)
Branch: v3.4
https://github.com/mongodb/mongo/commit/0e85602411f0bf38af7eb0efe816d0ca0c58b0c8

Comment by Githook User [ 15/Mar/18 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-33734 Improve jsTestLog filterability
Branch: master
https://github.com/mongodb/mongo/commit/54dc55063a25fdcae65356c2515e55768181dc80

Comment by Githook User [ 15/Mar/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: Revert "SERVER-33734 Improve jsTestLog filterability"

This reverts commit a65f5add63e89bf4303c4ea6abac1cefac81d98b.
Branch: master
https://github.com/mongodb/mongo/commit/e9f87c17cc5e6c7f908e6abe55ad021862d51373

Comment by Githook User [ 15/Mar/18 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-33734 Improve jsTestLog filterability
Branch: master
https://github.com/mongodb/mongo/commit/a65f5add63e89bf4303c4ea6abac1cefac81d98b

Comment by Robert Guo (Inactive) [ 12/Mar/18 ]

Per offline discussion with judah.schvimer, we're going to go with the jsTest prefix. This is the convention we use for server log components. The contextual dashed lines are kept to retain the visual distinction and are intentionally prefixed so it's obvious where they come from. They can be filtered out with an additional filter on additionalComponent

[js_test:resync] 2018-03-07T17:18:27.622+0000 [jsTest] --------
[js_test:resync] 2018-03-07T17:18:27.622+0000 [jsTest] [additionalComponent] Restarting node B
[js_test:resync] 2018-03-07T17:18:27.622+0000 [jsTest] --------

Comment by Jonathan Abrahams [ 08/Mar/18 ]

A better solution may be to use lobster with multi line search capability.

Generated at Thu Feb 08 04:34:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.