woodpecker

5398 commits 20 branches 74 tags 147 MiB

Author SHA1 Message Date

Author	SHA1	Message	Date
qwerty287	001b5639a6	Use `assert` for test (#3201 ) instead of `if`s	2024-01-14 19:33:58 +01:00
qwerty287	12c40eb957	Enable `gocritic` and don't ignore globally (#3159 ) Use `nolint` directives instead. From #2960	2024-01-10 15:34:44 +01:00
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

qwerty287

001b5639a6

Use assert for test (#3201 )

instead of `if`s

2024-01-14 19:33:58 +01:00

qwerty287

12c40eb957

Enable gocritic and don't ignore globally (#3159 )

Use `nolint` directives instead.

From #2960

2024-01-10 15:34:44 +01:00

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

Renamed from server/pipeline/stepStatus_test.go (Browse further)

3 commits