Yes, i want s.th. called cache_failed_builds.

This would safe build time, if the reason for the failure is in the sources.

Maybe an additional option, to reset the failed builds might be interesting, in case the failure lies in the dependencies to installed packages and not in the sources.

Maybe this whole thing is too complicated and confuses more users than it helps ;-)

M.

Hi,

there's some inconsistency in the documentation and behaviour.

[from the default config file]:
features = {
# If the cache is enabled, then modules will only be built if their
# sources have changed since the previous build cycle. This provides
# much faster cycle times if there are many modules in the build
# config, only a few of which ever change
cache = 1

However, I do have a couple of failing packages, which are being rebuilt although caching is enabled. This is a bit annoying, as it takes up to 3h until the error is reached.

However, this autobuild behaviour is reasonable in some cases. I.e. when build fails due to a dependency. In that case I would want to trigger a rebuild of the failed packages without changing the sources.

Now: Is the above problem supported?

Many thanks!
M.