| Message ID | 20191206140012.15517-3-wainersm@redhat.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | tests/acceptance: Add boot vmlinux test | expand |
Wainer dos Santos Moschetta <wainersm@redhat.com> writes: > The tests/acceptance/pvh.py test builds the Linux kernel > at runtime so it needs dependencies installed in the > container. Current used container image misses only > libelf-dev, which is then added with this change. Hmm I'm not sure about this. Do we really want to building a whole kernel inside Travis? There must be stable PVH aware distro kernels we could use for the CI? > > Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com> > --- > .travis.yml | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/.travis.yml b/.travis.yml > index 445b0646c1..d8fe98eb63 100644 > --- a/.travis.yml > +++ b/.travis.yml > @@ -277,6 +277,8 @@ matrix: > - python3.5-venv > - tesseract-ocr > - tesseract-ocr-eng > + # Additional kernel build dependencies > + - libelf-dev > > > # Using newer GCC with sanitizers
diff --git a/.travis.yml b/.travis.yml index 445b0646c1..d8fe98eb63 100644 --- a/.travis.yml +++ b/.travis.yml @@ -277,6 +277,8 @@ matrix: - python3.5-venv - tesseract-ocr - tesseract-ocr-eng + # Additional kernel build dependencies + - libelf-dev # Using newer GCC with sanitizers
The tests/acceptance/pvh.py test builds the Linux kernel at runtime so it needs dependencies installed in the container. Current used container image misses only libelf-dev, which is then added with this change. Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com> --- .travis.yml | 2 ++ 1 file changed, 2 insertions(+)