Retry backoff policy for failed builds #146

New Issue

Closed

opened 2022-09-09 10:03:04 +02:00 by WeaponMan · 2 comments

WeaponMan commented

2022-09-09 10:03:04 +02:00

Would be nice to have some kind of retry and backoff policy for failed builds.

For example:

java11-openjdk - has failed build that was some kind of connection issue, auto rebuild will solve it
firefox - seems that another build of firefox was running and build failed on some kind of python server that was suppose to listen on network port

Would be nice to have some kind of retry and backoff policy for failed builds. For example: * java11-openjdk - has failed build that was some kind of connection issue, auto rebuild will solve it * firefox - seems that another build of firefox was running and build failed on some kind of python server that was suppose to listen on network port

anonfunc added the

enhancement

label 2022-09-09 12:27:11 +02:00

anonfunc commented

2022-09-09 12:30:32 +02:00

Owner

ALHP actually has some error detection, see ff963ec039/proto_package.go (L247).

I agree this could be improved, and there are some unresolved bugs in that code. For example, this build error from firefox you mentioned is not being detected consistently (even if the regex matches the log correctly).
I'll have a look if I find time. Maybe we can move this detection into a separate config file so contribution can be easier.

A general retry mechanic is certainly possible, but with the limited resources the current buildserver has I would prefer to target specific known build errors.

ALHP actually has some error detection, see https://git.harting.dev/ALHP/ALHP.GO/src/commit/ff963ec039e18d726ae2210efc2e54099e758607/proto_package.go#L247. I agree this could be improved, and there are some unresolved bugs in that code. For example, this build error from firefox you mentioned is not being detected consistently (even if the regex matches the log correctly). I'll have a look if I find time. Maybe we can move this detection into a separate config file so contribution can be easier. A general retry mechanic is certainly possible, but with the limited resources the current buildserver has I would prefer to target specific known build errors.

anonfunc referenced this issue

2022-10-01 19:45:11 +02:00

firefox missing #152

anonfunc commented

2023-06-03 13:50:47 +02:00

Owner

Closing this as wontfix. If there is a new detection for a specific build-error needed, please open a new issue.

I still think this would probably only waste resources now. We have detection for almost all build errors that can occur (that we can actually rebuild successfully), trying failed packages over and over would only lead to more delay for new package builds. Closing this as `wontfix`. If there is a new detection for a specific build-error needed, please open a new issue.

anonfunc closed this issue

2023-06-03 13:50:47 +02:00

anonfunc added

wontfix

and removed

enhancement

labels 2023-06-03 13:50:52 +02:00