add cirun-openstack-gpu-large to tinygrad #1819
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is another attempt at #1818, by using one of the openstack runners (it's similarly useful to have have an actual GPU to test the JIT code there, so this makes sense independently).
That is because
admin-requests/conda_forge_admin_requests/access_control.py
Lines 162 to 168 in fd804c9
does not actually work for non-openstack runners. I had not understood this aspect at the time of da8b21e, apologies.
This is not easy to extend because the interface in smithy expects
--cirun_users_from_json=...as an argument, which is not necessarily what we want for other resources (where a simpleusers:list should be created). We'll probably have to expand that interface (both in the yamls here, as well as in smithy; cirun itself should be generic enough AFAICT).Concretely, after #1818 there was a PR to the feedstock (though not to
.cirun, which I handled in conda-forge/.cirun#138), but it did not set up any actions.This is yet another aspect of #1749