You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature testing of tracee is split between integration tests and e2e tests. Integration tests runs tracee instances through procedural code calls, whereas e2e runs full tracee instances with corresponding policy and signatures. While e2e tests cover many kernels and therefore both main cpu architectures (x86_64 and arm64), integration tests which arguably test even more internal mechanisms do not have this coverage.
Solution
We should mirror these tests to cover arm64. This can be done most simply by duplicating the job and making sure it runs on an arm64 machine. We may want to make this change to unit tests as well.
The text was updated successfully, but these errors were encountered:
Background
Feature testing of tracee is split between integration tests and e2e tests. Integration tests runs tracee instances through procedural code calls, whereas e2e runs full tracee instances with corresponding policy and signatures. While e2e tests cover many kernels and therefore both main cpu architectures (x86_64 and arm64), integration tests which arguably test even more internal mechanisms do not have this coverage.
Solution
We should mirror these tests to cover arm64. This can be done most simply by duplicating the job and making sure it runs on an arm64 machine. We may want to make this change to unit tests as well.
The text was updated successfully, but these errors were encountered: