maas-devel team mailing list archive
-
maas-devel team
-
Mailing list archive
-
Message #00591
Re: Jenkins Still Failing - maas-trunk 831
-
To:
maas-devel@xxxxxxxxxxxxxxxxxxx
-
From:
Julian Edwards <julian.edwards@xxxxxxxxxxxxx>
-
Date:
Mon, 24 Sep 2012 14:27:01 +1000
-
In-reply-to:
<317360053.1048.1348406007373.JavaMail.jenkins@jiufeng>
-
Organization:
Canonical Ltd
-
User-agent:
KMail/4.9.1 (Linux/3.5.0-15-generic; KDE/4.9.1; x86_64; ; )
On Sunday 23 September 2012 13:13:27 Jenkins Notification wrote:
> maas-trunk - Build # 831 - Still Failing:
>
> Public Jenkins URL: https://jenkins.qa.ubuntu.com/job/maas-trunk/831 to
> view the results.
>
> Private Jenkins URL: http://10.189.74.2:8080/job/maas-trunk/831
I think this is because it's using the buildout Piston instead of the system
package.
Gavin has a branch that fixes this:
lp:~allenap/maas/prod-deps-not-in-buildout
and it tests fine locally for me. I will land it now but it won't make any
difference until someone runs "make install-dependencies" on the jenkins box.
Hey, Diogo! :)
J
References