On 30 May 2016 at 09:24, Martin Perina <email@example.com> wrote:
> I'm missing something here, how can it fail on engine build when both build
> jobs for the patch were successful?
The upgrade jobs use a different build process then the other jobs,
mock and the rest of the stuff in the automation dir is not used.
This is a result of the jobs being old-style rather then standard-ci.
Also forwarded the errors to Sandro and others with hopes they can say
what is missing for the build to succeed. The same jobs runs ok on 4.0
and 3.6 atm.
(Long term the upgrade checking logic should probably be combined into