ci: Use cargo nextest as the test runner and export junit reports
Close #519 (closed)
Merge request reports
Activity
added CI label
- Resolved by Jordan Petridіs
Maybe we can get rid of
warning: `/builds/alatiera/gstreamer-rs/.cargo/config` is deprecated in favor of `config.toml` note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
while we're at it :)
- Resolved by Jordan Petridіs
Does this actually work? There does not seem to be a report in gitlab
Is it maybe overwriting the report with every
cargo nextest
call, so the report is empty because the last one doesn't actually run any tests?
added 36 commits
-
1200d92c...6a04bad1 - 35 commits from branch
gstreamer:main
- 2078eb6b - ci: Use cargo nextest as the test runner and export junit reports
-
1200d92c...6a04bad1 - 35 commits from branch
added 1 commit
- 5f6da9e6 - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- 627cb89d - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- f5aee2aa - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- eacf2589 - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- 6dd0cd6a - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- 1f5fc350 - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- fada610f - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- 80920a32 - ci: Use cargo nextest as the test runner and export junit reports
added 1 commit
- e1a1b293 - ci: Specify the number of build jobs on windows
added 1 commit
- d306ecc1 - ci: Specify the number of build jobs on windows
plugins-rs counterpart gst-plugins-rs!1840 (merged)