New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes. #6495
Comments
jow-: Not sure what to make out of this ticket. Do you have any specific examples I can investigate? I need at least some pointers to correlate things... |
bluewavenet: A long story, so I will try to keep it short. I might be misunderstanding how this all works, but it seems to me to be a package will fail to build if a dependency has also failed, which seems reasonable, but this seems to be leading to the build system chasing its tail, or somehow there was a "storm of errors". My past experience in IT support made me imagine maintainers tearing their hair out trying to fix something causing this, hence my initial sketchy ticket details. If I am doing something wrong, or there is something wrong with the package, then I can look in depth there, but the same pattern seems to appear in the faillogs for other packages... |
bluewavenet: See also: |
jow-: The travis build job is totally unrelated to the snapshot mirrors though, it uses the SDK to build the package and all its dependencies locally. It does not utilize the opkg repositories at all. |
bluewavenet: I guessed that, but the errors seemed to be the same or similar, although both change without the code changing. |
jow-: I can understand that... will see if I can take a deeper look at it later. Note that the travis integration is not directly administered by OpenWrt/LEDE, it is local to the Github package repository. The toplevel travis scripts in the repo should probably get adjusted to actually show the compile logs (or to build the package with V=s in the first place). |
bluewavenet: Much appreciated, along with all your other efforts! |
bluewavenet: The 25th of April seems to be a common date. I thought package version jumps did not push into the stable release but stayed only available in snapshots, or have I got that wrong? |
bluewavenet:
Snapshot/Packages
Occurs on all architectures apparently at random with faillogs.
After next build some that failed will be ok and some that previously built will fail.
eg submit a PR on https://github.com/openwrt/packages
Travis shows fail on dependencies. After next automated build, Travis errors will be different, or if lucky will pass, only to fail again after the next build.
It seems the build system is chasing its tail somehow.
The text was updated successfully, but these errors were encountered: