summaryrefslogtreecommitdiff
path: root/test cases/frameworks/24 libgcrypt
AgeCommit message (Collapse)Author
2024-12-06libgcrypt-config is no more on ubuntu-rollingPaolo Bonzini
2024-08-06CI: mark arch as skipping frameworks/libgcryptEli Schwartz
They have recently upgraded to libgcrypt 1.11 and it has inherited the gpg suite migration to pkg-config.
2024-07-02CI: mark cygwin as skipping frameworks/libgcryptEli Schwartz
They have recently upgraded to libgcrypt 1.11 and it has inherited the gpg suite migration to pkg-config.
2024-03-17tests: rename skip_on_jobname to expect_skip_on_jobname and skip_on_os to ↵Christoph Reiter
expect_skip_on_os The test.json format currently has three keys related to skipping tests: * `skip_on_jobname` * `skip_on_os` * `skip_on_env` While `skip_on_env` marks the test itself as skipped, i.e. they don't get run when the conditions are met, the other two skip options are just marking the test as "expected to be skipped" if the conditions apply, i.e. they want to see `MESON_SKIP_TEST` in the output and things will fail if that doesn't happen. They don't actually skip the tests as the names imply. To make this clearer rename the keys: * `skip_on_jobname` -> `expect_skip_on_jobname` * `skip_on_os` -> `expect_skip_on_os` `skip_on_env` stays the same, since that actually skips. The docs were also confused about this, so adjust that too.
2022-12-11CI: skip libgcrypt test on msys2Eli Schwartz
This is no longer implicitly installed due to libxslt. Actually though, we don't need to test this in order to ensure that the custom dependency works -- we have other jobs that test it, and the config-tool handling itself won't suddenly fail on msys2 specifically.
2021-07-13Add expected skip annotations for non-linux CI runs to framework testsJon Turney
2018-10-03Add custom libgcrypt dependency using libgcrypt-configPatrick Griffis
Fixes #3563