[Debian-science-sagemath] Nearly released; but ell_rational_field has lfunction/sympow failures

[Jerome BENOIT]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,

On 14/12/16 07:46, Ximin Luo wrote:
> Jerome BENOIT:
>>
>>
>> On 14/12/16 03:25, François Bissey wrote:
>>
>>>> On 14/12/2016, at 16:23, Ximin Luo <infinity0 at debian.org> wrote:
>>>>
>>>> Ximin Luo:
>>>>> I built 7.4-1 for Debian experimental, it failed with 89 test failures. However, I think I have fixed 12 of them, which takes it below our arbitrary "80 failed tests" limit and I am now rebuilding it. I will upload this to NEW in the morning.
>>>>>
>>>>> However, we do need to fix the following before we re-upload to unstable:
>>>>>
>>>>> 30+ of those test failures are from ell_rational_field.py, the direct failures in that file (17) are attached. It seems related to lfunction or sympow. 
>>>>>
>>>>> [..]
>>>>
>>>> Maaaybe this is because sympow craps out when it can't write to ~/.sympow. I've logged into the schroot session where sbuild is working and manually created this directory now, so `sympow` at least works. I'm going to bed, will report back with the results in the morning.
>>>>
>>
>>> Sounds likely. simpow will create a number of data files
>>> and in debian and Gentoo we create them in ~/.sympow.
>>
>> For Debian, sympow was patched to create data on the fly in such
>> a way it is transparent for the final user [1].
>> I have no idea if it was applied to Gentoo.
>>
>> Jerome
>>
>> [1] http://sources.debian.net/src/sympow/1.023-7/debian/patches/upstream-on_fly_new_data.patch/
>>
> 
> Thanks for the input guys. It looks like the non-existent (and non-writable) $HOME was indeed the reason for the failures.
> 
> But unfortunately my work-around failed because I did the wrong thing - I created /home/infinity0 inside the chroot but I should have instead done `su -c 'chown infinity0: /sbuild-nonexistent'` because that is what sbuild sets $HOME to - and it already exists because something creates /sbuild-nonexistent/.jupyter/migrated with root-owned permissions during sbuild's setup phase.
> 
> That is pretty annoying :/ We will be forced to fix it for unstable, because the buildd network uses sbuild.
> 
> Perhaps we can set HOME=$DOT_SAGE for all sympow child processes, in Sage?

What about a HOME in debian/tmp ? 

Jerome

> 
> X
> 
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calculus@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-----BEGIN PGP SIGNATURE-----

iQQcBAEBCgAGBQJYUPutAAoJED+SGaZ/NsaL+HEgAJWG4K8Q9yS/NmuIFnN1KJFs
+QnhynGQvNysE54HCHJyROgzbht4h5l4MboLswbXedgpKy1wvnTVvgn/dnxVY126
i7G/hggi2uqSCwWkYunOOJezwDa2F98aX7VgBWEcbO9XThJKWjJKrKCt0hKnRAJe
CLel9jRonXwM0lNPZ/yXnZ8ObDppqsCKBB4CpVypg6Yi5ZhycEOebyTxMF/4M/fJ
qAoqlbXMiKLBqYUSiJA1ZwNDCWICsIvkq8wQcstcnXFfPt/niJ1aZzfK39ogHDkB
6O6nqR8ztiL3w4ycsCOHLt3a802rhdGqxT90nS3eGnpIAdhI0/Pi/Py6JQD2RiSc
3C/Ar6w/CbTDSg7gsWwraIZfDxV6Kg2PRNEMOIezkagKXrRCyeunFlR/T9CUAuw5
kUB+7A6v13y0smLPmrPjQicjMHrhRqsbhRu9VJDHRmKa8mg2af7yQQTHbOBUNeLY
a3mJ75nDIVNLiX0XxwtUyj5RlQO9Zhf3AQdsvYQAGjjnmnUF5kXrVtO0XzVO35fB
1/kXhwVxk51gV4OkYCIJE9gqBMywvVhIBaoh3YvpiQ++Tqskr+5g316M7ykM0pz5
IKPwDMEooHS7EvgQagul1QY8N7pMfsPkNwh2p0f8eNMdd9sUvVkIllrq0cvpTiG9
bSe3H0KQjjFeLNYb5QSmi2UqO7Uyi9saV4Q5bRVvrT/B1UaJPMyAZdFI5S6qe9S0
0Ra38es0bCoE8fHUPUirQ/RyrRlX4PlkFwqO8J0ZLNdbqqQJ7aA/BNnF0HgnnOGG
cD6vTAyqMu0HzByieAzwGZQ/vFIZ27Ji2AmsjqsapaYXR15N+eAdPoTWBasFjvEN
EGKMPVuZ0G9Gi4DjDPJlge25KxF3HaP6rRVZRHyjIQ1DKBJ+wW/y3RNpHpBNGWp5
ROFyAw+YNJ6tG2IIwYDRccb9zZZf878s+l/CZGE6I5JMVr/LTNzsrzlZVSmETz5C
S6oTEGiAf6al+B+S1ie6b9G4fq7HMDgXk46Gy0PVCnQGsjkfYsww8HXXm6BMk7jE
ubfGTs9Z2nCQDRQCi8FXMKtim29WDWh2MQUqAfeNL4YE5pIdPZQD3CRaJcCzx2bp
ocRNn/yEJJ1csR4ywpLSTd7QIFhON8PMI/C/tPFJvzaDiq2Sgq2heCfFzhXqeTEk
I8nTGeIg3kmjJakEGX0crFwHKf+A38Dx4TqO0nQeGz3S27DetQDnnX7swIkWE2ne
ITusvZ1V8iq+W91fBgRm+qV3kPrHhwgu/HIZ9TX3NrgAFHhSxlkdLqpEalMVL9J7
clBdwNlvqmOwdNOjRxuzucHUkLSwXrvcwP0zbaKD0EqOg9XkBdszEEEejoBGpRw=
=VVGp
-----END PGP SIGNATURE-----