Skip to content

Add remote links to results table and deal with engines that seem to pass but have the wrong results #68

@stellaprins

Description

@stellaprins
  • Add links as in foldout section of pass / FAIL (R) column

Amici, gillespy2, and vcell seem to pass while they do not really pass.

For remote runs:

  • in logs find "simulation failed: Reached maximum number of steps" for AMICI and change colour coding to "❌ FAIL" depending on that.
  • Investigate what goes wrong for gillespy2 and change colour coding depending on that (no specific reason found)
  • investigate why vcell does not pass and change label to "❌ FAIL" (status: "QUEUED")

Do same for local runs:

  • in logs find "simulation failed: Reached maximum number of steps" for AMICI and change colour coding to "❌ FAIL" depending on that.
  • Investigate what goes wrong for gillespy2 and change colour coding depending on that (no specific reason found)
  • investigate why vcell does not pass and change label to "❌ FAIL"

Address Padraig's comment on PR #69

  • Check whether the message in "Error (R)" column refers to the outcome of the test in "pass / FAIL (R)". If so, put error message under expandable arrow under the XFAIL/FAIL message in the "Error (R)" column, not in separate columns.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions