Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Static workflow #7

Closed
wants to merge 38 commits into from
Closed

Static workflow #7

wants to merge 38 commits into from

Conversation

Amulyam24
Copy link
Owner

No description provided.

@Amulyam24 Amulyam24 closed this Dec 6, 2023
@Amulyam24 Amulyam24 reopened this Dec 6, 2023
@Amulyam24 Amulyam24 force-pushed the static branch 5 times, most recently from a438f7f to 695a2d5 Compare December 13, 2023 09:50
Combinations of network features were tested:

- None
- virtio-net
- vhost-net
- vhost-user-net
- virtio-net,vhost-net
- vhost-net,vhost-user-net
- virtio-net,vhost-user-net
- virtio-net,vhost-net,vhost-user-net

Fixes: kata-containers#8742

Signed-off-by: Xuewei Niu <[email protected]>
@Amulyam24 Amulyam24 force-pushed the static branch 3 times, most recently from 4976e5a to cdcaf84 Compare January 3, 2024 12:27
GabyCT and others added 18 commits January 3, 2024 17:14
This PR improves the iperf3 cleanup to ensure all the components are
being deleted properly to avoid the random failures of leaving
the iperf3 clients on the kata metrics CI.

Fixes kata-containers#8765

Signed-off-by: Gabriela Cervantes <[email protected]>
As reported in kata-containers#8767, we have found that the root cause is that rust-vmm's vmm-sys-utils
introduce a new release 0.12.1 and dbs-pci rely on rust-vmm's vfio-ioctls which uses >=
to declare vmm-sys-utils so it automatically upgrade vmm-sys-utils to 0.12.1.
That's how two different versions of vmm-sys-utils is introduced and this breaks the compilation.

In order to fix this and also avoid future problems, we introduce Cargo.lock file to dbs crates.

fixes: kata-containers#8770

Signed-off-by: Chao Wu <[email protected]>
In order to avoid rust-vmm upstream change breaks Dragonball
compilation, we introduce Cargo.lock to dbs crates.

fixes: kata-containers#8770

Signed-off-by: Chao Wu <[email protected]>
In order to avoid rust-vmm upstream change breaks Dragonball
compilation, we introduce Cargo.lock to dbs crates.

fixes: kata-containers#8770

Signed-off-by: Chao Wu <[email protected]>
As the StratoVirt VMM has been added, we can update the docs
and make some intoduction to StratoVirt, thus users can know more
about the hypervisor choices.

Fixes: kata-containers#8645

Signed-off-by: Zhigang Wang <[email protected]>
Signed-off-by: Liu Wenyuan <[email protected]>
dbs-pci: introduce Cargo.lock to prevent the influence from upstream
- `ttrpc` from `0.7.1` to `0.8`.

Fixes: kata-containers#8756

Signed-off-by: Xuewei Niu <[email protected]>
- `ttrpc` from `0.7.1` to `0.8`.

Fixes: kata-containers#8756

Signed-off-by: Xuewei Niu <[email protected]>
- `ttrpc` from `0.7.1` to `0.8`.
- `containerd-shim-protos` from `0.3.0` to `0.6.0`.

Fixes: kata-containers#8756

Signed-off-by: Xuewei Niu <[email protected]>
- `ttrpc` from `0.7.1` to `0.8`.

Fixes: kata-containers#8757

Signed-off-by: Xuewei Niu <[email protected]>
…inerd-shim-protos

runtime-rs|agent|protocols|agent-ctl: Bump ttrpc and containerd-shim-protos versions
dragonball: Fix compilation issue without all net features
…r_stratoVirt_VMM

docs: Update docs for new StratoVirt VMM introduction
Don't release the lock between is_allowed and set_policy calls,
because the policy might change in between these calls.

Also, move more policy code into policy.rs.

Fixes: kata-containers#8734

Signed-off-by: Dan Mihai <[email protected]>
This PR adds the qemu-experimental hypervisor in the function to
kill kata components.

Fixes kata-containers#8775

Signed-off-by: Gabriela Cervantes <[email protected]>
tests: Add hypervisor component to kill kata components function
jongwu and others added 14 commits January 9, 2024 13:14
This is to add a runner for arm64 to the workflow.

Signed-off-by: Jianyong Wu <[email protected]>
PathBuf here is only used for x86.

Signed-off-by: Jianyong Wu <[email protected]>
As part of the CI migration from Jenkins to GitHub Action, a CI job named
`kata-containers-2.0-ubuntu-s390x-unit-PR` is covered by the static check.
This commit is to enable the check for s390x by incorporating a runner
`s390x` with the corresponding workflow.

Fixes: kata-containers#8482

Signed-off-by: Hyounggyu Choi <[email protected]>
If `yq_path` is set to `/usr/local/bin/yq`, there could be a situation
where the `yq` cannot be installed without `sudo`.
This commit handles the situation by putting `sudo` in front of `curl`
and `chmod`, respectively.

Signed-off-by: Hyounggyu Choi <[email protected]>
Some linting errors were identified during the enablement of `make check`.
These have not been found by the Jenkins CI job because `make test` was
only triggered.

The errors for the `agent` occurs under the s390x specific tests while
the other ones for the `kata-ctl` are the architecture-specific code.

This commit is to fix those errors.

Signed-off-by: Hyounggyu Choi <[email protected]>
At the moment, a project `dragonball` and `runtime-rs` does not support
for s390x. During the enablement, some errors due to the misconfiguration
of Makefile for `make check` and `make vendor` were identified.

This is to skip the build for the affected target of the projects.

Signed-off-by: Hyounggyu Choi <[email protected]>
It was observed that a tmporary file `/tmp/kata_hybrid_vsock02.hvsock`
for test_setup_hvsock_failed() is not removed from time to time.
This leads to a test failure for the same test next time due to the
file permission on a self-hosted runner.
This commit is to explicitely delete the file before the check starts.

Signed-off-by: Hyounggyu Choi <[email protected]>
By convention the caller of tools/packaging/kernel/build-kernel.sh changes
the script behavior by passing arguments, whereas, for measured rootfs
it has used an environment variable (MEASURED_ROOTFS). This refactor
the script so that the caller now must pass the "-m" argument to enable
the build of the kernel with measured rootfs support.

Fixes kata-containers#6674
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
This PR adds ppc64le runner to the static-checks workflow.

Signed-off-by: Amulyam24 <[email protected]>
Since dragonball is not currently supported on ppc64le, skip running the targets for static-checks.

Signed-off-by: Amulyam24 <[email protected]>
A few CPU related test cases were failing as the version was being verified against Power8 while the CI machine is Power9.

Fixes: kata-containers#5531

Signed-off-by: Amulyam24 <[email protected]>
This minor PR removes the extra space in the makefiles.

Signed-off-by: Amulyam24 <[email protected]>
kata-ctl currently fails to build on ppc64le. Skip it for running static checks and the issues will be fixed and tracked in a seperate issue.

Signed-off-by: Amulyam24 <[email protected]>
@Amulyam24 Amulyam24 force-pushed the static branch 3 times, most recently from 6eea606 to 1d4f116 Compare January 9, 2024 08:46
@Amulyam24 Amulyam24 closed this Jan 9, 2024
@Amulyam24 Amulyam24 reopened this Jan 18, 2024
@Amulyam24 Amulyam24 force-pushed the static branch 8 times, most recently from a9ef0fa to b0c8d22 Compare January 18, 2024 12:39
- test_volume_capacity_stats : verify the file block size against the fetched size via statfs()
- test_reseed_rng: Correct the request codes for RNDADDTOENTCNT and RNDRESEEDCRNG when platform is ppc64le

Signed-off-by: Amulyam24 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.