Accelerate unit_test_with_bcc about kepler HOT 3 CLOSED

• we have different tag used for different system.
• our code coverage, as unit test just focusing on kepler/kepler core logic but not each tag.
• for each build tag targeting with specific system/hardware, provider should keep eye on them self?
• if possible should we test with specific system/hardware? I suppose yes.
• Here comes the thing at unit test scope, as should we run the test base on a clean env or base on docker?

I want to do unit test with a clean env. which means we have to install bcc from zero.

• for container or not
  as unit test in different github action with docker build, if we just use base container, which means each time, it will use lates t base image on main branch but not the pr one. otherwise, to ensure we use the base image build by pr, it's seems we need to install bcc during docker build isn't we?

as summary, I suppose accelerate with docker means we need build docker image and use it to test ...
if we install bcc during docker image, what's different with install bcc in github agent?

from kepler.

The kepler base container has already installed bcc. No build is needed. It is the target environment where kepler runs. Aligning the CI setup to this environment is closer to what we need.

from kepler.

The kepler base container has already installed bcc. No build is needed. It is the target environment where kepler runs. Aligning the CI setup to this environment is closer to what we need.

I also checked bcc https://github.com/iovisor/bcc/blob/master/INSTALL.md#ubuntu---binary and ... as ubuntu's release for bcc is still out of date...

k... let's try to use base container to run the unit test.

from kepler.