[SERVER-17270] Allow changing test + buildlogger from javascript Created: 12/Feb/15  Updated: 26/May/18  Resolved: 26/May/18

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

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

For passthough tests in javascript it is important to be able to start a new buildlogger session which is registered in the smoke test result xml file.

Changing our passthrough tests, and build more serious test frameworks under smoke, require this kind of change to make logging sane, and diagnostics useful.

This could be done relatively easily by changing smoke to hold onto the file handles for std err/out and redirect to a different buildlogger endpoint based on a callback from the javascript test. In this way the javascript test can start a child test (maybe just with a prefix name) which will show up in the test results xml and with a new buildlogger endpoint (url). mpobrien005@gmail.com and I have discussed this plan so it is time to record a task.



 Comments   
Comment by Max Hirschhorn [ 26/May/18 ]

We'll eventually have a service that both resmoke.py and the mongo shell connect with to manage process and log endpoints. It isn't a goal to make it so you can log to a different endpoint inside of the test. We've instead opted to try and integrate more with resmoke.py.

Comment by Max Hirschhorn [ 12/Jun/15 ]

Could scotthernandez or mpobrien provide some details as to what a "callback from the javascript test" might look like? For example, having a socket open between the smoke.py process and the mongo shell to communicate what test the shell was about to run got rejected during the planning phases of resmoke.py.

Additionally, SERVER-1424 made it so that each individual test run as part of the passthrough has its own logkeeper endpoint and its own test status entry in the report.json. What more work is desired here in terms of logging?

Generated at Thu Feb 08 03:43:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.