fix ci jobs make backends

[andrewfowlie]

Some of the CI jobs fail because of missing Python deps, e.g., https://github.com/GambitBSM/gambit/actions/runs/13601337841/job/38027844094#step:5:8808. I wonder if we can add a step to the workflow, maybe around here,

gambit/.github/workflows/ci_linux.yml

Lines 24 to 28 in 8f1a9da

	- name: Set up build environment
	run: |
	echo "Set up the build environment"
	mkdir -p BUILD
	cd BUILD

that does

pip install --user -r optional.txt

where optional is the file https://github.com/GambitBSM/gambit/blob/master/optional.txt. I'm not sure though because these CI jobs are on our runners and I don't know the setup. The advantage here is that anyone can fix these kinds of issues by adding to the optional.txt file.

[ChrisJChang]

I tried to see if this would work, however on our Linux runner, it is limited in space. Just trying to install all of the requirements in the optional.txt will fail. Allowing the user to install other packages on this machine is probably not a good idea.

[ahye]

Hi @ChrisJChang, I might be misunderstanding, but is this a problem on wino? If so we should be able to fix it. How much space is needed?

[ChrisJChang]

@ahye . Yes this was on Wino. I am not sure how much space is needed, but when installing tensorflow and its requirements, it claimed to run out of space. I deleted several Gb on my home directory in case it was the limiting factor, but it did not prevent this.

[ahye]

OK, let me have a look at it when I am back after the summer holidays.

I'm going to need some info on how this is set up. Is this on your home directory for example? That might be an issue because that is limited by your UiO account and its storage cap, which is mounted whatever internal UiO server you are on, while most if the space on wino is on \scratch2

Is there an alternative to move the installation to \scratch2? You should have r+w there.

[ChrisJChang]

Everything is running from my home directory. I noticed that I can install these packages successfully if I log onto Wino and do it manually, but not if it is through the runner. The runner has write permissions in my home directory, so it should be able to do this.

[ahye]

Odd. This might be some security feature, but strange since the runner obviously can write other files.

Do you know where it is trying to write? In other words, what is --user going to imply here? Is it guaranteed to do the same as if you executed that pip command in the terminal?