Skip to content

Commit 93e53c6

Browse files
Alexandra Iordacheandreeaflorescu
authored andcommitted
buildkite: use rust-vmm-ci pipeline from submodule
Signed-off-by: Alexandra Iordache <aghecen@amazon.com>
1 parent 42aea56 commit 93e53c6

File tree

5 files changed

+1
-367
lines changed

5 files changed

+1
-367
lines changed

.buildkite/rust-vmm-ci-pipeline.yml

Lines changed: 0 additions & 176 deletions
This file was deleted.

README.md

Lines changed: 1 addition & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ cargo build
1818
Our Continuous Integration (CI) pipeline is implemented on top of
1919
[Buildkite](https://buildkite.com/).
2020
For the complete list of tests, check our
21-
[CI pipeline](https://buildkite.com/rust-vmm/vm-virtio-ci).
21+
[CI pipeline](https://buildkite.com/rust-vmm/rust-vmm-ci).
2222

2323
Each individual test runs in a container. To reproduce a test locally, you can
2424
use the dev-container on both x86 and arm64.
@@ -32,57 +32,6 @@ cd linux-loader/
3232
cargo test
3333
```
3434

35-
### Test Profiles
36-
37-
The integration tests support two test profiles:
38-
- **devel**: this is the recommended profile for running the integration tests
39-
on a local development machine.
40-
- **ci** (default option): this is the profile used when running the
41-
integration tests as part of the the Continuous Integration (CI).
42-
43-
The test profiles are applicable to tests that run using pytest. Currently only
44-
the [coverage test](tests/test_coverage.py) follows this model as all the other
45-
integration tests are run using the
46-
[Buildkite pipeline](https://buildkite.com/rust-vmm/vm-virtio-ci).
47-
48-
The difference between is declaring tests as passed or failed:
49-
- with the **devel** profile the coverage test passes if the current coverage
50-
is equal or higher than the upstream coverage value. In case the current
51-
coverage is higher, the coverage file is updated to the new coverage value.
52-
- with the **ci** profile the coverage test passes only if the current coverage
53-
is equal to the upstream coverage value.
54-
55-
Further details about the coverage test can be found in the
56-
[Adaptive Coverage](#adaptive-coverage) section.
57-
58-
### Adaptive Coverage
59-
60-
The line coverage is saved in [tests/coverage](tests/coverage). To update the
61-
coverage before submitting a PR, run the coverage test:
62-
63-
```bash
64-
docker run -it \
65-
--security-opt seccomp=unconfined \
66-
--volume $(pwd):/linux-loader \
67-
rustvmm/dev:v2
68-
cd linux-loader/
69-
pytest --profile=devel tests/test_coverage.py
70-
```
71-
72-
If the PR coverage is higher than the upstream coverage, the coverage file
73-
needs to be manually added to the commit before submitting the PR:
74-
75-
```bash
76-
git add tests/coverage
77-
```
78-
79-
Failing to do so will generate a fail on the CI pipeline when publishing the
80-
PR.
81-
82-
**NOTE:** The coverage file is only updated in the `devel` test profile. In
83-
the `ci` profile the coverage test will fail if the current coverage is higher
84-
than the coverage reported in [tests/coverage](tests/coverage).
85-
8635
### bzImage test
8736

8837
As we don't want to distribute an entire kernel bzImage, the `load_bzImage` test is ignored by

tests/conftest.py

Lines changed: 0 additions & 28 deletions
This file was deleted.

tests/coverage

Lines changed: 0 additions & 1 deletion
This file was deleted.

tests/test_coverage.py

Lines changed: 0 additions & 110 deletions
This file was deleted.

0 commit comments

Comments
 (0)