no obvious way to debug remote execution failures

[gidden]

I just get "failed" in the jobs pane without any explanation

[gidden]

(note the cyclus output at the bottom was from a local run)

[FlanFlanagan]

With cyclus it would show you the input file you ran on the website.

I'm not sure if the input here is incorrect or if it's a connection issue.

[gidden]

The input here is definitely bad, but you have no idea what went wrong based on the UI feedback, only that the job failed.

[yarden-livnat]

Is there a text message in the console (i..e the bottom panel that says ‘Cyclus run complete’)?

I don’t have Cyclus installed on my mac and I’m not sure what kind of error messages Cyclus provides.

On Jun 5, 2015, at 10:30 AM, Matthew Gidden [email protected] wrote:

The input here is definitely bad, but you have no idea what went wrong based on the UI feedback, only that the job failed.

—
Reply to this email directly or view it on GitHub #86 (comment).

[gidden]

That occurs for local runs, but there is no response for remote runs. Only
the job being "queued" and then "failed".

On Fri, Jun 5, 2015 at 12:11 PM, Yarden [email protected] wrote:

Is there a text message in the console (i..e the bottom panel that says
‘Cyclus run complete’)?

I don’t have Cyclus installed on my mac and I’m not sure what kind of
error messages Cyclus provides.

On Jun 5, 2015, at 10:30 AM, Matthew Gidden [email protected]
wrote:

The input here is definitely bad, but you have no idea what went wrong
based on the UI feedback, only that the job failed.

—
Reply to this email directly or view it on GitHub <
https://github.com/cyclus/cyclist2/issues/86#issuecomment-109354259>.

—
Reply to this email directly or view it on GitHub
#86 (comment).

Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph. 225.892.3192