http://bugzilla.suse.com/show_bug.cgi?id=1048541
http://bugzilla.suse.com/show_bug.cgi?id=1048541#c1
--- Comment #1 from Michel Normand ---
as per job history (1) the build failures are reported only with lamb* workers
and not with wildcard* cloud* build* workers.
That for sure differ by their cpu types and configuration.
So I would suggest to find a way to configure and add a _constraints file.
I do not know yet how to do that.
Anyway as per readme.suse;
libatlas should be built on machine where it is supposed to be used, so
delivered binaries of distro is not critical.
(1)
===
$osc jobhist -l10 openSUSE:Leap:42.3 libatlas3 standard x86_64
time package reason code build time
worker
2017-05-22 18:29:55 libatlas3 new build failed 4m 2s
lamb60:2
2017-06-08 23:09:16 libatlas3 meta change failed 3m 36s
lamb12:6
2017-06-13 22:20:46 libatlas3 meta change failed 3m 32s
lamb03:4
2017-06-20 18:12:06 libatlas3 new build succeeded 15m 28s
cloud103:2
2017-06-26 08:03:16 libatlas3 meta change failed 4m 1s
lamb75:8
2017-06-26 22:50:46 libatlas3 new build failed 4m 21s
lamb53:1
2017-06-29 16:41:02 libatlas3 new build failed 4m 38s
lamb07:7
2017-07-02 22:03:48 libatlas3 new build failed 3m 41s
lamb53:10
2017-07-07 21:30:02 libatlas3 new build failed 3m 46s
lamb04:8
2017-07-08 08:40:58 libatlas3 new build failed 3m 59s
lamb20:1
===
$osc jobhist -l2000 openSUSE:Leap:42.3 libatlas3 standard x86_64 |grep -E
'source|succeeded'
2016-11-23 04:25:49 libatlas3 new build succeeded 11m 54s
wildcard2:8
2016-11-26 09:00:28 libatlas3 meta change succeeded 13m 17s
wildcard2:3
2016-12-04 11:17:09 libatlas3 new build succeeded 13m 26s
cloud121:2
2016-12-08 23:18:37 libatlas3 meta change succeeded 8m 13s
build83:3
2017-01-18 16:57:14 libatlas3 meta change succeeded 14m 45s
build76:3
2017-05-08 17:49:31 libatlas3 new build succeeded 7m 58s
build75:3
2017-06-20 18:12:06 libatlas3 new build succeeded 15m 28s
cloud103:2
===
--
You are receiving this mail because:
You are on the CC list for the bug.