libelektra: Jenkins: Retry Failed Builds
Description
Currently the Jenkins build fails quite often for various reasons. This issue should list some of the problems that currently include:
- failing Maven builds,
- failing Homepage builds,
- internal compiler errors,
- CMake install failures,
- workspace removal failures,
- Haskell build failures,
- APT install failures,
- timeouts,
- failing tests,
- connection problems, and
- Git commit failures
.
Failures
| Branch | Failure Reason | Failed Build Job/Stage |
|---|---|---|
PR #2932 |
Maven build | debian-unstable-clang-asan |
master |
Homepage build | Deploy Website |
master |
Homepage build | Deploy Website |
PR #2945 |
Internal compiler error | build-elektra-web-base |
master |
Cmake install failure | debian-stretch-full |
master |
Workspace removal failure | Main builds |
master |
Workspace removal failure | Main builds |
master |
Workspace removal failure | Main builds |
master |
Workspace removal failure | Main builds |
master |
Workspace removal failure | Main builds |
master |
Workspace removal failure | Main builds |
PR #2945 |
Haskell build failure | debian-stretch-full-optimizations-off |
PR #2945 |
APT install failed | build-elektra-website |
PR #2932 |
Maven build | debian-unstable-clang-asan |
master |
Timeout | debian-stretch-full-mmap-asan |
PR #2975 |
Timeout | debian-buster-mingw-w64 |
master |
Homepage build | Deploy Website |
master |
Homepage build | Deploy Website |
master |
Timeout | debian-buster-full |
master |
Haskell build failure | debian-stretch-full-ini |
master |
Timeout | debian-unstable-full |
master |
Failing tests | debian-buster-full |
master |
Internal compiler error | build-elektra-web-base |
master |
Homepage build | Deploy Website |
master |
Homepage build | Deploy Website |
master |
Homepage build | Deploy Website |
master |
Homepage build | Deploy Website |
PR #2998 |
Timeout, Connection problems | build-elektra-web-base, debian-buster-full-i386 |
master |
Maven build | debian-unstable-clang-asan |
PR #2998 |
Timeout | build-elektra-website-backend |
master |
Connection problems | build-elektra-web-base |
master |
Homepage build | Deploy Website |
master |
Maven build | debian-unstable-full-clang |
master |
Git commit failure | buildPackage/debian/buster |
master |
Git commit failure | buildPackage/debian/buster |
master |
Git commit failure | buildPackage/debian/buster, buildPackage/debian/stretch |
master |
Git commit failure | buildPackage/debian/buster |
master |
Git commit failure | buildPackage/debian/buster |
Failing Tests
| Test | Location | Times Failed |
|---|---|---|
check_external_example_codegen_econf |
debian-buster-full |
1 |
check_external_example_codegen_menu |
debian-buster-full |
1 |
check_external_example_codegen_tree |
debian-buster-full |
1 |
check_external_example_highlevel |
debian-buster-full |
1 |
check_spec |
debian-buster-full |
1 |
testkdb_ensure |
debian-buster-full |
1 |
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 36 (36 by maintainers)
Commits related to this issue
- tests: run cmake twice might improve #2967 — committed to ElektraInitiative/libelektra by deleted user 5 years ago
- tests: run ctest twice might improve #2967 — committed to ElektraInitiative/libelektra by deleted user 5 years ago
- tests: run ctest twice might improve #2967 — committed to darddan/libelektra by deleted user 5 years ago
- tests: run ctest twice might improve #2967 — committed to darddan/libelektra by deleted user 5 years ago
It just
Disk quota exceeded, I did not want to overkill it with memory. I cleaned it up now. Its up again.I updated the Node, again, there shouldnt be any permission issues anymore.
Node updated.
I updated the node. It should work now. If something goes wrong you can update me here again.
The failures with
docker pullfailing in the website stage occurs quite often now.What do you think about #3224?
Trying to update the start post or trying to fix all these issues is hopeless. We need automatic retrying. I hope @Mistreated will implement this soon on our new server.
Yet another error in https://build.libelektra.org/jenkins/blue/organizations/jenkins/libelektra/detail/master/12/pipeline/
I am afraid https://wiki.jenkins.io/display/JENKINS/Naginator+Plugin is the only bigger step forwards.
Unfortunately, it will not fix the problems for Travis or Cirrus.
Two more tests that sometimes fail (#3168):
Looks like building Docker images does not work on
hetzner-jenkins1:. I disabled the node.
Build jobs on
hetzner-jenkins1seem to fail, because of permission related problems:.
Looks like
docker pullfails onhetzner-jenkins1, since the node has not enough free space:.
Thank you for adding the new Jenkins node. I disabled the node for now, since it seems to break the build.
I think our best guess to make our lives much easier is to “fix” these problems using https://wiki.jenkins.io/display/JENKINS/Naginator+Plugin
Then Jenkins will restart failed jobs several times. I think we could try 5 restarts before giving up?
@Mistreated Can you implement this also on the old server? Or is this too risky?
Before we implement this, however, we need the new Jenkins Node as otherwise the queue will get too long.
Done, see #3086
For issues related to source code I agree. For the issues related to docker/jenkins instability it is enough to collect issues here as it is very limited what we can do next to the migration we already do but unfortunately takes longer as expected. It would be nice if @Mistreated could give more information about the status, maybe in #160.
Nope. I already gave up on modifying the list, since the Jenkins build fails too often. I would recommend we just open an issue for each specific problem.
Yes, I agree test_service_convertengine is not reported here yet. Actually we can disable the test as the service is not modified anyway.
@sanssecours is there some procedure how to add new tests in the above list?
Is this all the retrying and waiting after
Pulling from build-elektra-web-base(log)?Additionally, I think this error is new:
test_service_convertenginefails duringStarting build/hub.libelektra.org/build-elektra-website-backend(log 2)I just got connection problems for build-elektra-web-base, too.
This is a full log.
For the Haskell problems we can remove the haskell bindings/plugins. They are not maintained anyway.
I know 😊. I already added a link in the issue description.