the test logs should be in logs/tests.log,
post them here, otherwise it's hard to say what's wrong
On 9 March 2025 00:09:53 GMT-06:00, Ashutosh Rajora
wrote:
>
>The testing ended, but i can see a lot of FAILED TESTS, are they normal?
>and can i proceed to contribute or these need to be fixed?
The testing ended, but i can see a lot of FAILED TESTS, are they normal?
and can i proceed to contribute or these need to be fixed?
--
sage -t --warn-long 5.0
--random-seed=136679533914642111015813988340208459895
src/sage/symb
Thanks a lot sir,
Previously I tried re-running "make" but it had failed,
so this time particularly mentioned it to run no parallel jobs while
building SciPy, ensured this by running :
make SAGE_NUM_THREADS=1 MAKE="make -j1" scipy
make SAGE_NUM_THREADS=2 MAKE="make -j2"
and the BUILD was SUCC
perhaps you are running too many complications in parallel, and that's why one
of them errors out. As scipy uses ninja, check out ninja documentation on how
to limit the number - that's a parameter to add to ninja call.
This might need a small patch to scipy,
or using another version of scipy...
Can anybody please assist with this issue.
On Saturday, March 8, 2025 at 9:50:10 AM UTC+5:30 Ashutosh Rajora wrote:
> how to check this:
>
> " It looks indeed as an insufficient RAM for the C++ compiler.
> Do you have a fixed amount of RAM allocated to WSL? It should better be
> 4Gb or more."
>
It looks indeed as an insufficient RAM for the C++ compiler.
Do you have a fixed amount of RAM allocated to WSL? It should better be 4Gb or
more.
I am not sure what "free -h" is showing here.
If RAM is dynamically shared between Windows and WSL, it doesn't mean much.
Try re-running "make"
On
