Great, I was actually going to do that myself in a couple of hours :)
I meant to yesterday but didn't get to it.

I'll take a peek at the cpp job, but will almost certainly need to
pass it to others with more of a clue about those tests.

Robbie

On 7 July 2016 at 12:19, Oleksandr Rudyy <[email protected]> wrote:
> Hi all,
>
> I updated configurations for jobs "Qpid-cpp-trunk-test" and
> "Qpid-Java-Cpp-Test" to get sources from new git repos.
> Lorenz did the same for job "Qpid-Python-Java-Test".
>
> The jobs are running and building.
>
> However,  the failed tests on job "Qpid-cpp-trunk-test" do not mark the job
> as failed. It seems that the same failed tests did not mark the job as
> failed previously before my change.
> I did not look into this problem.
>
> Kind Regards,
> Alex
>
> [1] https://builds.apache.org/view/M-R/view/Qpid
>
>
> On 5 July 2016 at 23:04, Robbie Gemmell <[email protected]> wrote:
>
>> The migration to the new git repositories have now been performed:
>> https://git-wip-us.apache.org/repos/asf/qpid-cpp.git
>> https://git-wip-us.apache.org/repos/asf/qpid-python.git
>>
>> Some additional tasks still need completed now that the migration has
>> been done. See the JIRAs for further details:
>> https://issues.apache.org/jira/browse/INFRA-11794
>> https://issues.apache.org/jira/browse/INFRA-11795
>>
>> I have deleted the cpp and python subdirs of svn trunk to prevent
>> continued use.
>>
>> I have disabled the following Jenkins Jobs for now, their config still
>> needs updated to reflect the changes:
>> Qpid-cpp-trunk-test
>> Qpid-Java-Cpp-Test
>> Qpid-Python-Java-Test
>>
>> I also realised that the .gitignore details in the old repo was in the
>> parent dir, so each of the new repos will need their own added giving
>> similar effect.
>>
>> Robbie
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to