On Wed, Feb 1, 2017 at 7:23 PM, Matthew Miller wrote:
> I'm looking at https://apps.fedoraproject.org/autocloud/jobs/740, where
> there is a failure in the Fedora Cloud Base vagrant-libvirt image (yet
> vagrant-virtualbox and others are fine).
>
> The specific failure
On Thu, Feb 2, 2017 at 8:06 PM, Matthew Miller
wrote:
> Yeah, but... how could that go wrong in this way?
Here is the test for the above failure [0].
I'm going to debug this tomorrow and try to figure out what is going wrong.
[0]
On Thu, Feb 02, 2017 at 06:44:14PM +0530, Kushal Das wrote:
> > I'm looking at https://apps.fedoraproject.org/autocloud/jobs/740, where
> > there is a failure in the Fedora Cloud Base vagrant-libvirt image (yet
> > vagrant-virtualbox and others are fine).
> It was a non-gating test about auditd,
On 01/02/17, Matthew Miller wrote:
> I'm looking at https://apps.fedoraproject.org/autocloud/jobs/740, where
> there is a failure in the Fedora Cloud Base vagrant-libvirt image (yet
> vagrant-virtualbox and others are fine).
It was a non-gating test about auditd, which got automatically fixed. We
I'm looking at https://apps.fedoraproject.org/autocloud/jobs/740, where
there is a failure in the Fedora Cloud Base vagrant-libvirt image (yet
vagrant-virtualbox and others are fine).
The specific failure (with whitespace removed) from
https://apps.fedoraproject.org/autocloud/jobs/1984/output