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