dsg/vhost-device
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
vhost-device/.buildkite
History
Dorinda Bassey 1a1d1e2685 vhost-device-gpu: update rutabaga_gfx, CI and README 
- Updated rutabaga_gfx to 0.1.62, which now requires env vars to
use system-provided virglrenderer and minigbm libraries for both
gfxstream and virglrenderer GPU backends.

- Updated README with new build instructions using
  CROSVM_USE_SYSTEM_* env vars.
- Update transfer_read to use the latest rutabaga_gfx changes

- The GNU CI builds and tests for vhost-device-gpu currently fail
because they try to build against the vendored virglrenderer tree.
Locally we already build with CROSVM_USE_SYSTEM_* env vars, so
mirror that setup in CI as well.

Signed-off-by: Dorinda Bassey <dbassey@redhat.com>
2025-09-02 12:09:54 +02:00
..
main-tests.json vhost-device-gpu: update rutabaga_gfx, CI and README 2025-09-02 12:09:54 +02:00
README.md buildkite: add main-tests.json 2025-02-11 19:51:01 +05:30
staging-tests.json Move vhost-user-gpu from staging to main directory 2025-02-14 10:15:52 +02:00

README.md

buildkite custom pipelines

This folder contains the custom pipelines for this repository.

If we add a new pipeline we need to enable it in https://buildkite.com/rust-vmm/vhost-device-ci/steps

Custom pipelines currently defined are:

  • main-tests.json This is based on rust-vmm-ci/.buildkite/test_description.json. We have an internal version, because we have several applications that have dependencies that don't work very well on musl, so it's easier to manage CI by having our own internal pipeline.

  • staging-tests.json This is based on main-tests.json. We should keep staging-tests.json aligned with it as much as possible to make sure we don't notice any difference in CI when we move a crate from the staging to the main workspace.