The experiment tools generate different bash scripts then execute them.
Some of these bash scripts cannot be executed directly from the experiment tools.
However, these bash scripts seems fine, as running them directly seems to work...
Steps to reproduce
Use the data_storage branch, commit d437b38a64eee7a6fa8c9be for example
In the batsim_command of file
./tools/experiments/instance_examples /pybatsim_filler_medium.yaml,
execute batsim with valgrind: valgrind batsim ... instead of batsim ...
This output is obtained by calling the bash scripts generated by the previous command.
Run batsim: bash test/out/instance_examples/pfmedium/batsim_command.sh
==10523== Memcheck, a memory error detector
==10523== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10523== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==10523== Command: batsim -p platforms/energy_platform_homogeneous_no_net_128.xml -w workload_profiles/batsim_paper_workload_example.json -e test/out/instance_examples/pfmedium/out
==10523==
[0.000000] [workload/INFO] Loading JSON workload 'workload_profiles/batsim_paper_workload_example.json'...
[0.000000] [jobs/INFO] Loaded job 0 from workload workload_profiles/batsim_paper_workload_example.json
[0.000000] [jobs/INFO] Loaded job 1 from workload workload_profiles/batsim_paper_workload_example.json
...
[0.000000] [network/INFO] Creating UDS socket on '/tmp/bat_socket'
[0.000000] [network/INFO] Waiting for an incoming connection...
Description
The experiment tools generate different bash scripts then execute them.
Some of these bash scripts cannot be executed directly from the experiment tools. However, these bash scripts seems fine, as running them directly seems to work...
Steps to reproduce
valgrind batsim ...
instead ofbatsim ...
Output
Execution script output
"Normal" output
This output is obtained by calling the bash scripts generated by the previous command. Run batsim:
bash test/out/instance_examples/pfmedium/batsim_command.sh