Eric cccec6574c
fixes to get hardhat process launching at the test-level
- removed ethersuite as the base testing suite for multinodesuite because the need to launch hardhat before ethersuite setup and kill hardhat after ethersuite teardown was required. Removing ethersuite allowed for checking if a connection to hardhat was established. If no connection established, hardhat would need to be started via the test config. If there was a connection established, a snapshot is taken during test setup and reverted during teardown.
- modified the way the hardhat process was launched, because evaluating a command using chronos startProcess would wait for the command to complete before access to the output stream was given. Instead, we now launch the hardhat executable from node_modules/.bin/hardhat.
- modify the way the processes are exited by killing them immediately.
- fix warnings
2023-12-06 15:41:18 +11:00
..
2023-12-06 15:40:47 +11:00
2022-01-10 09:32:56 -06:00
2023-09-13 16:17:56 +02:00
2023-08-01 16:47:57 -07:00
2023-08-01 16:47:57 -07:00
2023-12-06 15:39:08 +11:00
2023-08-01 16:47:57 -07:00
2023-08-01 16:47:57 -07:00
2023-04-19 15:06:00 +02:00
2023-12-06 15:39:08 +11:00
2023-09-13 16:17:56 +02:00