[PTHREADING] No build for ppc64le and s390x, text fail on x86_64
After adding Victor to jenkins whitelist, CI started to test https://gerrit.ovirt.org/#/c/94974/ But we have only x86_64 jobs. This kind of project must have jobs for all platforms. The last maintainer was Yaniv Bronhaim, so I guess nobody remember why we have only x86_64 builds. I hope someone can help to move the project to new stdci and add ppc64le and s390x builds. While I was writing this the build completed with this failure: 00:01:01.195 ========== Running the shellscript automation/check-patch.sh 00:01:01.204 ./automation/check-patch.sh: line 3: tox: command not found This worked when I added tox for fedora 25. Looks like we need a simple patch to get tox on el7/fc28. Nir
Il giorno mar 16 ott 2018 alle ore 23:43 Nir Soffer <nsoffer@redhat.com> ha scritto:
After adding Victor to jenkins whitelist, CI started to test https://gerrit.ovirt.org/#/c/94974/
But we have only x86_64 jobs. This kind of project must have jobs for all platforms.
The last maintainer was Yaniv Bronhaim, so I guess nobody remember why we have only x86_64 builds.
It was on x86_64 only because former maintainer treated this as a non-ovirt project but as an external project, Builds are delivered by downstream distribution: https://koji.fedoraproject.org/koji/buildinfo?buildID=1122696 Tests were manually done by former maintainer, not by Jenkins.
I hope someone can help to move the project to new stdci and add ppc64le and s390x builds.
Who's current maintainer? Is something changed in the policies previously set for this package of being an external project? Is current maintainer also packaging for Fedora / EPEL as former maintainer?
While I was writing this the build completed with this failure: 00:01:01.195 ========== Running the shellscript automation/check-patch.sh 00:01:01.204 ./automation/check-patch.sh: line 3: tox: command not found
This worked when I added tox for fedora 25. Looks like we need a simple patch to get tox on el7/fc28.
Nir _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IAT2KDTLFVVUOO...
-- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK>
On Wed, Oct 17, 2018 at 12:53 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mar 16 ott 2018 alle ore 23:43 Nir Soffer <nsoffer@redhat.com> ha scritto:
After adding Victor to jenkins whitelist, CI started to test https://gerrit.ovirt.org/#/c/94974/
But we have only x86_64 jobs. This kind of project must have jobs for all platforms.
The last maintainer was Yaniv Bronhaim, so I guess nobody remember why we have only x86_64 builds.
It was on x86_64 only because former maintainer treated this as a non-ovirt project but as an external project, Builds are delivered by downstream distribution: https://koji.fedoraproject.org/koji/buildinfo?buildID=1122696 Tests were manually done by former maintainer, not by Jenkins.
I hope someone can help to move the project to new stdci and add ppc64le and s390x builds.
Who's current maintainer?
Good question! I think since Yaniv left, there is no maintainer, but I hope that Marcin will work on it now.
Is something changed in the policies previously set for this package of being an external project? Is current maintainer also packaging for Fedora / EPEL as former maintainer?
I think we should handle this project like ioprocess, provides builds in ovirt repositories for upstream, and downstream builds using RHEL. Since vdsm is the only user of this project, and the project will be dropped once vdsm move to python 3, I don't see the need to maintain this in Fedora. Nir
While I was writing this the build completed with this failure:
00:01:01.195 ========== Running the shellscript automation/check-patch.sh 00:01:01.204 ./automation/check-patch.sh: line 3: tox: command not found
This worked when I added tox for fedora 25. Looks like we need a simple patch to get tox on el7/fc28.
Nir _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IAT2KDTLFVVUOO...
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK>
participants (2)
-
Nir Soffer -
Sandro Bonazzola