-
Notifications
You must be signed in to change notification settings - Fork 1
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
enable tests in ga.spec #5
Comments
The mpi modules set the MPI_SUFFIX variable, which includes underscore
We should use that in the spec instead of manually use a dash ( Lines 147 to 151 in 7cf8461
|
There is an "chicken and egg" issue here (likely to affect in GlobalArrays/ga#154, too) |
@marcindulak I have updated my ga and nwchem trees to enable the ga tests. |
@marcindulak ga 5.7.2 is out |
It seems like tests on el6/el7/el8 are failing: |
I will have a look at it. In the meantime, I have just partially removed the last commit |
After adding verbose output for tests 6c92d39,
|
|
This is a recent MPICH bug report that could be related |
openmpi tests do work, instead |
I believe I've seen already el6 "gethostbyname failed". Maybe we should exclude mpich from el6 tests? Can you look into el7/el8 failures?
Another thing to check/fix - how do we limit the number of cores used by the tests? I would set it to 2. |
epel7 https://koji.fedoraproject.org/koji/taskinfo?taskID=42159068 is the hanging build and it uses I've updated the table above to the right epel7 failing with "Comparison failed" with openmpi. |
Thanks for the prompt update
The seg fault for el8 could be an issue that was reported for openmpi 4.1.0 |
I will have to get rid of the NPROCS=2 commit since some tests do require 4 processes |
Can we disable those tests? We don't know what cpu resources we have on the koji build servers. Apparently el7 provides a newer openmpi, but called openmpi3 https://bugzilla.redhat.com/show_bug.cgi?id=1709933#c3 and scalapack.spec uses special logic to handle this exception in naming https://bugzilla.redhat.com/show_bug.cgi?id=1709933#c18 |
Pushed ed797e7 to limit number of tests and restore NPROC=2 |
Green light now on epel8 and epel7 |
@marcindulak please try the latest commit c495ba3 |
el6/el7/el8/f33 build now. Should I package this ga for all of them or are we waiting still for some changes in ga needed by nwchem? |
I would go ahead an package this ga since it contains all the changes needed by nwchem |
small ga.spec changes with f978657 |
How critical is this change? Could you merge the fedora spec https://src.fedoraproject.org/rpms/ga/tree/master into your repo? We diverged in terms of the changelog, since I'm not merging your github changes into the fedora git repository (I had to release for example 5.6.5-8). We could agree on how we synchronize work between this github and fedora repository. |
These changes are not critical at all. They bear zero impact on functionality |
|
Thanks. dereferencing_fix.patch seems to be missing. If the patches are not critical, can we hold them back, and rely on them being part of the source of the next ga release instead? |
Thanks for spotting this 6dd7868 Yes, we can hold them back and wait for next ga release |
Would you be willing then to go back to 5.7.2-2 in your repo? Fedora will keep making auto commits to the spec master branch and we'll diverge in the changelog. |
Back to 5.7.2-2 |
I meant rather to sync to what's currently in https://src.fedoraproject.org/rpms/ga/blob/master/f/ga.spec, without additions to the changelog or Lines 16 to 17 in c3019a0
Making another build of all epel and fedora's will require 1-2 hours of attention, and I prefer to not spend time on those now. I think the way to go forward could be to have a branch in your repo called e.g. develop, and keeping your master branch always synced with the fedora master. We could prepare new builds in the develop branch and merge only to your master when things work, then I take your master and write into the fedora master. |
I think this issue can be closed as fixed |
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1709933#c15 we should execute tests during the build of ga, but it seems like the test is specific to mpich
fedpkg/ga/ga.spec
Lines 214 to 220 in 7cf8461
The text was updated successfully, but these errors were encountered: