[SERVER-2255] give js tests more control over spawned shells Created: 20/Dec/10  Updated: 14/Apr/16  Resolved: 15/Mar/16

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

Type: Improvement Priority: Minor - P4
Reporter: Aaron Staple Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Several of our js tests rely on spawned shells to run operations in parallel with the main test script. If the interface for managing these spawned shells was a bit more flexible we might be able to make test failures more clear and eliminate some bad failure conditions (for example waiting forever).

Some things which would be immediately helpful:

  • being able to check if a shell has finished without waiting for it to finish
  • being able to wait for a shell to finish, but with a timeout
  • explicit interface to audit errors from the returned shell (via shell return code or another mechanism)

I'm sure other features would be useful too - these are just ones that come to mind immediately.

As an aside - another option would be to allow threading in shells. This might make our tests clearer as well as easier to control (since we don't have to serialize input scripts for separate processes) and errors might be easier to detect as well. This functionality is currently implemented for our v8 mode but not for spidermonkey.



 Comments   
Comment by Mira Carey [ 15/Mar/16 ]

Over the years we've migrated towards using js threads more heavily for parallel tests and don't really need more sophisticated tooling for sub shells.

Closing as gone away

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