Re: [iovisor-dev] Failing bcc tests on xenial with 4.13 kernel

Great! Thanks for the info! Mike On Wed, Mar 7, 2018 at 10:47 PM, Y Song wrote: > Your workaround looks good. Basically, you can put the workaround in > for 4.13 for any tools which references > task_struct construct. > > The bcc issue https://github.com/iovisor/bcc/issues/1492 has more details

Re: [iovisor-dev] Failing bcc tests on xenial with 4.13 kernel

Your workaround looks good. Basically, you can put the workaround in for 4.13 for any tools which references task_struct construct. The bcc issue https://github.com/iovisor/bcc/issues/1492 has more details. It is an issue for 4.13. it is an issue for 4.14 original release, but the patch is ported

Re: [iovisor-dev] Failing bcc tests on xenial with 4.13 kernel

Y Song, thank you very much for your detailed feedback. Let me focus on the specific wakeuptime.py failure since that seems to be my biggest blocker at the moment: > File "../../tools/wakeuptime.py", line 216, in > > print("%-16s %s" % ("target:", k.target.decode())) > > UnicodeDecodeE

Re: [iovisor-dev] Failing bcc tests on xenial with 4.13 kernel

On Tue, Mar 6, 2018 at 11:12 PM, Mike Percy via iovisor-dev wrote: > Hi bcc devs, > > I am trying to get the bcc tests to pass on the master branch on top of > Ubuntu 16.04 running the HWE kernel, which is version 4.13.0-36-generic. I'm > compiling bcc using LLVM 6.0 (yes, it's now available) from

[iovisor-dev] Failing bcc tests on xenial with 4.13 kernel

Hi bcc devs, I am trying to get the bcc tests to pass on the master branch on top of Ubuntu 16.04 running the HWE kernel, which is version 4.13.0-36-generic. I'm compiling bcc using LLVM 6.0 (yes, it's now available) from the llvm.org APT repo. H