CI fails to build opencv on x86-64

  • Done
  • quality assurance status badge
Details
2 participants
  • Guillaume Le Vaillant
  • Leo Famulari
Owner
unassigned
Submitted by
Guillaume Le Vaillant
Severity
normal
G
G
Guillaume Le Vaillant wrote on 8 May 2021 09:34
(address . bug-guix@gnu.org)
874kfdllvh.fsf@kitej
Hi,

It looks like the build farm fails to build the opencv package on
x86-64. The build log (see [1] or [2]) indicates that the build
"timed out after 3600 seconds of silence" in the test phase, more
precisely in the 'opencv_test_aruco' test.

What is strange is that on my machine the build succeeds and this
'opencv_test_aruco' test takes less than 1 second.

Does someone see the test phase getting stuck when building opencv
locally?


-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYJY/Ag8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9OXQEApYN2oOuy9EuUIsw8RsWRtl9kjiaao6xfk1fZ
URDCrVABAI9Y55jCHB8YSfoSImN6B56wYCc82UE9xl1iYH84KzMO
=DRzd
-----END PGP SIGNATURE-----

L
L
Leo Famulari wrote on 8 May 2021 21:25
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 48282@debbugs.gnu.org)
YJblknHbGocfH16B@jasmine.lan
On Sat, May 08, 2021 at 07:34:26AM +0000, Guillaume Le Vaillant wrote:
Toggle quote (5 lines)
> It looks like the build farm fails to build the opencv package on
> x86-64. The build log (see [1] or [2]) indicates that the build
> "timed out after 3600 seconds of silence" in the test phase, more
> precisely in the 'opencv_test_aruco' test.

Are you using Intel or AMD?

I ask because of this upstream bug report about ArUco not working on AMD
processors:


The build farm is AMD.
G
G
Guillaume Le Vaillant wrote on 9 May 2021 09:54
(name . Leo Famulari)(address . leo@famulari.name)(address . 48282@debbugs.gnu.org)
871rags5od.fsf@kitej
Leo Famulari <leo@famulari.name> skribis:

Toggle quote (15 lines)
> On Sat, May 08, 2021 at 07:34:26AM +0000, Guillaume Le Vaillant wrote:
>> It looks like the build farm fails to build the opencv package on
>> x86-64. The build log (see [1] or [2]) indicates that the build
>> "timed out after 3600 seconds of silence" in the test phase, more
>> precisely in the 'opencv_test_aruco' test.
>
> Are you using Intel or AMD?
>
> I ask because of this upstream bug report about ArUco not working on AMD
> processors:
>
> https://github.com/opencv/opencv_contrib/issues/2736
>
> The build farm is AMD.

The machine I used to build opencv (successfully) also has an AMD
processor (AMD Ryzen 9 5950X).
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYJeVQg8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j+h4gD9ETKeIUz6AHiBNwInagmN5xjqpqh06957FsHK
tzOAyH4BAJI7ulZyPFY3kyZjaIudkiNt00MAG+B8Os0uqLRMf8Y/
=ajQc
-----END PGP SIGNATURE-----

L
L
Leo Famulari wrote on 9 May 2021 16:09
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 48282@debbugs.gnu.org)
YJftC/ngibpVpsx8@jasmine.lan
On Sun, May 09, 2021 at 07:54:42AM +0000, Guillaume Le Vaillant wrote:
Toggle quote (3 lines)
> The machine I used to build opencv (successfully) also has an AMD
> processor (AMD Ryzen 9 5950X).

I saw some reports of success with Ryzen chips; maybe it's a problem
with AMD Epyc, which will be more typical for build farms and
high-performance workstations.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAmCX7QsACgkQJkb6MLrK
fwgPMw/9GzO7lrahHVNxcbBCTkzdgWL9yQSWSL58ZKNI1r7XWYqjvykcx2VuJN7F
ktg6dbLAIrHelOC3kumVifLmflEmo4c1mUloEK64uQ7M6Tj3QNt22cjSo62FL6q9
bpUjvecdbIs5ln7HBzHbWYM8vYk+22OUISbR5LqRta8I56wpuaZCFAnK/psSvRWR
TqFnAtkD2eJNfO24hsPmC62K6u7J1+LW+K6UHknk70OlTRP1Kdw073Z6FP4pp80k
1ltKZbJC7Jn+f6yzmqBC/9fOj3Sj1fiWHw7Gqej++yeFUWWkrsabVGZ+K6zFJFsU
DA8ZxjQNVKpmYI07oqeWXBp5QFErGJJs/6Oe5J2yhB9d+BIPl/U7rjG/51p+7H2z
RrpJQAuiSWSRcPNFMMqaPjU0gp/wdExODOq3MHeObgq7nBXBLjUcvTEw27KkC+3V
n9zmkQvqGzvLolcFd+QfxLGmyeTlnV0kc4Us9bp5dSQZsf6T0Ua5Aum2vSGuVU7M
REpH+sGHmb6ZOFDrKJkNBwlhhLD4v8Ul+BSlguelqLzh3U8zhj74j8cDEGkYAk/A
6lRWlWtbhSurNsAqlvNfDIEmiFYV1QUqUSdL8fpwys+F5JER9Q9C8f0pp0j7qhux
0B+s8KvD6cTtvkRNb5QoYKn6jcqNyhauNSu62aVX+EIVlEBeXWQ=
=l9qi
-----END PGP SIGNATURE-----


G
G
Guillaume Le Vaillant wrote on 20 Nov 2023 13:34
(address . 48282-close@debbugs.gnu.org)
87r0kkvbyf.fsf@kitej
It looks like this build failure doesn't happen anymore now.
Closing.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCZVtSuA8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j+U3gD9GlJmWm9QGGljDeN4QDynkjDxFjjNceatT96I
KbDD35UA/AqMgERvUqk4l17eiSYMzgUy0fA+kvWzDbIjae6IGMNx
=bnwj
-----END PGP SIGNATURE-----

?