iovisor / iovisor/bcc

Multiple tests in make-test failing on v0.3.0-87-ge2a0377

Open
#1,101 7 comments 1 reaction 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
10d 4h
Merged PRs (30d)
3

Description

After building bcc from master at e2a037779c2b8c6ca83648699f0af670668a92b5 with all optional packages installed, `make test` failed in a number of tests.

Environment:
* Slackware64-current (as of April 7th, 2017)
* Linux kernel 4.11.0-rc3 (most/all things included for verbose tracing)
* GCC-5.4.0
* Clang-4.0.0
* Python-2.7.13
* Lua-5.1.5
* LuaJIT-2.0.4
* Netperf-2.6.0
* iperf-2.0.5
* netaddr-0.7.19

Test summary:

Total Test time (real) = 306.91 sec

The following tests FAILED:
3 - test_libbcc (Failed)
7 - py_test_xlate1_c (Failed)
8 - py_test_call1 (Failed)
15 - py_test_brb (Failed)
17 - py_test_clang (Failed)
18 - py_test_histogram (Failed)
24 - py_test_perf_event (Failed)
28 - py_test_tools_smoke (Failed)
Errors while running CTest

The `Makefile` was changed to include `-VV` as argument to `ctest`. I've included the relevant snippet from `dmesg`, and the output for `make test`.

[dmesg.txt](https://github.com/iovisor/bcc/files/906198/dmesg.txt)
[make_test.txt](https://github.com/iovisor/bcc/files/906197/make_test.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Makefile and the attached dmesg.txt and make_test.txt files, then reproduce make test at commit e2a037779c2b8c6ca83648699f0af670668a92b5 in the listed environment. Trace the eight named CTest failures and verify that the failing tests are resolved and make test completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux, python
Domain
build-system, operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.