search

edf-hpc / unclebench

10 stars 4 forks source link

users should be able to follow compilation process #2

Closed rezib closed 7 years ago

rezib commented 8 years ago

On the first run, unclebench compiles the benchmark, with the following output:

$ ubench run -b vasp -p athos

---- vasp description files are already present in run directory and will be overwritten.

---- launching  vasp  with default node configuration

Then, the compilation process starts, the command ends and the user has no hint to follow the compilation. So there is no way to check if everything is going well, and when the job start...

It would be better if the user has a way to know when the compilation happens, if everything is going well, where to check for errors, and when he/she's supposed to get jobs running.

pierretr commented 8 years ago

This issue could be solved by a "ubench log" command which would return logs from each step of the benchmark. Thus user would be able to follow all the steps from compilation to the end of the benchmark execution.

pierretr commented 7 years ago

Available since version 0.2.0.