On 29. 01. 21 16:26, Daniel P. Berrangé wrote:
Is there a good way to detect that the build is in an emulated copr
env rather than native. Does Copr / mock set any env variable to
show that you're emulated ?
I've talked to Pavel Raiskup on IRC about this.
Copr uses mock's --forcearch option to
On 31. 01. 21 16:44, Pavel Raiskup wrote:
There can be a macro that you would use like this:
--timeout %{adjust_timeout 3600}
Currently the environment (the copr-rpmbuild wrapper script) guards that mock
doesn't run longer than expected (it is not a mock built-in timeout).
Not saying it
On 01. 02. 21 10:53, Pavel Raiskup wrote:
On Monday, February 1, 2021 10:32:04 AM CET Daniel P. Berrangé wrote:
On Sun, Jan 31, 2021 at 03:35:14PM +0100, Pavel Raiskup wrote:
On Friday, January 29, 2021 4:26:18 PM CET Daniel P. Berrangé wrote:
When we attempt to build libvirt in Copr, the test
On Monday, February 1, 2021 10:32:04 AM CET Daniel P. Berrangé wrote:
> On Sun, Jan 31, 2021 at 03:35:14PM +0100, Pavel Raiskup wrote:
> > On Friday, January 29, 2021 4:26:18 PM CET Daniel P. Berrangé wrote:
> > > When we attempt to build libvirt in Copr, the test suite times out on
> > > s390 buil
On Sun, Jan 31, 2021 at 03:35:14PM +0100, Pavel Raiskup wrote:
> On Friday, January 29, 2021 4:26:18 PM CET Daniel P. Berrangé wrote:
> > When we attempt to build libvirt in Copr, the test suite times out on
> > s390 builds.
> >
> > IIUC, this is because s390 in Copr is using a QEMU emulated syste
On Sunday, January 31, 2021 4:17:04 PM CET Miro Hrončok wrote:
> On 31. 01. 21 15:35, Pavel Raiskup wrote:
> > I don't know, perhaps we could have some configurable coefficient for
> > timeout_in Copr_ for emulated architectures? If that was say "3", and
> > the --timeout was 3600s, emulated arch
On 31. 01. 21 15:35, Pavel Raiskup wrote:
I don't know, perhaps we could have some configurable coefficient for
timeout_in Copr_ for emulated architectures? If that was say "3", and
the --timeout was 3600s, emulated arches would get 10800s instead?
There can be a macro that you would use lik
On Friday, January 29, 2021 4:26:18 PM CET Daniel P. Berrangé wrote:
> When we attempt to build libvirt in Copr, the test suite times out on
> s390 builds.
>
> IIUC, this is because s390 in Copr is using a QEMU emulated system,
> not native hardware, and thus is massively slower to execute.
>
> W
On Sat, Jan 30, 2021 at 12:08:18PM -0800, Kevin Fenzi wrote:
> On Fri, Jan 29, 2021 at 03:26:18PM +, Daniel P. Berrangé wrote:
> > When we attempt to build libvirt in Copr, the test suite times out on
> > s390 builds.
> >
> > IIUC, this is because s390 in Copr is using a QEMU emulated system,
On Fri, Jan 29, 2021 at 03:26:18PM +, Daniel P. Berrangé wrote:
> When we attempt to build libvirt in Copr, the test suite times out on
> s390 builds.
>
> IIUC, this is because s390 in Copr is using a QEMU emulated system,
> not native hardware, and thus is massively slower to execute.
>
> We
When we attempt to build libvirt in Copr, the test suite times out on
s390 builds.
IIUC, this is because s390 in Copr is using a QEMU emulated system,
not native hardware, and thus is massively slower to execute.
We don't want to bump up the default test suite timeout unconditonally,
as that make
11 matches
Mail list logo
