gothonly prepares and launches its local network with all components needed for a requestor agent to connect to and run its tasks against it.
gothwill patiently wait for the developer to do whatever they need and will dutifully record its logs for further examination once the user is finished with their activity.
yagnafrom the its repository's main branch, along with other necessary components, such as the VM runtime,
yagnadocker image based on the artifacts we downloaded, as well as get some other pre-built docker images,
YAGNA_APPKEY, the URL and the port that you need to use to run your requestor agent within goth's test network.
gothand press Ctrl-C to finish the interactive run and allow
gothto proceed with some cleanup that ensures any test artifacts are remove and that subsequent runs can be lanuched without issues.
/tmp/goth-testsor, more exactly, under whatever location
$TEMP_DIR/goth-testsresolves to in your shell. This path will depend either on the shell environment or the operating system on which the tests are being run (see
tempfile.gettempdirfor more details).
gothwill create a timestamped directory there, e.g.:
goth_20201221_172759+0000which will contain all the logs that this run was able to collect from all the components of your local Golem network:
runner.log- the logs for the goth runner itself. This includes the output that goth produces to the console but it also includes a whole lot of additional DEBUG-level logs.
proxy.log- contains the traffic between the nodes and the agents in the goth's network
test_interactive_vm- the directory in which the logs for each of the components launched by the runner are stored. You'll be most interested in the following ones:
provider_N.log- the debug logs from the provider daemons
provider_agent_N.log- the debug logs from the provider agents - including also the logs from each provider's execution units which will be of most interest to you as the developer of the application that's executed there,
requestor.log- the debug logs from the requestor daemon you're connecting your requestor agent to