On Sat, Feb 18, 2017 at 11:36 PM, Kevin Fenzi wrote:
> On Sat, 18 Feb 2017 22:30:08 +0800
> Kalpa Welivitigoda wrote:
>
> > A scratch build failed for me,
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=17934589
> >
> > This was only a couple of
On Sat, 18 Feb 2017 22:30:08 +0800
Kalpa Welivitigoda wrote:
> A scratch build failed for me,
> https://koji.fedoraproject.org/koji/taskinfo?taskID=17934589
>
> This was only a couple of minutes ago.
But your build failure wasn't anything to do with this threads build
A scratch build failed for me,
https://koji.fedoraproject.org/koji/taskinfo?taskID=17934589
This was only a couple of minutes ago.
On Mon, Jan 23, 2017 at 5:15 PM, Peter Robinson
wrote:
> On Mon, Jan 23, 2017 at 8:30 AM, Dave Young wrote:
> > On
On Mon, Jan 23, 2017 at 8:30 AM, Dave Young wrote:
> On 01/19/17 at 10:24pm, Kevin Fenzi wrote:
>> ok. After a bunch of debugging and digging today it sure looks like the
>> underlying problem was squid operating in smp mode.
>>
>> We switched the squid servers back to non smp
On 01/19/17 at 10:24pm, Kevin Fenzi wrote:
> ok. After a bunch of debugging and digging today it sure looks like the
> underlying problem was squid operating in smp mode.
>
> We switched the squid servers back to non smp mode around 00:00 and I've
> not seen any of these failures since then.
>
On Fri, 20 Jan 2017 10:22:01 -0700
Orion Poplawski wrote:
> On 01/16/2017 09:16 AM, Kevin Fenzi wrote:
> >
> > Yes, there's been ongoing issues since last week:
> >
> > * This issue (which seems new in the last few days) where srpm isn't
> > unpacking correctly.
> >
On 01/16/2017 09:16 AM, Kevin Fenzi wrote:
>
> Yes, there's been ongoing issues since last week:
>
> * This issue (which seems new in the last few days) where srpm isn't
> unpacking correctly.
> https://pagure.io/fedora-infrastructure/issue/5694
Still seeing this:
ok. After a bunch of debugging and digging today it sure looks like the
underlying problem was squid operating in smp mode.
We switched the squid servers back to non smp mode around 00:00 and I've
not seen any of these failures since then.
I sure hope everything is back to normal now.
kevin
On 01/19/2017 06:55 PM, Kevin Fenzi wrote:
Please post links to the top level task.
My case:
https://koji.fedoraproject.org/koji/taskinfo?taskID=17327268
https://kojipkgs.fedoraproject.org//work/tasks/7272/17327272/mock_output.log
Approx. at the same time the i686 raised the error above, the
On Thu, 19 Jan 2017 17:37:23 +
"Daniel P. Berrange" wrote:
> I'm still seeing quite alot of problems today - randomly the arm7 or
> ppc task will just sit there in "open" status doing nothing for hours.
> If I cancel & rerun the build it works fine, presumably because it
On 01/19/2017 06:37 PM, Daniel P. Berrange wrote:
Now I've just seen some builds which succeeded in the build phase
get marked as failed because mock throws an exception handling the
results
https://kojipkgs.fedoraproject.org//work/tasks/1011/17331011/mock_output.log
Finish: run
ERROR: list
On Wed, Jan 18, 2017 at 11:55:38AM -0700, Kevin Fenzi wrote:
> On Wed, 18 Jan 2017 07:22:49 -0500 (EST)
> Charalampos Stratakis wrote:
>
> > Python 3 started failing on i686, x86_64 and arm only.
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=17313924
> >
> >
- Original Message -
From: "Kevin Fenzi" <ke...@scrye.com>
To: devel@lists.fedoraproject.org
Sent: Wednesday, January 18, 2017 7:55:38 PM
Subject: Re: Is there something wrong with the Koji builders?
On Wed, 18 Jan 2017 07:22:49 -0500 (EST)
Charalampos Stratakis <cstra...@redhat.com&
On 01/18/2017 07:55 PM, Kevin Fenzi wrote:
If you see any further issues like the above, let me know.
https://koji.fedoraproject.org/koji/taskinfo?taskID=17327268
seems to hang on arm7vhl and i386.
The x86_64 built finished ca. 45 minutes after the built was started.
However, I can not spot
On Wed, 18 Jan 2017 07:22:49 -0500 (EST)
Charalampos Stratakis wrote:
> Python 3 started failing on i686, x86_64 and arm only.
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=17313924
>
> The failures come from the test_socket.py [0], test_aead_aes_gcm [1]
> and
://bugs.python.org/issue27744
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
- Original Message -
From: "Kevin Fenzi" <ke...@scrye.com>
To: devel@lists.fedoraproject.org
Sent: Monday, January 16, 2017 5:16:40 PM
Subject: Re: Is there
On 01/16/2017 05:16 PM, Kevin Fenzi wrote:
I guess my monday is all mapped out for me. ;)
will keep the above bugs posted and report back here when I figure
anything out. ;(
And I have another case for you:
Buildroots fail to find/download packages:
From
On Mon, 16 Jan 2017 09:38:25 -0500 (EST)
Jaroslav Skarvada wrote:
> - Original Message -
> > I've done two builds for rawhide this morning.
> >
> > On the first the armv7hl and ppc64le builds failed because the
> > source tar file could not be unpacked.
> >
> > On
- Original Message -
> I've done two builds for rawhide this morning.
>
> On the first the armv7hl and ppc64le builds failed because the source
> tar file could not be unpacked.
>
> On the second the aarch64 build failed because the source tar file could
> not be unpacked.
>
> All the
I've done two builds for rawhide this morning.
On the first the armv7hl and ppc64le builds failed because the source
tar file could not be unpacked.
On the second the aarch64 build failed because the source tar file could
not be unpacked.
All the other arches built successfully.
--
Kaleb
20 matches
Mail list logo