On 7 December 2016 at 14:15, Nir Soffer wrote:
>
> Last week it was 19-20 mintues, great improvement!
>
there are a couple of other things we might try soon, that will,
perhaps, help us shave off another 2-3 minutes...
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi,
On 7 December 2016 at 14:15, Nir Soffer wrote:
> On Mon, Dec 5, 2016 at 10:11 AM, Barak Korren wrote:
>> On 5 December 2016 at 10:07, Nir Soffer wrote:
>>>
>>> 20 seconds setup sounds great.
>>>
>>> Can we try the patches with vdsm
On Mon, Dec 5, 2016 at 10:11 AM, Barak Korren wrote:
> On 5 December 2016 at 10:07, Nir Soffer wrote:
>>
>> 20 seconds setup sounds great.
>>
>> Can we try the patches with vdsm builds?
>
> We'll probably merge today, if not, I'll manually cherry-pick this
On Mon, Dec 5, 2016 at 12:48 PM, Yaniv Kaul wrote:
>
>
> On Mon, Dec 5, 2016 at 9:59 AM, Barak Korren wrote:
>>
>> > Here are builds that do not change the build system:
>> > -
>> >
On Mon, Dec 5, 2016 at 9:59 AM, Barak Korren wrote:
> > Here are builds that do not change the build system:
> > - http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> x86_64/5767/console:
> > 10:07
> > - http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-
>
On 5 December 2016 at 10:07, Nir Soffer wrote:
>
> 20 seconds setup sounds great.
>
> Can we try the patches with vdsm builds?
We'll probably merge today, if not, I'll manually cherry-pick this for
the vdsm jobs.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps
On Mon, Dec 5, 2016 at 9:59 AM, Barak Korren wrote:
>> Here are builds that do not change the build system:
>> -
>> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5767/console:
>> 10:07
>> -
>>
> Here are builds that do not change the build system:
> -
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5767/console:
> 10:07
> -
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/4157/console:
> 10:16
>
> So we about 2X times faster now.
Awesome! also for
On Sun, Dec 4, 2016 at 11:56 PM, Nir Soffer wrote:
> On Sun, Dec 4, 2016 at 1:35 PM, Barak Korren wrote:
>>> To debug this we need to get a shell on a jenkins slave with the exact
>>> environment of
>>> a running job.
>>
>> Perhaps try to check if this
On Sun, Dec 4, 2016 at 1:35 PM, Barak Korren wrote:
>> To debug this we need to get a shell on a jenkins slave with the exact
>> environment of
>> a running job.
>
> Perhaps try to check if this reproduces with mock_runner.sh.
>
> You can try running with with something like:
> To debug this we need to get a shell on a jenkins slave with the exact
> environment of
> a running job.
Perhaps try to check if this reproduces with mock_runner.sh.
You can try running with with something like:
JENKINS=
cd
$JENKINS/mock_configs/mock_runner.sh --patch-only \
On Sun, Dec 4, 2016 at 9:59 AM, Barak Korren wrote:
> On 3 December 2016 at 21:36, Nir Soffer wrote:
>> HI all,
>>
>> Watching vdsm travis builds in the last weeks, it is clear that vdsm tests
>> on travis are about 4X times faster compared with jenkins
On 3 December 2016 at 21:36, Nir Soffer wrote:
> HI all,
>
> Watching vdsm travis builds in the last weeks, it is clear that vdsm tests
> on travis are about 4X times faster compared with jenkins builds.
>
> Here is a typical build:
>
> ovirt ci:
>
13 matches
Mail list logo