oVirt infra daily report - unstable production jobs - 90

2016-09-27 Thread jenkins 
Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/90//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


upstream_report.html
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : ovirt_master_system-tests #582

2016-09-27 Thread jenkins 
See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_master_system-tests #581

2016-09-27 Thread jenkins 
See 

Changes:

[Eyal Edri] remove index.rst file since all the page is using md format

[Gil Shinar] Removing old check patch for Jenkins repo

--
[...truncated 687 lines...]
##  took 1875 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1701 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson357015016227252924.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI

2016-09-27 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-723:

Summary: check/add support for python3 + dnf on standard CI  (was: otopi 
jobs using python3 fail on fedora 24)

> check/add support for python3 + dnf on standard CI
> --
>
> Key: OVIRT-723
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Hi,
> Patch [1] fails jenkins [2] like this:
> 11:35:21 [ INFO  ] DNF Repository updates-testing is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-testing-debuginfo is listed
> more than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-debuginfo is listed more
> than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora-debuginfo is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'fedora', 
> disabling.
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'updates',
> disabling.
> 11:35:21 [ INFO  ] Stage: Environment packages setup
> 11:35:21 [ INFO  ] DNF Repository updates-testing is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-testing-debuginfo is listed
> more than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-debuginfo is listed more
> than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora-debuginfo is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'fedora', 
> disabling.
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'updates',
> disabling.
> 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched
> 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages
> setup': no package matched
> I suspected, based on the log, that something is broken about dnf
> configuration, so pushed [3] and ran the job again [4] with [3]
> cherry-picked, and it succeeded. I thought that's enough for a
> verification, so asked to merge it, and it was merged. Later on, lago
> tests started breaking [5] with:
> 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by
> python-lago-ovirt-0.24.0-1.fc23.noarch
> So [3] was reverted [6], Currently pending, but I expect it to be merged soon.
> So we need a better solution.
> While investigating this, Nadav partially understood the issue - we have, at
> certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf.
> Not sure why and whether we need both.
> We tried also various variations on this patch in [7][8][9][10], none worked.
> Probably better to fully support dnf instead of this hack, not sure
> what this requires.
> Thanks,
> [1] https://gerrit.ovirt.org/59831
> [2] 
> http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console
> [3] https://gerrit.ovirt.org/63249
> [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/
> [5] 
> http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/console
> [6] https://gerrit.ovirt.org/63405
> [7] https://gerrit.ovirt.org/63386
> [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203
> [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/
> [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/
> -- 
> Didi



--
This message was sent by Atlassian JIRA
(v1000.375.1#100014)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Dropping rpm build from ovirt-engine check-merged.sh

2016-09-27 Thread Sandro Bonazzola 
On Tue, Sep 27, 2016 at 2:40 PM, Eyal Edri  wrote:

>
>
> On Mon, Sep 26, 2016 at 7:37 PM, Vojtech Szocs  wrote:
>
>> Hi,
>>
>> to me, it seems that with current CI flow, we can do following:
>>
>> - in build-artifacts.sh, build UI for English (only) & all supported
>>   browsers (IE10+, Firefox, Chrome), by using `ovirt_build_locales 0`
>>   as the default fallback
>>
>
> +1 from my side.
> Sandro - any objections or thoughts?
>

No objections provided that for release we can fix it.




>
>
>>
>>   Note: this will cut down the # of permutations from 3x9 to just 3
>>   (currently we have 3 supported browser types, 9 supported locales).
>>
>> - ensure that release builds still target all supported UI locales,
>>   by using `ovirt_build_locales 1` (override the default fallback)
>>
>
> You can make sure in the automation/ dir in the 'manual*' script has it.
>
>
>
>>
>> - it would be nice if the Jenkins job for build-artifacts.sh would
>>   set some `RELEASE=1` flag (or similar) when doing a release build
>>   (is this possible with current standard CI?)
>>
>
> In planning, what I want to do is to move the 'manual official' [1] to be
> automatic official builds,
> as for RELEASE flag, we'll need to discuss on changing how we manage
> ovirt-engine versioning, I think we talked about 4.1 or later to try to use
> mvn release plugin or
> an alternate way to avoid the manual patches for updating POM files.
>
>
>>
>> Eyal/others, does above make sense?
>>
>
> Yea, see my comments.
>
>
>>
>> Also, as Nir mentioned, if `ovirt-engine` repo was configured with
>> Submit Type == Fast Forward Only, we could drop RPM / GWT build in
>> check-merged.sh (which was Eyal's original suggestion).
>>
>
>
> Its currently on 'Rebase if necessary', if there is an agreement I can
> change it to 'Fast forward only'.
>

Fast forward only will require lot of manual rebase. That's the reason we
dropped it in the past


>
>
>>
>> Regards,
>> Vojtech
>>
>>
>> - Original Message -
>> > From: "Nir Soffer" 
>> > To: "Eyal Edri" 
>> > Cc: "Juan Hernandez" , "devel" ,
>> "Martin Perina" , "Tal
>> > Nisan" , "infra" 
>> > Sent: Tuesday, September 20, 2016 5:38:08 PM
>> > Subject: Re: Dropping rpm build from ovirt-engine check-merged.sh
>> >
>> > On Tue, Sep 20, 2016 at 11:27 AM, Eyal Edri < ee...@redhat.com > wrote:
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Sep 20, 2016 at 9:34 AM, Sandro Bonazzola < sbona...@redhat.com
>> >
>> > wrote:
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Sep 19, 2016 at 7:56 PM, Eyal Edri < ee...@redhat.com > wrote:
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Sep 19, 2016 at 9:41 AM, Sandro Bonazzola < sbona...@redhat.com
>> >
>> > wrote:
>> >
>> >
>> >
>> >
>> >
>> > On Sun, Sep 18, 2016 at 4:18 PM, Eyal Edri < ee...@redhat.com > wrote:
>> >
>> >
>> >
>> > Hi,
>> >
>> > Following [1] I'd like to propose to remove rpm building from the
>> > 'check-merged.sh' script from ovirt-engine (master for now).
>> >
>> > The job [2] takes on avg 15 min while actually the rpms are built
>> already in
>> > check-patch
>> > (with gwt draft mode if needed) and runs exactly the same build rpm
>> command
>> > as check-patch [3].
>> >
>> > So there isn't real value in running exactly the same rpm build post
>> merge,
>> > and we already build full permutation mode in 'build-artifacts.sh'.
>> >
>> > Any reason to keep it?
>> > We can cut down valuable time in CI if we drop it and vacant more time
>> for
>> > more meaningful tests.
>> >
>> >
>> > This depends on the flow: if we make check_merge gating to the merge
>> and to
>> > the build we should keep the rpm build becuase at merge a rebase is done
>> > automatically.
>> >
>> > What do you mean by 'gating to the merge'? I'm not sure I understand
>> what it
>> > means.
>> > Isn't check-patch.sh does the gating? check-merge runs post merge so its
>> > already too late to gate the code ...
>> > And I think check-merge and check-patch currently runs the same rpmbuild
>> > command, so I don't see how check-merged has any value over check-patch.
>> >
>> > when merge command is issued a rebase is done as well. We still need a
>> > check-merged job because the code checked by check-patch is not the same
>> > anymore when check-merged runs.
>> >
>> > OK, now I understand, so indeed check-merge can potentially run on
>> different
>> > code than check-patch and possibly fail due to it.
>> >
>> > If we require only fast-forward merges, there is no way to merge patch
>> > before a rebase. Once you rebase a patch, check-patch runs...
>> >
>> > So check-merge may be unneeded in this case.
>> >
>> >
>> >
>> >
>> >
>> >
>> > In original desing of stdci, check-merged was supposed to become a
>> gating
>> > test for build-artifacts.
>> >
>> > We have it in our backlog, i.e installing Zuul and adding gating for the
>> > check-merged jobs, its

[JIRA] (OVIRT-746) Build oVirt 4.0.5 RC1

2016-09-27 Thread sbonazzo (oVirt JIRA) 
sbonazzo created OVIRT-746:
--

 Summary: Build oVirt 4.0.5 RC1
 Key: OVIRT-746
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-746
 Project: oVirt - virtualization made easy
  Issue Type: Task
  Components: Repositories Mgmt
Reporter: sbonazzo
Assignee: infra
Priority: Highest






--
This message was sent by Atlassian JIRA
(v1000.375.1#100014)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-746) Build oVirt 4.0.5 RC1

2016-09-27 Thread sbonazzo (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sbonazzo updated OVIRT-746:
---
Assignee: sbonazzo  (was: infra)
  Status: In Progress  (was: To Do)

> Build oVirt 4.0.5 RC1
> -
>
> Key: OVIRT-746
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-746
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: sbonazzo
>Priority: Highest
>




--
This message was sent by Atlassian JIRA
(v1000.375.1#100014)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt 4.0.5 RC1 merge / branch / tag / bugzilla reminder

2016-09-27 Thread Sandro Bonazzola 
All stable branch maintainers, please make sure to

   - merge all relevant open bugs until Wednesday morning 11:00 AM TLV time.


For each package that need to be built (i.e oVirt product) please make sure
every bug in MODIFIED has the right Target Release and Target Milestone.
A Target release should state the version of the package you're building
and should include the same version you used for the tag you just used for
this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.5, tr: 4.0.5)
A list of bugs that require attention is here:

   -
   
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.5%20target_release%3A---%20status%3Amodified%2Cpost


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_master_system-tests #580

2016-09-27 Thread jenkins 
See 

Changes:

[Eyal Edri] remove index.rst file since all the page is using md format

--
[...truncated 746 lines...]
##  took 2321 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 2157 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson195048084277820550.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log

Re: fabric jobs in ci

2016-09-27 Thread Eyal Edri 
thanks, merged.

On Mon, Sep 26, 2016 at 6:26 PM, Barak Korren  wrote:

> This should fix it: https://gerrit.ovirt.org/#/c/64474/1
>
> On 26 September 2016 at 10:20, Eyal Edri  wrote:
> > Fabric has 2 jobs that are failing [1] for over a month, if no one has
> > objection i'll disable them for now since they are just adding noise to
> the
> > unstable jobs which should be 0 on normal state.
> >
> > I know we have some work in progress for fabric so it might not be ready,
> > so I suggest to add these jobs to a jira ticket that is tracking
> progress on
> > this task
> > and the owner will enable them once the fabric project will be stable.
> >
> >
> > [1]
> > http://jenkins.ovirt.org/job/fabric-ovirt_master_check-
> merged-el7-x86_64/
> >
> > --
> > Eyal Edri
> > Associate Manager
> > RHV DevOps
> > EMEA ENG Virtualization R
> > Red Hat Israel
> >
> > phone: +972-9-7692018
> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
>
>
>
> --
> Barak Korren
> bkor...@redhat.com
> RHEV-CI Team
>



-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Dropping rpm build from ovirt-engine check-merged.sh

2016-09-27 Thread Eyal Edri 
On Mon, Sep 26, 2016 at 7:37 PM, Vojtech Szocs  wrote:

> Hi,
>
> to me, it seems that with current CI flow, we can do following:
>
> - in build-artifacts.sh, build UI for English (only) & all supported
>   browsers (IE10+, Firefox, Chrome), by using `ovirt_build_locales 0`
>   as the default fallback
>

+1 from my side.
Sandro - any objections or thoughts?


>
>   Note: this will cut down the # of permutations from 3x9 to just 3
>   (currently we have 3 supported browser types, 9 supported locales).
>
> - ensure that release builds still target all supported UI locales,
>   by using `ovirt_build_locales 1` (override the default fallback)
>

You can make sure in the automation/ dir in the 'manual*' script has it.



>
> - it would be nice if the Jenkins job for build-artifacts.sh would
>   set some `RELEASE=1` flag (or similar) when doing a release build
>   (is this possible with current standard CI?)
>

In planning, what I want to do is to move the 'manual official' [1] to be
automatic official builds,
as for RELEASE flag, we'll need to discuss on changing how we manage
ovirt-engine versioning, I think we talked about 4.1 or later to try to use
mvn release plugin or
an alternate way to avoid the manual patches for updating POM files.


>
> Eyal/others, does above make sense?
>

Yea, see my comments.


>
> Also, as Nir mentioned, if `ovirt-engine` repo was configured with
> Submit Type == Fast Forward Only, we could drop RPM / GWT build in
> check-merged.sh (which was Eyal's original suggestion).
>


Its currently on 'Rebase if necessary', if there is an agreement I can
change it to 'Fast forward only'.


>
> Regards,
> Vojtech
>
>
> - Original Message -
> > From: "Nir Soffer" 
> > To: "Eyal Edri" 
> > Cc: "Juan Hernandez" , "devel" ,
> "Martin Perina" , "Tal
> > Nisan" , "infra" 
> > Sent: Tuesday, September 20, 2016 5:38:08 PM
> > Subject: Re: Dropping rpm build from ovirt-engine check-merged.sh
> >
> > On Tue, Sep 20, 2016 at 11:27 AM, Eyal Edri < ee...@redhat.com > wrote:
> >
> >
> >
> >
> >
> > On Tue, Sep 20, 2016 at 9:34 AM, Sandro Bonazzola < sbona...@redhat.com
> >
> > wrote:
> >
> >
> >
> >
> >
> > On Mon, Sep 19, 2016 at 7:56 PM, Eyal Edri < ee...@redhat.com > wrote:
> >
> >
> >
> >
> >
> > On Mon, Sep 19, 2016 at 9:41 AM, Sandro Bonazzola < sbona...@redhat.com
> >
> > wrote:
> >
> >
> >
> >
> >
> > On Sun, Sep 18, 2016 at 4:18 PM, Eyal Edri < ee...@redhat.com > wrote:
> >
> >
> >
> > Hi,
> >
> > Following [1] I'd like to propose to remove rpm building from the
> > 'check-merged.sh' script from ovirt-engine (master for now).
> >
> > The job [2] takes on avg 15 min while actually the rpms are built
> already in
> > check-patch
> > (with gwt draft mode if needed) and runs exactly the same build rpm
> command
> > as check-patch [3].
> >
> > So there isn't real value in running exactly the same rpm build post
> merge,
> > and we already build full permutation mode in 'build-artifacts.sh'.
> >
> > Any reason to keep it?
> > We can cut down valuable time in CI if we drop it and vacant more time
> for
> > more meaningful tests.
> >
> >
> > This depends on the flow: if we make check_merge gating to the merge and
> to
> > the build we should keep the rpm build becuase at merge a rebase is done
> > automatically.
> >
> > What do you mean by 'gating to the merge'? I'm not sure I understand
> what it
> > means.
> > Isn't check-patch.sh does the gating? check-merge runs post merge so its
> > already too late to gate the code ...
> > And I think check-merge and check-patch currently runs the same rpmbuild
> > command, so I don't see how check-merged has any value over check-patch.
> >
> > when merge command is issued a rebase is done as well. We still need a
> > check-merged job because the code checked by check-patch is not the same
> > anymore when check-merged runs.
> >
> > OK, now I understand, so indeed check-merge can potentially run on
> different
> > code than check-patch and possibly fail due to it.
> >
> > If we require only fast-forward merges, there is no way to merge patch
> > before a rebase. Once you rebase a patch, check-patch runs...
> >
> > So check-merge may be unneeded in this case.
> >
> >
> >
> >
> >
> >
> > In original desing of stdci, check-merged was supposed to become a gating
> > test for build-artifacts.
> >
> > We have it in our backlog, i.e installing Zuul and adding gating for the
> > check-merged jobs, its mostly relevant for system jobs, but we can
> defiently
> > do it first for simple 'check-merged.sh' jobs
> > as part of standard CI.
> >
> > Opened a ticket for it [1]
> >
> > [1] https://ovirt-jira.atlassian.net/browse/OVIRT-734
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > If there's not gating process performed by check-merge then I agree in
> > dropping rpm build.
> >
> >
> >
> >
> >
> >
> > [1]

Build failed in Jenkins: ovirt_master_system-tests #579

2016-09-27 Thread jenkins 
See 

Changes:

[Eyal Edri] remove index.rst file since all the page is using md format

--
[...truncated 687 lines...]
##  took 1867 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1690 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson8545034464753394785.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/root.log

Re: Permissions to run builds manually

2016-09-27 Thread Ala Hino 
Works now. Thanks!

On Tue, Sep 27, 2016 at 1:26 PM, Gil Shinar  wrote:

> Try now
>
> On Tue, Sep 27, 2016 at 1:20 PM, Ala Hino  wrote:
>
>> Hello,
>>
>> I created a user, ahino, in Jenkins but cannot run builds manually.
>> Can you please assign the appropriate permissions to me so I can trigger
>> builds manually?
>>
>> Thanks,
>> Ala
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Permissions to run builds manually

2016-09-27 Thread Gil Shinar 
Try now

On Tue, Sep 27, 2016 at 1:20 PM, Ala Hino  wrote:

> Hello,
>
> I created a user, ahino, in Jenkins but cannot run builds manually.
> Can you please assign the appropriate permissions to me so I can trigger
> builds manually?
>
> Thanks,
> Ala
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : ovirt_master_system-tests #578

2016-09-27 Thread jenkins 
See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_master_system-tests #577

2016-09-27 Thread jenkins 
See 

Changes:

[Yaniv Kaul] Fix Glance provider list test

--
[...truncated 683 lines...]
##  took 1822 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1661 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson2244514957989166457.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log