woodpecker/server
6543 a63135363b
Step status update dont set to running again once it got stoped (#3151)
Because of the check `if step.Stopped == 0`

without the check there are edgecases where could be the case a stoped
steped can be markt as running again, witch is wrong.

I do remember we have "running" steps indefinetly in cancled pipelines.
This could be the fix, i just did not test that specific.

Anyway the func hat a good testcoverage ... so just look at the tests

_Source:
https://github.com/woodpecker-ci/woodpecker/pull/3143#discussion_r1446138088_
2024-01-09 18:34:55 +01:00
..
api Correct http cache headers for firefox (#3017) 2023-12-26 08:37:13 +01:00
badges Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
cache Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
ccmenu Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
cron Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
forge Load changed files for closed PR (#3067) 2023-12-29 22:50:31 +01:00
grpc Step status update dont set to running again once it got stoped (#3151) 2024-01-09 18:34:55 +01:00
logging Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
model Make config linking non-unique (#3128) 2024-01-07 16:12:27 +01:00
pipeline Step status update dont set to running again once it got stoped (#3151) 2024-01-09 18:34:55 +01:00
plugins Add another testcase (#3035) 2023-12-27 10:51:39 +01:00
pubsub Refactor/simplify pubsub (#2554) 2023-10-13 07:34:33 +02:00
queue Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
router Add option to disable version check in admin web UI (#3040) 2023-12-27 22:16:15 +01:00
store Hide PR tab if PRs are disabled (#3004) 2023-12-24 11:04:18 +02:00
web Add option to disable version check in admin web UI (#3040) 2023-12-27 22:16:15 +01:00
config.go Add option to disable version check in admin web UI (#3040) 2023-12-27 22:16:15 +01:00