spindown now has a ENTROPY_DONT_KILL env

CHANGELOG.md

@@ -16,6 +16,8 @@ Version header format: `[version] Name - year-month-day (entropy-core compatibil
   - `configurationSchema` & `auxiliaryDataSchema` to `ProgramInterface`
   - added new testing function `jumpStartNetwork(entropy: Entropy) => Promise<undefined>` This function must be called now with a funded key to kick off the network. **It will not work for networks with less then 4 validators**
   - added new docker script for four nodes
+  - `spinNetworkDown` now has an access to the env var `ENTROPY_DONT_KILL` which will preserve the network
+    the initial though for this was to look at network logs for debugging
 
 ### Fixed
 

dev/testing-utils.mjs

@@ -136,6 +136,10 @@ total-block-time: ${headersSenseStart} blocks
 }
 
 export async function spinNetworkDown (networkType = 'four-nodes') {
+  if (!process.env.ENTROPY_DONT_KILL) {
+    console.warn('$ENTROPY_DONT_KILL is set not spinning the network down')
+    return false
+  }
   try {
     execFileSync('dev/bin/spin-down.sh', [networkType], { 
       shell: true, 

tests/end-to-end.test.ts

@@ -24,7 +24,7 @@ test('End To End', async (t) => {
   await run('network up', spinNetworkUp(networkType))
   t.teardown(async () => {
     await entropy.close()
-    if (!process.env.DONT_KILL) await spinNetworkDown(networkType).catch((error) =>
+    await spinNetworkDown(networkType).catch((error) =>
       console.error('Error while spinning network down', error.message)
     )
   })