On 10/21/24 19:02, Daniel P. Berrangé wrote:
The AF_ALG crypto integration for Linux is not being tested in
any CI scenario. It always requires an explicit configure time
flag to be passed to turn it on. The Fedora system test is
arbitrarily picked as the place to test it.
Signed-off-by: Daniel
On 22/10/2024 10.03, Daniel P. Berrangé wrote:
On Tue, Oct 22, 2024 at 07:31:49AM +0200, Thomas Huth wrote:
On 21/10/2024 19.02, Daniel P. Berrangé wrote:
The AF_ALG crypto integration for Linux is not being tested in
any CI scenario. It always requires an explicit configure time
flag to be pas
On Tue, Oct 22, 2024 at 07:31:49AM +0200, Thomas Huth wrote:
> On 21/10/2024 19.02, Daniel P. Berrangé wrote:
> > The AF_ALG crypto integration for Linux is not being tested in
> > any CI scenario. It always requires an explicit configure time
> > flag to be passed to turn it on. The Fedora system
On 21/10/2024 19.02, Daniel P. Berrangé wrote:
The AF_ALG crypto integration for Linux is not being tested in
any CI scenario. It always requires an explicit configure time
flag to be passed to turn it on. The Fedora system test is
arbitrarily picked as the place to test it.
Signed-off-by: Danie
On 21/10/24 14:02, Daniel P. Berrangé wrote:
The AF_ALG crypto integration for Linux is not being tested in
any CI scenario. It always requires an explicit configure time
flag to be passed to turn it on. The Fedora system test is
arbitrarily picked as the place to test it.
Signed-off-by: Daniel
The AF_ALG crypto integration for Linux is not being tested in
any CI scenario. It always requires an explicit configure time
flag to be passed to turn it on. The Fedora system test is
arbitrarily picked as the place to test it.
Signed-off-by: Daniel P. Berrangé
---
.gitlab-ci.d/buildtest.yml |
