[SERVER-64853] Remove debug logging from JS tests Created: 23/Mar/22  Updated: 29/Oct/23  Resolved: 24/Mar/22

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-64193 Record log volume and upload result t... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: DAG 2022-04-04
Participants:

 Description   

A small number of tests are responsible for over 10% of all test logs on master, despite the last meaningful change being made in 2019. The test file also does not load any other files.

Assigning to myself for now to disable the logging in those tests



 Comments   
Comment by Githook User [ 24/Mar/22 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}

Message: SERVER-64853 remove debug logging code from FSM tests
Branch: master
https://github.com/mongodb/mongo/commit/edcfbbf40dd1e1d8b57cbbcd01c2515b706f8b23

Comment by Robert Guo (Inactive) [ 24/Mar/22 ]

Thanks for the info max.hirschhorn! Extremely valuable. Upon further inspection, I do see more evidence of the collection_uuid.js change being the culprit. The mongos log level change does not seem to cause measurably more logging. The number of bugs unintentionally caught by that one file seems problematic too.

Running a patch build to confirm the log level change; will update the ticket description if it turns out to be true.

Comment by Max Hirschhorn [ 24/Mar/22 ]

Is the issue necessarily the schema_validator_with_expr_variables.js FSM workload itself? Or could it be that it happens to run after a couple of the FSM workloads which set the mongos log level to verbosity 3 and never unset it?

One thing I'd like to point out about the schema_validator_with_expr_variables.js FSM workload is that it has managed to catch three (3) data consistency bugs it wasn't written to catch (WT-4961, WT-4965, SERVER-53575). Hopefully we have sufficient coverage elsewhere but I'd feel a little sad if we kept a test which has identified critical bugs as disabled for a long period of time.

Generated at Thu Feb 08 06:01:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.