[SERVER-49504] Allow resmoke's mongo shell to log to Jasper Created: 14/Jul/20  Updated: 29/Oct/23  Resolved: 14/Dec/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.9.0

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

Issue Links:
Depends
Duplicate
is duplicated by SERVER-48156 Ensure resmoke works with Jasper Closed
Problem/Incident
Related
related to SERVER-53250 Evaluate consequences of using upgrad... Closed
Backwards Compatibility: Fully Compatible
Sprint: Evergreen 2020-07-27, Evergreen 2020-09-07, Evergreen 2020-09-21, Evergreen 2020-10-05, Evergreen 2020-10-19, Evergreen 2020-11-02, Evergreen 2020-11-16
Participants:
Linked BF Score: 0
Story Points: 0

 Description   

Allow the mongo shell spawned by resmoke to log to LogKeeper v3.

Suites that don't use fixtures run almost entirely from shell subprocesses, making this feature an easy way to validate the new logging path. We'll need to set up all the LogKeepver v3 related credentials in resmoke/evergreen.yml as part of this ticket as well.



 Comments   
Comment by Githook User [ 14/Dec/20 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-49504: Allow resmoke's mongo shell to log to Jasper
Branch: master
https://github.com/mongodb/mongo/commit/fff7a4baa0583cb8e14c8d75649b0ac019600b11

Comment by Githook User [ 07/Dec/20 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: Revert "SERVER-49504: Allow resmoke's mongo shell to log to Jasper"

This reverts commit 3c179e493589356f16641c40647cfd1418473d06.
Branch: master
https://github.com/mongodb/mongo/commit/2c50126f91f069b62bdb5c420aca8761e7486845

Comment by Robert Guo (Inactive) [ 07/Dec/20 ]

Going to revert this again due to unexpected behavior in pip on some static hosts. See comments on SERVER-53250 for more info. The code in this ticket is working as expected and will be committed again once the platform-specific pip issues are resolved.

Comment by Githook User [ 06/Nov/20 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-49504: Revert "Revert "SERVER-49504: Allow resmoke's mongo shell to log to Jasper""
Branch: master
https://github.com/mongodb/mongo/commit/3c179e493589356f16641c40647cfd1418473d06

Comment by Ryan Timmons [ 16/Oct/20 ]

Was there a PR for this? There's an obvious bug in the evergreen.yml syntax. The evergreen.yml line with CEDAR_PASSWORD doesn't have a backslash to escape the newline. I don't know how it could ever have worked.

Comment by Githook User [ 15/Oct/20 ]

Author:

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

Message: Revert "SERVER-49504: Allow resmoke's mongo shell to log to Jasper"

This reverts commit e9e1635d6c4a37a4f2d8ee20ccfa2c7e916121d6.
Branch: master
https://github.com/mongodb/mongo/commit/e62f90245be98c6763ae85441eb6ebd9448bb85c

Comment by Githook User [ 14/Oct/20 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-49504: Allow resmoke's mongo shell to log to Jasper
Branch: master
https://github.com/mongodb/mongo/commit/e9e1635d6c4a37a4f2d8ee20ccfa2c7e916121d6

Comment by Githook User [ 12/Oct/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: Revert "SERVER-49504: Allow resmoke's mongo shell to log to Jasper"

This reverts commit 308cc2fa21eb3a3d2b53cb47bb3dcdd3b259bf20.
Branch: master
https://github.com/mongodb/mongo/commit/8468e69c2eb6b5aee8a8828c7c22c22073916735

Comment by Billy Donahue [ 12/Oct/20 ]

This seems to have broken my invocation of resmoke.py?

me (in a venv):

python buildscripts/resmoke.py run --suite=sharding

resmoke:

Traceback (most recent call last):
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/job.py", line 80, in __call__
    self._run(queue, interrupt_flag)
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/job.py", line 127, in _run
    self._execute_test(test)
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/job.py", line 171, in _execute_test
    test(self.report)
  File "/opt/mongodbtoolchain/revisions/e5348beb43e147b74a40f4ca5fb05a330ea646cf/stow/python3-v3.Aah/lib/python3.7/unittest/case.py", line 663, in __call__
    return self.run(*args, **kwds)
  File "/opt/mongodbtoolchain/revisions/e5348beb43e147b74a40f4ca5fb05a330ea646cf/stow/python3-v3.Aah/lib/python3.7/unittest/case.py", line 588, in run
    result.startTest(self)
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/report.py", line 111, in startTest
    command = test.as_command()
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/testcases/interface.py", line 130, in as_command
    return self._make_process().as_command()
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/testcases/jstest.py", line 150, in _make_process
    return self.test_case_template._make_process()  # pylint: disable=protected-access
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/testing/testcases/jstest.py", line 107, in _make_process
    **self.shell_options)
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/core/programs.py", line 467, in mongo_shell_program
    return make_process(logger, args, **process_kwargs)
  File "/home/ubuntu/mongo-dev/work/mongo-vscode/buildscripts/resmokelib/core/programs.py", line 78, in make_process
    return process_cls(*args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'job_num'

Comment by Githook User [ 12/Oct/20 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-49504: Allow resmoke's mongo shell to log to Jasper
Branch: master
https://github.com/mongodb/mongo/commit/308cc2fa21eb3a3d2b53cb47bb3dcdd3b259bf20

Generated at Thu Feb 08 05:20:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.