Hmm,
seems to be about mocking out an object that it hard fetched not from mock
context or so.
What might be interesting for CI in general is that I can reproduce with:
"nosetests tests/unittests" (as called by jenkins), while "make check" runs
just fine.
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
On Thu, Jul 21, 2016 at 11:16 AM, Christian Ehrhardt <
<email address hidden>> wrote:
Hmm,
seems to be about mocking out an object that it hard fetched not from mock
context or so.
What might be interesting for CI in general is that I can reproduce with:
"nosetests tests/unittests" (as called by jenkins), while "make check" runs
just fine.
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
On Thu, Jul 21, 2016 at 11:16 AM, Christian Ehrhardt <
<email address hidden>> wrote:
> That seems to be stuff that only triggers in an environment even more integration /server- team-jenkins. canonical. com/job/ curtin- ci/318/ /server- team-jenkins. canonical. com/job/ generic- update- mp/332/ console /server- team-jenkins. canonical. com/job/ curtin- ci/318/ rebuild /code.launchpad .net/~paelzer/ curtin/ bug-1574113- derived- repositories/ +merge/ 296118
> restricted than I have tested on horse.
> I'll try to fix and push over the day, ...
>
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd
>
> On Wed, Jul 20, 2016 at 8:08 PM, Server Team CI bot <
> <email address hidden>> wrote:
>
>> Review: Needs Fixing continuous-
>>
>> FAILED: Continuous integration, rev:576
>> https:/
>> Executed test runs:
>> None:
>> https:/
>>
>> Click here to trigger a rebuild:
>> https:/
>>
>> --
>>
>> https:/
>> You are the owner of lp:~paelzer/curtin/bug-1574113-derived-repositories.
>>
>
>