{"action":"opened","issue":{"url":"https://api.github.com/repos/edf-hpc/unclebench/issues/2","repository_url":"https://api.github.com/repos/edf-hpc/unclebench","labels_url":"https://api.github.com/repos/edf-hpc/unclebench/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/edf-hpc/unclebench/issues/2/comments","events_url":"https://api.github.com/repos/edf-hpc/unclebench/issues/2/events","html_url":"https://github.com/edf-hpc/unclebench/issues/2","id":144211153,"number":2,"title":"users should be able to follow compilation process","user":{"login":"rezib","id":1862918,"avatar_url":"https://avatars.githubusercontent.com/u/1862918?v=3","gravatar_id":"","url":"https://api.github.com/users/rezib","html_url":"https://github.com/rezib","followers_url":"https://api.github.com/users/rezib/followers","following_url":"https://api.github.com/users/rezib/following{/other_user}","gists_url":"https://api.github.com/users/rezib/gists{/gist_id}","starred_url":"https://api.github.com/users/rezib/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rezib/subscriptions","organizations_url":"https://api.github.com/users/rezib/orgs","repos_url":"https://api.github.com/users/rezib/repos","events_url":"https://api.github.com/users/rezib/events{/privacy}","received_events_url":"https://api.github.com/users/rezib/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-29T09:40:10Z","updated_at":"2016-03-29T09:40:10Z","closed_at":null,"body":"On the first run, unclebench compiles the benchmark, with the following output:\r\n\r\n```\r\n$ ubench run -b vasp -p athos\r\n\r\n---- vasp description files are already present in run directory and will be overwritten.\r\n\r\n---- launching  vasp  with default node configuration\r\n```\r\n\r\nThen, 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...\r\n\r\nIt 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.\r\n"}}