[Bug][CircleCi] Negative workflow duration

[The0Danktor]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Will collecting and transforming data the crashes on the subtask extractJobs

this happens because for some reason a workflow stopped before it started causing it to have a negative durration

and the field is an bigint unsigned

time="2024-12-03 09:07:05" level=error msg=" [pipeline service] [pipeline #3] [task #16] subtask extractJobs ended unexpectedly\n\tWraps: (2) error adding result to batch (500)\n\tWraps: (3) Error 1264 (22003): Out of range value for column 'duration_sec' at row 262 (500)\n\tWraps: (4) Error 1264 (22003): Out of range value for column 'duration_sec' at row 262\n\tError types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *hintdetail.withDetail (4) *mysql.MySQLError"

What do you expect to happen

that it would work even with a negative duration
maby by changing them to positive or changing the field type in the database

How to reproduce

import a workflow in circleci that has a negative duration

Anything else

No response

Version

v1.0.1

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

@The0Danktor Hello there! I'm here to help you with any bugs, questions, or contributions you have in mind. If you need assistance, feel free to ask.

The issue you're encountering is due to the duration_sec field being defined as an unsigned bigint, which cannot store negative values. This results in an "Out of range value" error when a workflow has a negative duration ^[1].

To address this, you have a couple of options:

1. Convert Negative Durations to Positive: Modify the logic in the extractJobs subtask to convert negative durations to positive values before storing them. This can be done by taking the absolute value of the duration.

2. Change the Database Field Type: Alter the database schema to allow negative values by changing the duration_sec field from an unsigned bigint to a signed bigint. This would allow the storage of negative durations without errors.

Both approaches have their pros and cons, and the choice depends on how you want to handle negative durations in your data analysis. If you decide to submit a pull request, ensure that the changes are well-documented and tested to prevent any unintended side effects.

To continue talking to Dosu, mention @dosu.

[klesh]

Thanks for reporting the issue.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

[JFGHT]

Workaround:

ALTER TABLE _tool_circleci_jobs MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;
ALTER TABLE _tool_circleci_workflows MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;
ALTER TABLE _tool_circleci_pipelines MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;
ALTER TABLE cicd_pipelines MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;
ALTER TABLE cicd_tasks MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;
ALTER TABLE cicd_deployments MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;
ALTER TABLE cicd_deployment_commits MODIFY COLUMN duration_sec BIGINT DEFAULT NULL;

[varsis]

@klesh Can this be reopened? I'm experiencing this issue on my instance.

[klesh]

@varsis Sure, did you try @JFGHT 's workaround ?