Hi, just to clarify why now all github actions are red. It is caused by TW glibc update. See for more info https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/P...
I expect we need to use again 15.3 workaround or wait till github apply patch.
Josef
Dne 23. 09. 21 v 20:41 josef Reidinger napsal(a):
Hi, just to clarify why now all github actions are red. It is caused by TW glibc update. See for more info https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/P...
I expect we need to use again 15.3 workaround or wait till github apply patch.
I have created an issue for GitHub Actions regarding this problem [1].
I found out a workaround by using the "--privileged" Docker option, see the PoC [2]. With that option the jobs can be run successfully.
Let's see what they respond, if the fix takes too long I'd apply the workaround in all YaST Git repositories. I'm already preparing a script for that...
Ladislav
[1] https://github.com/actions/virtual-environments/issues/4193 [2] https://github.com/yast/yast-packager/pull/579/files
On 9/30/21 14:39, Ladislav Slezak wrote:
Dne 23. 09. 21 v 20:41 josef Reidinger napsal(a):
Hi, just to clarify why now all github actions are red. It is caused by TW glibc update. See for more info https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/P...
I expect we need to use again 15.3 workaround or wait till github apply patch.
I have created an issue for GitHub Actions regarding this problem [1].
I found out a workaround by using the "--privileged" Docker option, see the PoC [2]. With that option the jobs can be run successfully.
Let's see what they respond, if the fix takes too long I'd apply the workaround in all YaST Git repositories. I'm already preparing a script for that...
Ladislav
[1] https://github.com/actions/virtual-environments/issues/4193 [2] https://github.com/yast/yast-packager/pull/579/files
Thanks a lot Ladislav for taking care ;)
Dne 30. 09. 21 v 17:17 José Iván López González napsal(a):
Let's see what they respond, if the fix takes too long I'd apply the workaround in all YaST Git repositories. I'm already preparing a script for that...
It seems that GitHub is waiting for the official Docker fix which should be included in Docker 20.10.9.
I guess that will take quite some time so I decided to apply the "--privileged" workaround in all YaST and libyui GitHub repositories.
GitHub Actions should now works properly, if you still find some problem just ping me.
Ladislav
I fixed a problem in rake tasks [1] when running the GitHub Actions locally on your machine ("rake actions:run").
If you want to run the Actions locally make sure you have installed yast-rake >= 0.2.42.
Ladislav
[1] https://github.com/yast/yast-rake/pull/85
-- Ladislav Slezák YaST Developer
SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8
Hello,
GitHub has just updated the Docker included in the VM images to version 20.10.10 which contains the fix for the new glibc-2.34. [*]
The "--privileged" workaround in the GitHub Actions is not needed anymore, I have removed that option from all YaST repositories by a script.
If you still see some problem in GitHub Actions then just ping me.
Ladislav
[*] https://github.com/actions/virtual-environments/issues/4193#issuecomment-959...
-- Ladislav Slezák YaST Developer
SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8
-
josef Reidinger -
José Iván López González -
Ladislav Slezak -
Ladislav Slezak