Packages randomly failing - hardware issue? #228
Reference in New Issue
Block a user
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?
I've seen some packages failing randomly:
https://alhp.dev/logs/x86-64-v4/clang.log - file validity failed (v2 and v3 built correctly)
https://alhp.dev/logs/x86-64-v4/gtk3.log - download failed (v2 and v3 built correctly)
https://alhp.dev/logs/x86-64-v4/polkit.log - built failed early (v2 and v3 built correctly)
https://alhp.dev/logs/x86-64-v4/sane.log - built failed early (v2 and v3 built correctly)
https://alhp.dev/logs/x86-64-v3/lib32-nss.log (v2 and v4 built correctly)
https://alhp.dev/logs/x86-64-v4/nss.log (v2 and v3 built correctly)
https://alhp.dev/logs/x86-64-v4/jpegexiforient.log (v2 and v3 built correctly)
It's just some packages that I have remembered, there were some more which I can't remember. At least some of the failures look like there could be some issue with memory, the drive or the internet connection on the build host. Validity checks failing for 1 out of 3 builds, downloads that can not be finished and files that can not be found in 1 out of 3 builds looks not like an issue with the build itself to me but more like some sort of corruption happening.
The packages you have listed are most likely related to network issues (maybe except
clang). The build server is on a consumer connection, so some issues are expected due to the poor quality of the connection. Although I have implemented some checks to catch these issues, they are not foolproof.As far as I know, there are no hardware problems.