Closed ikalash closed 1 year ago
Forgot the attachment. Here it is. nightly_log_attawayAlbanyIntelSerialBuild.txt
@ikalash I haven't seen this one before. ~What compiler (and version) is this build using?~ Nevermind. I see icc-19.0.5.281
in the build string.
I haven't built with Intel compilers (outside of the new llvm based one) in some time. I'll see if I can reproduce this.
Ugh, unfortunately internal compiler errors are often nonsense. The fix sometimes involves rearranging some code, splitting code among separate cpp files, or removing seemingly innocuous (and perfectly legit) const
qualifiers. All of this requires time (first, to narrow down the exact line in our code where the issue is, and then to find a workaround). @cwsmith are you going to try to find the problematic line(s)? Usually bisection (commenting out code) works well.
Attempting to use a different compiler or compiler version, if possible, sometimes also helps (though not always).
@ikalash I haven't seen this one before. ~What compiler (and version) is this build using?~ Nevermind. I see
icc-19.0.5.281
in the build string.I haven't built with Intel compilers (outside of the new llvm based one) in some time. I'll see if I can reproduce this.
Thanks! We actually have another intel build which is using icc-2021.3.0. That one builds Omega_h just fine. So it may have something to do with the versions.
It's probably not worth it to spend time on Intel 19. Why don't we simply disable Omega_h on that build?
I am happy to do this. Will do it now.
There is a cryptic internal error encountered when building Omega_h on the attaway cluster:
The full output is attached.
@cwsmith , @bartgol : have you seen an error like this before?
This is when building omega_h as a part of Albany. I suppose I could try building it stand-alone to see if the same error is encountered, if you think it would be useful.