| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-01-28 | tests: enable gir static lib on cygwin | Dylan Baker | |
| Where it is now working. | |||
| 2024-03-17 | tests: 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. | |||
| 2021-07-13 | Add expected skip annotations for non-linux CI runs to framework tests | Jon Turney | |
| 2021-07-07 | Annotate framework tests with where they are expected to skip | Jon Turney | |
| Remove hard-coded framework test skip logic in skippable(), instead annotate test.json with environments in which skip is expected. (Mainly this is done with by testing the value of MESON_CI_JOBNAME now set for linux jobs) | |||
| 2020-11-13 | gnome: Handle libraries that are not in the current build dir | Sam Thursfield | |
| The generate_gir() function previously assumed all library inputs were in the current build dir. This would fail if they weren't. | |||
