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

ENH: Unified interface for creating swap files? #1971

Open
h-vetinari opened this issue Jul 9, 2024 · 1 comment
Open

ENH: Unified interface for creating swap files? #1971

h-vetinari opened this issue Jul 9, 2024 · 1 comment

Comments

@h-vetinari
Copy link
Member

h-vetinari commented Jul 9, 2024

From #1751, where I had noted at the time:

If we're making a new switch for swap files, it would probably make sense to tie this in with conda-forge/conda-forge-ci-setup-feedstock#155 / conda-forge/conda-forge-ci-setup-feedstock#158, which is currently activated by:

azure:
  settings_win:
    variables:
      SET_PAGEFILE: "True"

I had an unmerged PR that would have allowed setting the size too, if we want to match it in capabilities with linux.

Not sure about where the PowerShell script would have to live, but IIUC, conda-smithy would just generate the call in azure-pipelines-wind.yml.tmpl, but could rely on the fact that the respective PowerShell script is present after conda-forge-ci-setup has been installed.

In contrast, the interface on linux looks like:

azure:
  settings_linux:
    swapfile_size: 15GiB

A potential unification was descoped at the time to not hold up the PR, but it would be nice to have a uniform way to do this cross-platform.

Originally posted by @h-vetinari in #1751 (comment)

@jakirkham
Copy link
Member

This seems like a good idea

Do we see them staying roughly the same across platforms? Or do we need some escape hatch for customizing per OS?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants