19 May
2021
19 May
'21
4:20 p.m.
Maamoun TK maamoun.tk@googlemail.com writes:
Did you get the credentials of the new VM?
Yes! I set it up and updated the gitlab config last evening, and I've seen a successfull ci run.
I'm thinking after adding the address and ssh key of new VM, we can't get the optimized cores of AES tested since enable-msa isn't triggered. We need to push some sort of hard-coded option in configure.ac to get it tested in the VM during ci job.
We could either switch it on by default in configure.ac, or add a configure flag in .gitlab-ci.
Once fat build support is added, we will no longer to enable it explicitly, right?
Regards, /Niels
--
Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677.
Internet email is subject to wholesale government surveillance.