Handling Python related errors in the buildstatus file #25

Closed
opened 2024-07-24 18:55:35 +02:00 by antux18 · 2 comments
Collaborator

Those errors are not handled by the Python script itself. Maybe it should be handled by the script that calls ECG?

Those errors are not handled by the Python script itself. Maybe it should be handled by the script that calls ECG?
Author
Collaborator

Also they should be present in the output log file.

Also they should be present in the output log file.
antux18 self-assigned this 2024-07-26 17:08:49 +02:00
Author
Collaborator

Reopened because the current "try, except" workaround isn't good. This should be handled by the script that calls ECG.

Reopened because the current "try, except" workaround isn't good. This should be handled by the script that calls ECG.
antux18 reopened this issue 2024-08-05 15:56:03 +02:00
antux18 added the
Kind/Enhancement
Priority
High
labels 2024-08-05 16:03:42 +02:00
antux18 added
Priority
Medium
and removed
Priority
High
labels 2024-08-05 16:21:32 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: GuilloteauQ/study-docker-repro-longevity#25
No description provided.