github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-23 07:15:48 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Negative duration time in a workflow run. #14536

New Issue
Open
opened 2025-11-02 11:15:34 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 11:15:34 -06:00
Owner
Copy Link

Originally created by @NorthRealm on GitHub (Jun 2, 2025).

Description

There's a negative duration time in one of my workflow runs.
I was testing my runner after moving virtual machines and encountered consecutive failures. I did rerun jobs and found this negative duration record.
I don't even know where went wrong, as it's quite a rare occurrence.

Gitea Version

1.25.0+dev-86-g7149c9c55d built with GNU Make 4.4.1, go1.24.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Image

Image

action_run:

Image

action_run_job:

Image

action_task:

Image

Git Version

2.47.2

Operating System

Debian

How are you running Gitea?

Gitea in Docker. Nightly version from docker.gitea.com

Database

PostgreSQL

Originally created by @NorthRealm on GitHub (Jun 2, 2025). ### Description There's a negative duration time in one of my workflow runs. I was testing my runner after moving virtual machines and encountered consecutive failures. I did rerun jobs and found this negative duration record. I don't even know where went wrong, as it's quite a rare occurrence. ### Gitea Version 1.25.0+dev-86-g7149c9c55d built with GNU Make 4.4.1, go1.24.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![Image](https://github.com/user-attachments/assets/045d09ba-8e5e-4612-8813-e0e1066c13be) ![Image](https://github.com/user-attachments/assets/334be537-6a25-4509-a2a2-f08200cc34e9) action_run: ![Image](https://github.com/user-attachments/assets/ea44a154-3e99-4b36-9381-07c0908b6389) action_run_job: ![Image](https://github.com/user-attachments/assets/478b746f-a755-4633-89cb-4289e03be338) action_task: ![Image](https://github.com/user-attachments/assets/3ca4396f-9935-417c-8c99-6ae27a59f43b) ### Git Version 2.47.2 ### Operating System Debian ### How are you running Gitea? Gitea in Docker. Nightly version from `docker.gitea.com` ### Database PostgreSQL
GiteaMirror added the topic/gitea-actionstype/bug labels 2025-11-02 11:15:34 -06:00
GiteaMirror commented 2025-11-02 11:15:35 -06:00
Author
Owner
Copy Link

@NorthRealm commented on GitHub (Jun 2, 2025):

I just edited post adding relevant database records I find.

@NorthRealm commented on GitHub (Jun 2, 2025): I just edited post adding relevant database records I find.
GiteaMirror commented 2025-11-02 11:15:35 -06:00
Author
Owner
Copy Link

@ChristopherHX commented on GitHub (Jun 2, 2025):

I believe the data that yield to the negative duration in previous_duration has been deleted at the the time of the rerun and saving the previous_duration field.

Maybe race conditions while trying to rerun multiple jobs one by one, while the previous rerun job is still running.

Could be so many things.

@ChristopherHX commented on GitHub (Jun 2, 2025): I believe the data that yield to the negative duration in previous_duration has been deleted at the the time of the rerun and saving the previous_duration field. Maybe race conditions while trying to rerun multiple jobs one by one, while the previous rerun job is still running. Could be so many things.
GiteaMirror commented 2025-11-02 11:15:35 -06:00
Author
Owner
Copy Link

@Soft-icode commented on GitHub (Jun 2, 2025):

OK

@Soft-icode commented on GitHub (Jun 2, 2025): **OK**
GiteaMirror commented 2025-11-02 11:15:36 -06:00
Author
Owner
Copy Link

@merlinz01 commented on GitHub (Oct 1, 2025):

I'm having a similar issue with incorrect durations as shown below:

Image Image

Gitea 1.25.0-rc0
Gitea Actions Runner 0.2.13 on Windows amd64

@merlinz01 commented on GitHub (Oct 1, 2025): I'm having a similar issue with incorrect durations as shown below: <img width="1202" height="193" alt="Image" src="https://github.com/user-attachments/assets/795e154d-0eac-4f39-8869-63f0a5df0cff" /> <img width="1212" height="232" alt="Image" src="https://github.com/user-attachments/assets/8d301029-21e1-4a3e-9a91-5f1bf1ecb6f0" /> Gitea 1.25.0-rc0 Gitea Actions Runner 0.2.13 on Windows amd64
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/gitea-actions type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14536
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?