Skip to content
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

feat: Add ability to cache compilers between runs #98

Open
gnikit opened this issue Jun 2, 2024 · 1 comment
Open

feat: Add ability to cache compilers between runs #98

gnikit opened this issue Jun 2, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@gnikit
Copy link
Member

gnikit commented Jun 2, 2024

It would be extremely useful if the Action had a key option cache, similar to setup-python that could enable/disable caching the downloaded compilers and the setup.

Suggestion

    - uses: fortran-lang/[email protected]
      id: setup-fortran
      with:
        compiler: ${{ matrix.toolchain.compiler }}
        version: ${{ matrix.toolchain.version }}
        cache: true  # optional, default is false
@wpbonelli wpbonelli added the enhancement New feature or request label Jun 2, 2024
@wpbonelli
Copy link
Contributor

Some notes

  • We already cache the Intel toolchain on Windows. The key currently rotates daily to avoid a broken state where the cache can neither be restored nor refreshed, backstory here. Not sure if still relevant but even if so, maybe we just warn people may need to occasionally clear it?
  • Windows seems like highest priority as even GCC and LFortran installs are fairly slow (~5 and ~2.5 min respectively). Intel is usually slowest, although on Ubuntu the slowest is Nvidia. But makes sense to cache all platforms/compilers IMO

@wpbonelli wpbonelli added help wanted Extra attention is needed good first issue Good for newcomers labels Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants