On Wed, 04 Jan 2017 13:58:38 +0100
Pavel Raiskup wrote:
> On Wednesday, January 4, 2017 12:06:40 PM CET Pavel Raiskup wrote:
> > On Monday, January 2, 2017 3:47:52 PM CET Pavel Raiskup wrote:
> > > On Monday, January 2, 2017 2:40:34 PM CET Pavel Raiskup wrote:
> > > > Also, the question is whethe
On Wednesday, January 4, 2017 12:06:40 PM CET Pavel Raiskup wrote:
> On Monday, January 2, 2017 3:47:52 PM CET Pavel Raiskup wrote:
> > On Monday, January 2, 2017 2:40:34 PM CET Pavel Raiskup wrote:
> > > Also, the question is whether it isn't really glibc bug, because
> > > schedulers non-ppc64le
On Monday, January 2, 2017 3:47:52 PM CET Pavel Raiskup wrote:
> On Monday, January 2, 2017 2:40:34 PM CET Pavel Raiskup wrote:
> > Also, the question is whether it isn't really glibc bug, because
> > schedulers non-ppc64le architectures look to be more "fair" regardless
> > the default.
>
> Sorry
Dne 2.1.2017 v 11:24 Miroslav Suchý napsal(a):
> Hmm, that is nice idea. Plugin for Mock which will print:
> * number of CPU
> * RAM + swap
> * storage size available
>
> I will try to work on that.
Done. You can expect it in next version of Mock:
https://github.com/rpm-software-management/mo
On Monday, January 2, 2017 2:40:34 PM CET Pavel Raiskup wrote:
> Also, the question is whether it isn't really glibc bug, because
> schedulers non-ppc64le architectures look to be more "fair" regardless
> the default.
Sorry, not really -- at least i686 (build cross-compiled from x86_64
probably) i
On Monday, January 2, 2017 11:24:35 AM CET Miroslav Suchý wrote:
> Dne 20.12.2016 v 16:03 Pavel Raiskup napsal(a):
> > The only thing I was able to find is version of mock in the log output.
>
> Hmm, that is nice idea. Plugin for Mock which will print:
> * number of CPU
> * RAM + swap
> * stora
On Monday, January 2, 2017 11:00:44 AM CET Kamil Dudka wrote:
> > Note this test was just changed upstream to use locks instead of volatiles,
> > which significantly improved performance on a 40 core NUMA system at least:
> > http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=480d374
>
Dne 20.12.2016 v 16:03 Pavel Raiskup napsal(a):
> The only thing I was able to find is version of mock in the log output.
Hmm, that is nice idea. Plugin for Mock which will print:
* number of CPU
* RAM + swap
* storage size available
I will try to work on that.
--
Miroslav Suchy, RHCA
Red Ha
On Sunday, December 25, 2016 13:13:31 Pádraig Brady wrote:
> On 22/12/16 13:13, Pádraig Brady wrote:
> > On 21/12/16 16:04, Dan Horák wrote:
> >> On Tue, 20 Dec 2016 16:03:49 +0100
> >>
> >> Pavel Raiskup wrote:
> >>> Hi all,
> >>>
> >>> where is documented what system/hw is used on (primary) Ko
On 22/12/16 13:13, Pádraig Brady wrote:
> On 21/12/16 16:04, Dan Horák wrote:
>> On Tue, 20 Dec 2016 16:03:49 +0100
>> Pavel Raiskup wrote:
>>
>>> Hi all,
>>>
>>> where is documented what system/hw is used on (primary) Koji builders?
>>> I'm interested in memory, storage, filesystem, host operatin
On 21/12/16 16:04, Dan Horák wrote:
> On Tue, 20 Dec 2016 16:03:49 +0100
> Pavel Raiskup wrote:
>
>> Hi all,
>>
>> where is documented what system/hw is used on (primary) Koji builders?
>> I'm interested in memory, storage, filesystem, host operating system,
>> guest operating system (if those ar
On Tue, 20 Dec 2016 16:03:49 +0100
Pavel Raiskup wrote:
> Hi all,
>
> where is documented what system/hw is used on (primary) Koji builders?
> I'm interested in memory, storage, filesystem, host operating system,
> guest operating system (if those are VMs), etc.
>
> The only thing I was able to
On Tue, 20 Dec 2016 16:03:49 +0100
Pavel Raiskup wrote:
> Hi all,
>
> where is documented what system/hw is used on (primary) Koji builders?
> I'm interested in memory, storage, filesystem, host operating system,
> guest operating system (if those are VMs), etc.
>
> The only thing I was able to
Hi all,
where is documented what system/hw is used on (primary) Koji builders?
I'm interested in memory, storage, filesystem, host operating system, guest
operating system (if those are VMs), etc.
The only thing I was able to find is version of mock in the log output.
FWIW, I'd like to reproduce
14 matches
Mail list logo