-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora 38 is EOL --> compilation crashes at rpmfusion returning 404 error #100
Comments
Yeah this has been on the list for a while, but at the time I was running into some availability issues for packages I think. I'm not sure if the second part is related to this issue. |
I think it is. Rpmfussion is returing 404 for Fedora 38 since:
So it seems that it will not come back online. The only solution would be to upgrade Fedora. |
I was referring to the failing pip install with "the second part". I don't think that is related to RPMFusion, but the base container indeed needs updating to a more recent Fedora. |
Later also
[...] Workaround: EDIT: Later it crashes at:
Is it possible to relax version requirement here? https://github.com/tikk3r/flocs/blob/fedora-py3/requirements3.txt#L112 EDIT: I verified that latest |
There are a lot of At Casacore there is:
Explanation: https://github.com/casacore/casacore/releases/tag/v3.4.0. |
I verified that if finds the libraries without DUSE_FFTW3.
|
Potentially. I think I put it in because there was something about it that didn't install or interfered when later versions were used, but it might be relaxable now.
DDFacet is a beast of its own as you can probably see from the amount of |
Do you have any LOFAR related benchmarking scripts or anything like that? I would like to test some optimizations. |
I have a bunch of reference datasets that I image at every release. I can make those commands available in the repository at some point. |
In intel FFTW is not manually compiled. In AMD it is. |
It should be safe to upgrade OpenBLAS to this: |
In the tests: https://github.com/tikk3r/flocs/actions/runs/12415699968/workflow?pr=114#L32 |
It would be interesting to see if it makes a difference for the Intel containers. For AMD it was a necessity as the one that shipped with AOCL wasn't built threaded (at the time at least). |
|
This is intentional. AVX512 is giving odd segfaults in certain situations on our cascadelake machines, so I have it off by default. |
At IDG there is: |
There is:
in the Sagecal install logs even thought
Also there is
even thought
Also there is:
Maybe |
I just got this again:
|
Have you tried updating the CPU microcode and BIOS there? |
It was not easily reproducible, so we just left it at that.
Yeah, many of the toggles there are also becoming obsolete as the compiler has been warning me some will be removed. I didn't know
This seems to be an incompatibility of the shadeMS update. I've reverted it so it should be fixed again.
I think Release used to run some test or something that failed, but I don't think there's a particular reason to keep it at debug.
For the sagecal stuff, there is probably a bunch of stuff that can be done better for that installation. I put it in there to test it with Rapthor at some point previously, but none of my processing really uses it so I haven't looked deeply into it. |
Yes, as far as I understand it can. By the way, Fedora 39 is also EOL now :) But I might be too early for Fedora 40. |
I am aware, but something about these recipes combined with Fedora >=40 makes it such that stuff doesn' t build. I'm trying to figure out why. |
GCC 14 has some nice performance improvements, eg. in vectorization: BTW You could try this instead of disabling the entire AVX-512:
|
How about
after debug condition at the very end of |
Is it still necessary to use |
Probably |
Probably not on a technical basis, but I like it for keeping things separate from the OS and since I use venvs on other machines as well it serves as a sort of "test" at the same time. I think there have been some slight concerns about the overhead of mounting venvs on certain file systems in the past, but nothing I notice in my daily processing.
I think mtune defaults to whatever march is set to yeah. At least GCC 14 on my laptop it does. I am not sure what you mean with them not being valid? Do you mean the sandybridge default? |
Eg. this: |
I am not sure if this is working as we wanted
|
Do you think this line is neccesary? |
I read that as mtune being set to generic by default, if left unspecified. I don't think these container builds have been affected in that case as mtune was always specified alongside march.
If I remember right that source didn't fully load things for me, but I could be remembering that wrong. |
Ah, hmm. Well it was worth a try. |
The log is larger without it (2385 vs 2927 kB). So no reason to revert this. |
Should CASACore use MPI? Currently it is off: |
Is Sagecal:
|
We don't use MPI, so I'm not sure if it has any effect or benefit from turning it on. |
Describe the bug
Fedora 38 is EOL.
Logs or error messages
Additional information (if applicable or known):
https://discussion.fedoraproject.org/t/rpm-fusion-nonfree-updates-not-working-cant-download-nvidia-drivers/139016
Moving to Fedora 39 seems to fix it, but later:
A possible workaround is to manually install this commit:
pycontribs/xmlrunner#16
or install this instead: https://pypi.org/project/unittest-xml-reporting/ . It is imported the same way, so it might be a replacement. I verified taht it solves the above error.
It then crashes at
astropy-helpers
(https://github.com/astropy/astropy-helpers?tab=readme-ov-file#deprecated):Invoked here: https://github.com/tikk3r/flocs/blob/fedora-py3/requirements3.txt#L5 . Is it still needed?
The text was updated successfully, but these errors were encountered: