1 |
For me the tests pass on both Gentoo and Prefix: |
2 |
|
3 |
Gentoo: |
4 |
>>> Source compiled. |
5 |
>>> Test phase: sci-mathematics/pari-2.11.2 |
6 |
make -j5 dobench |
7 |
Making dobench in Olinux-x86_64 |
8 |
make[1]: Entering directory |
9 |
'/var/tmp/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64' |
10 |
* Testing objets gp-dyn..TIME= 1 |
11 |
* Testing analyz gp-dyn..TIME= 11 |
12 |
* Testing number gp-dyn..TIME= 11 |
13 |
* Testing polyser gp-dyn..TIME= 4 |
14 |
* Testing linear gp-dyn..TIME= 5 |
15 |
* Testing elliptic gp-dyn..TIME= 16 |
16 |
* Testing sumiter gp-dyn..TIME= 5 |
17 |
* Testing graph gp-dyn..TIME= 4 |
18 |
* Testing program gp-dyn..TIME= 3 |
19 |
* Testing trans gp-dyn..TIME= 13 |
20 |
* Testing nfields gp-dyn..TIME= 52 |
21 |
+++ Total bench for gp-dyn is 83 |
22 |
|
23 |
Prefix: |
24 |
>>> Source compiled. |
25 |
>>> Test phase: sci-mathematics/pari-2.11.2 |
26 |
make -j13 dobench |
27 |
Making dobench in Olinux-x86_64 |
28 |
make[1]: Entering directory |
29 |
'/storage/strogdon/gentoo-rap/var/tmp/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64' |
30 |
* Testing objets gp-dyn..TIME= 0 |
31 |
* Testing analyz gp-dyn..TIME= 12 |
32 |
* Testing number gp-dyn..TIME= 8 |
33 |
* Testing polyser gp-dyn..TIME= 4 |
34 |
* Testing linear gp-dyn..TIME= 4 |
35 |
* Testing elliptic gp-dyn..TIME= 16 |
36 |
* Testing sumiter gp-dyn..TIME= 4 |
37 |
* Testing graph gp-dyn..TIME= 0 |
38 |
* Testing program gp-dyn..TIME= 4 |
39 |
* Testing trans gp-dyn..TIME= 12 |
40 |
* Testing nfields gp-dyn..TIME= 44 |
41 |
+++ Total bench for gp-dyn is 72 |
42 |
|
43 |
The testing is done under /var/tmp and $EPREFIX/var/tmp |
44 |
|
45 |
Steve |
46 |
|
47 |
On Thu, Jul 18, 2019 at 5:14 PM François Bissey <frp.bissey@×××××.com> wrote: |
48 |
> |
49 |
> Hi all, |
50 |
> |
51 |
> For several years now I have keeping pari up to date in the |
52 |
> sage-on-gentoo overlay, even getting upstream snapshots as |
53 |
> needed for sage. For a while my stable ebuilds have been picked |
54 |
> up for the main tree by a kind soul. |
55 |
> |
56 |
> For several years now I haven't been able to successfully run |
57 |
> any of pari testsuite from portage. And it seems to be something |
58 |
> in the portage environment. I have now decided to seek some help |
59 |
> on the issue as I have run out of things I can think of a long |
60 |
> time ago. |
61 |
> |
62 |
> So if I run "ebuild pari-2.11.2.ebuild test" (valid with all older |
63 |
> ebuilds available) I get |
64 |
> >>> Source compiled. |
65 |
> >>> Test phase: sci-mathematics/pari-2.11.2 |
66 |
> make -j8 dobench |
67 |
> Making dobench in Olinux-x86_64 |
68 |
> make[1]: Entering directory |
69 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64' |
70 |
> * Testing objets gp-dyn..TIME= 1 |
71 |
> * Testing analyz gp-dyn..TIME= 3 |
72 |
> * Testing number gp-dyn..BUG [10] |
73 |
> * Testing polyser gp-dyn..BUG [3] |
74 |
> * Testing linear gp-dyn..BUG [0] |
75 |
> * Testing elliptic gp-dyn..BUG [14] |
76 |
> * Testing sumiter gp-dyn..TIME= 5 |
77 |
> * Testing graph gp-dyn..TIME= 3 |
78 |
> * Testing program gp-dyn..TIME= 0 |
79 |
> * Testing trans gp-dyn..TIME= 11 |
80 |
> * Testing nfields gp-dyn..BUG [38] |
81 |
> +++ [BUG] Total bench for gp-dyn is 57 |
82 |
> |
83 |
> PROBLEMS WERE NOTED. The following files list them in diff format: |
84 |
> Directory: |
85 |
> /dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64 |
86 |
> number-dyn.dif |
87 |
> polyser-dyn.dif |
88 |
> linear-dyn.dif |
89 |
> elliptic-dyn.dif |
90 |
> nfields-dyn.dif |
91 |
> make[1]: *** [Makefile:344: dobench] Error 1 |
92 |
> make[1]: Leaving directory |
93 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64' |
94 |
> make: *** [Makefile:34: dobench] Error 2 |
95 |
> * ERROR: sci-mathematics/pari-2.11.2::sage-on-gentoo failed (test phase): |
96 |
> * emake failed |
97 |
> * |
98 |
> * If you need support, post the output of `emerge --info |
99 |
> '=sci-mathematics/pari-2.11.2::sage-on-gentoo'`, |
100 |
> * the complete build log and the output of `emerge -pqv |
101 |
> '=sci-mathematics/pari-2.11.2::sage-on-gentoo'`. |
102 |
> * The complete build log is located at |
103 |
> '/var/log/portage/build/sci-mathematics/pari-2.11.2:20190718-215929.log'. |
104 |
> * For convenience, a symlink to the build log is located at |
105 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/temp/build.log'. |
106 |
> * The ebuild environment file is located at |
107 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/temp/environment'. |
108 |
> * Working directory: |
109 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2' |
110 |
> * S: '/dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2' |
111 |
> fbissey@moonloop ~/Work/Overlays/sage-on-gentoo/sci-mathematics/pari $ |
112 |
> cd /dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2 |
113 |
> fbissey@moonloop |
114 |
> /dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2 $ make -j8 |
115 |
> dobench |
116 |
> Making dobench in Olinux-x86_64 |
117 |
> make[1]: Entering directory |
118 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64' |
119 |
> * Testing objets gp-dyn..TIME= 0 |
120 |
> * Testing analyz gp-dyn..TIME= 0 |
121 |
> * Testing number gp-dyn..TIME= 1 |
122 |
> * Testing polyser gp-dyn..TIME= 3 |
123 |
> * Testing linear gp-dyn..TIME= 0 |
124 |
> * Testing elliptic gp-dyn..TIME= 14 |
125 |
> * Testing sumiter gp-dyn..TIME= 5 |
126 |
> * Testing graph gp-dyn..TIME= 3 |
127 |
> * Testing program gp-dyn..TIME= 3 |
128 |
> * Testing trans gp-dyn..TIME= 11 |
129 |
> * Testing nfields gp-dyn..TIME= 42 |
130 |
> +++ Total bench for gp-dyn is 48 |
131 |
> make[1]: Leaving directory |
132 |
> '/dev/shm/portage/sci-mathematics/pari-2.11.2/work/pari-2.11.2/Olinux-x86_64' |
133 |
> |
134 |
> That's right the tests fails in the ebuild but pass when I run the same |
135 |
> command manually/ It is not a fluke due to running the tests twice. |
136 |
> If I do "ebuild ... compile" and then run the tests manually, they will |
137 |
> succeed. |
138 |
> |
139 |
> When I look at the diff produced by the test suite I gat stuff like |
140 |
> *** ../src/test/32/number 2018-07-26 06:00:21.000000000 +1200 |
141 |
> --- gp.out 2019-07-19 10:11:20.505605285 +1200 |
142 |
> *************** |
143 |
> *** 60,70 **** |
144 |
> |
145 |
> ? factor(100!+1,0) |
146 |
> |
147 |
> ! [101 1] |
148 |
> |
149 |
> ! [14303 1] |
150 |
> |
151 |
> ! [149239 1] |
152 |
> |
153 |
> |
154 |
> [432885273849892962613071800918658949059679308685024481795740765527568493010 |
155 |
> |
156 |
> 727023757461397498800981521440877813288657839195622497225621499427628453 1] |
157 |
> --- 60,73 ---- |
158 |
> |
159 |
> ? factor(100!+1,0) |
160 |
> |
161 |
> ! [ |
162 |
> |
163 |
> ! |
164 |
> 101 1] |
165 |
> |
166 |
> ! [ |
167 |
> |
168 |
> ! |
169 |
> 14303 1] |
170 |
> |
171 |
> ! [ |
172 |
> |
173 |
> ! |
174 |
> 149239 1] |
175 |
> |
176 |
> |
177 |
> [432885273849892962613071800918658949059679308685024481795740765527568493010 |
178 |
> |
179 |
> 727023757461397498800981521440877813288657839195622497225621499427628453 1] |
180 |
> |
181 |
> The only difference is a widely different formatting of the output when |
182 |
> run under the portage environment. |
183 |
> |
184 |
> Does anyone have a clue as to how this is possible? What could cause it |
185 |
> and more importantly, how to fix it. |
186 |
> |
187 |
> Cheers, |
188 |
> François |
189 |
> |