On Thu, Aug 18, 2016 at 6:03 PM, Sandro Bonazzola <[email protected]> wrote:
> > > On Thu, Aug 18, 2016 at 4:16 PM, Nir Soffer <[email protected]> wrote: > >> Merged, so I sent this to enable the ppc builds again: >> https://gerrit.ovirt.org/62551 >> >> Someone with access to jenkins should verify that this jobs works now. >> >> > > will check tomorrow morning > Looks ok to me > > >> >> >> On Thu, Aug 18, 2016 at 10:03 AM, Sandro Bonazzola <[email protected]> >> wrote: >> > >> > >> > On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer <[email protected]> wrote: >> >> >> >> I posted this patch, changing python-ioprocess to require >> >> ioprocess-version (instead of version-release). This seem to resolve >> >> the issue and is more correct, we don't really need ioprocess from the >> >> same build. >> >> >> >> Please review >> >> https://gerrit.ovirt.org/62464 >> > >> > >> > +1 >> > >> > >> >> >> >> >> >> >> >> Nir >> >> >> >> On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer <[email protected]> >> wrote: >> >> > בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" >> >> > <[email protected]> >> >> > כתב: >> >> >> >> >> >> The issue is different: >> >> >> both x86_64 and ppc64le builds python-ioprocess package so a newer >> >> >> python-ioprocess may come from ppc64le build not corresponding to an >> >> >> exact >> >> >> nvr on x86_64. >> >> >> Solution may be to chance the ioprocess build to drop the timestamp >> or >> >> >> make the ioprocess build a matrix job building from the same >> src.rpm. >> >> >> Another solution may be relax the nvr requirements in the >> >> >> python-ioprocess >> >> >> package to not require the exact nvr but only the same version. >> >> >> Another solution may be competely separate x86_64 and ppc64le repos. >> >> > >> >> > I think the issue is the requiring the a version with the timestamp >> and >> >> > git >> >> > commit, it sould only require the same version. >> >> > >> >> > >> >> >> >> >> >> >> >> >> >> >> >> On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <[email protected]> >> wrote: >> >> >>> >> >> >>> Was the broken build replaced by new one that is working? >> >> >>> >> >> >>> On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <[email protected]> >> >> >>> wrote: >> >> >>>> >> >> >>>> Hi all, >> >> >>>> >> >> >>>> There was a broken build of ioprocess in ovirt repos, causing vdsm >> >> >>>> all >> >> >>>> vdsm master builds to fail with this error: >> >> >>>> >> >> >>>> ERROR: Command failed. See logs for output. >> >> >>>> >> >> >>>> If you have failed builds, please retrigger them in jenkins: >> >> >>>> http://jenkins.ovirt.org/gerrit_manual_trigger/ >> >> >>>> >> >> >>>> Nir >> >> >>>> _______________________________________________ >> >> >>>> Devel mailing list >> >> >>>> [email protected] >> >> >>>> http://lists.ovirt.org/mailman/listinfo/devel >> >> >>>> >> >> >>>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> -- >> >> >>> Eyal Edri >> >> >>> Associate Manager >> >> >>> RHV DevOps >> >> >>> EMEA ENG Virtualization R&D >> >> >>> Red Hat Israel >> >> >>> >> >> >>> phone: +972-9-7692018 >> >> >>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> >> >>> >> >> >>> _______________________________________________ >> >> >>> Devel mailing list >> >> >>> [email protected] >> >> >>> http://lists.ovirt.org/mailman/listinfo/devel >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Sandro Bonazzola >> >> >> Better technology. Faster innovation. Powered by community >> >> >> collaboration. >> >> >> See how it works at redhat.com >> > >> > >> > >> > >> > -- >> > Sandro Bonazzola >> > Better technology. Faster innovation. Powered by community >> collaboration. >> > See how it works at redhat.com >> > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
