On Wed, May 19, 2021 at 7:20 PM Niels Möller wrote:
> Maamoun TK writes:
> > 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
Maamoun TK 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
Hi, Niels
Did you get the credentials of the new VM? 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
