Skip to content

CI: Add experimental LFortran support - #316

Merged
bonachea merged 10 commits into
BerkeleyLab:mainfrom
bonachea:lfortran
Apr 16, 2026
Merged

bonachea merged 10 commits into
BerkeleyLab:mainfrom
bonachea:lfortran

Conversation

@bonachea

Copy link
Copy Markdown
Member

Minor script and code adjustments to accommodate LFortran version 0.62 and latest, which are now capable of building Caffeine (under the right conditions). Add LFortran to CI on Linux to help prevent bitrot. LFortran support remains deliberately undocumented for now.

Also deploy some factorization in the workflow definition file to ease maintenance.

LFortran correctly identified/reported that the arguments to MAX
are all required to have the same type and kind
Identified via harmless LFortran warning, but worth fixing regardless
Ideally this would be a GitHub configuration variable, but there
appears to be no reliable way to set a configuration variable
that will reliably be inherited across repo forks, regardless of organization.
Also:
* Workaround ISO_Fortran_binding.h missing from LFortran installs (issue 11079)
* Factor curl options
@bonachea
bonachea requested review from ktras and rouson April 15, 2026 00:19
@certik

certik commented Apr 15, 2026

Copy link
Copy Markdown

Let me know if you need any fixes in LFortran. We'll iterate on the usage and command-line options. We'll change some of the defaults over time to make it easy to use.

@bonachea

Copy link
Copy Markdown
Member Author

Let me know if you need any fixes in LFortran.

Thanks @certik !
You've already been amazingly responsive and productive in addressing our requests.

I look forward to continuing our productive partnership, and helping to support LFortran's growth and eventual deployment of multi-image features!

There are NO command changes in this commit, simply code motion
and addition of section comments.
@certik

certik commented Apr 15, 2026

Copy link
Copy Markdown

Thank your for using LFortran and giving us feedback, this is super helpful for us.

@bonachea

Copy link
Copy Markdown
Member Author

@certik would you be willing to add additional tags on the LFortran container package to correspond to versioned releases?

We have CI in multiple projects (and now this one, after this PR) relying on an LFortran DockerHub container that @PHHargrove kindly builds for us after each LFortran release, but it would save some steps if LFortran just provided release containers directly.

@certik

certik commented Apr 15, 2026

Copy link
Copy Markdown

Yes, we can do that. What exactly do we need to do?

@bonachea

Copy link
Copy Markdown
Member Author

Yes, we can do that. What exactly do we need to do?

Issue entered: lfortran/lfortran#11100

@ktras ktras left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bonachea
bonachea merged commit cc127ca into BerkeleyLab:main Apr 16, 2026
42 checks passed
@bonachea
bonachea deleted the lfortran branch April 16, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants