Skip to content

Conversation

ggouaillardet
Copy link
Contributor

@ggouaillardet ggouaillardet commented Jul 24, 2024

NVIDIA HPC Compiler (e.g. nvfortran) incorrectly selected the GCC style pragmas to support IGNORE_TKR. Harden the test by mimicking exactly the mpi f08 bindings in order to fix that false positive.

Thanks Chris Parrot for the report.

Refs. #11582

Signed-off-by: Gilles Gouaillardet [email protected]
bot:notacherrypick
(back-ported from commit 600df6a)

Copy link

Hello! The Git Commit Checker CI bot found a few problems with this PR:

5660c69: configury: harden IGNORE_TKR check

  • check_cherry_pick: does not include a cherry pick message (did you need to bot:notacherrypick?)

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

@ggouaillardet ggouaillardet force-pushed the topic/v4.1.x/nvfortran_ignore_tkr branch from 5660c69 to 194d8a5 Compare July 24, 2024 04:21
Copy link

Hello! The Git Commit Checker CI bot found a few problems with this PR:

194d8a5: configury: harden IGNORE_TKR check

  • check_cherry_pick: does not include a cherry pick message (did you need to bot:notacherrypick?)

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

@ggouaillardet
Copy link
Contributor Author

:bot:retest

@wenduwan
Copy link
Contributor

bot:aws:retest

NVIDIA HPC Compiler (e.g. nvfortran) incorrectly selected the GCC
style pragmas to support IGNORE_TKR. Harden the test by mimicking
exactly the mpi f08 bindings in order to fix that false positive.

Thanks Chris Parrot for the report.

Refs. open-mpi#11582

Signed-off-by: Gilles Gouaillardet <[email protected]>
bot:notacherrypick
(back-ported from commit 600df6a)
@ggouaillardet ggouaillardet force-pushed the topic/v4.1.x/nvfortran_ignore_tkr branch from 194d8a5 to 903055c Compare July 25, 2024 16:07
@ggouaillardet
Copy link
Contributor Author

Odd...

I updated the PR to fix

ERROR: files left in build directory after distclean:
./check_ignore_tkr.mod

not sure why other branches were happy though...

@jsquyres jsquyres modified the milestones: v4.1.7, v4.1.8 Jan 23, 2025
@bwbarrett bwbarrett modified the milestones: v4.1.8, v4.1.9 Feb 5, 2025
@bwbarrett bwbarrett modified the milestones: v4.1.9, v4.1.10 Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants