[MESOS-3820] Test-only libprocess reinitialization

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: libprocess, test
• Labels: mesosphere
• Epic Name: libprocess-finalize
• Story Points: 3
• Assignee: Joseph Wu
• Reporter: Joseph Wu
• Shepherd: Joris Van Remoortere
• Created: 02/Nov/15 23:40
• Updated: 24/Oct/16 23:22
• Resolved: 24/Oct/16 23:22

Description

Background
Libprocess initialization includes the spawning of a variety of global processes and the creation of the server socket which listens for incoming requests. Some properties of the server socket are configured via environment variables, such as the IP and port or the SSL configuration.

In the case of tests, libprocess is initialized once per test binary. This means that testing different configurations (SSL in particular) is cumbersome as a separate process would be needed for every test case.

Proposal

1. Add some optional code between some tests like:

   // Cleanup all of libprocess's state, as if we're starting anew.
   process::finalize(); 
   
   // For tests that need to test SSL connections with the Master:
   openssl::reinitialize();
   
   process::initialize();
   

   See MESOS-3863 for more on process::finalize.

Issue Links

• blocks: MESOS-3753 Test the HTTP Scheduler library with SSL enabled