Re: Bad pep8 on slave?

El lun 17 feb 2014 23:47:58 CET, Nir Soffer escribió: Hi infra, Note this strange failure of pep8: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/6390/ While the pep8 job succeeds: http://jenkins.ovirt.org/job/vdsm_master_pep8_gerrit/7174/ Can you check why this happens? What is

Re: Bad pep8 on slave?

On Mon, Feb 17, 2014 at 05:47:58PM -0500, Nir Soffer wrote: Hi infra, Note this strange failure of pep8: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/6390/ The following failure should have been hacked by http://gerrit.ovirt.org/24602 . Could you rebase your code? /usr/bin/pep8

Build failed in Jenkins: publish_ovirt_rpms_nightly_3.4 #1

See http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.4/1/ -- Started by user Kiril Nesenko Building on master in workspace http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.4/ws/ [publish_ovirt_rpms_nightly_3.4] $ /bin/sh -xe

Re: eninge-cleanup left db non-empty (was: [Users] Downgrading to 3.3.3 after 3.4.0 beta 2 testing)

Submitted against 3.3.3, https://bugzilla.redhat.com/show_bug.cgi?id=1066654 I am in process of installing 3.4.0-betaN to see if this only effects 3.3.3. - Trey On Sun, Feb 16, 2014 at 5:01 AM, Yedidyah Bar David d...@redhat.com wrote: - Original Message - From: Trey Dockendorf

Build failed in Jenkins: publish_ovirt_rpms_nightly_3.3 #26

See http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.3/26/ -- Started by timer Building on master in workspace http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.3/ws/ [publish_ovirt_rpms_nightly_3.3] $ /bin/sh -xe

Build failed in Jenkins: publish_ovirt_rpms_nightly #684

See http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/684/ -- Started by timer Building remotely on jenkins-slave-host04.ovirt.org in workspace http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/ [publish_ovirt_rpms_nightly] $ /bin/sh -xe

Re: [Users] eninge-cleanup left db non-empty (was: Downgrading to 3.3.3 after 3.4.0 beta 2 testing)

I just tried same steps with 3.4.0-beta2 and got same results. Performed full 'engine-cleanup' and a engine-backup --mode=restore failed with FATAL: Database is not empty $ su - postgres -c pg_dump engine | grep -i ^create CREATE PROCEDURAL LANGUAGE plpgsql; After the failed restore the

[oVirt Jenkins] ovirt_engine_upgrade_params - Build # 107 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/ Build: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/107/ Build Number: 107 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Success:

Jenkins build is back to normal : publish_ovirt_rpms_nightly_3.3 #27

See http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.3/27/ ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra