You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The (relevant parts of the) Orthanc logs are displayed in the CI output when one of the checks fails.
Testing
No response
Documentation
No response
Dependencies
No response
Details and Comments
At the moment, some of the system test checks might fail because of something going wrong during the Orthanc processing, but requires re-running locally and manually inspecting the logs to find out what.
Would be nice if we could see this immediately in the CI output.
The text was updated successfully, but these errors were encountered:
yeah could have a function which runs docker compose logs on the production components if there's a non zero exit and then propogates the exit code would be good.
Not sure how to make Orthanc return an non-zero exit code from the plugin though, I've tried adding raise SystemExit in try/except blocks, e.g. when it fails to connect to the FTP server, but that doesn't make the Orthanc service fail, it just shows up in the logs.
Definition of Done / Acceptance Criteria
The (relevant parts of the) Orthanc logs are displayed in the CI output when one of the checks fails.
Testing
No response
Documentation
No response
Dependencies
No response
Details and Comments
At the moment, some of the system test checks might fail because of something going wrong during the Orthanc processing, but requires re-running locally and manually inspecting the logs to find out what.
Would be nice if we could see this immediately in the CI output.
The text was updated successfully, but these errors were encountered: