Open kbara opened 8 years ago
Odd, no I dont know why, will investigate...
My guess is that your kernel doesn't have support for some of these things and it is erroring (which should be skipped but its hard to check), but will look into it. Your kernel doesnt match your userspace, but that shouldnt matter.
So, the intent is that all the tests should pass (or be skipped)?
I've run the tests again, against the same ljsyscall version and master ( c8baf9e944cd3f20267d5a1303683807b01bdc59 ), with the same results. I'm still using the same kernel, but a 16.04 userspace now.
Ideally, but in many cases it is hard to know how a kernel will fail so this does happen. Are you using the standard 16.04 kernel? If so I can check what is happening.
On 10 Aug 2016 2:00 p.m., "kbara" notifications@github.com wrote:
So, the intent is that all the tests should pass (or be skipped)?
I've run the tests again, against the same ljsyscall version and master ( c8baf9e https://github.com/justincormack/ljsyscall/commit/c8baf9e944cd3f20267d5a1303683807b01bdc59 ), with the same results. I'm still using the same kernel, but a 16.04 userspace now.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/justincormack/ljsyscall/issues/197#issuecomment-238858837, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdcPBSgizckQtIHVCyvLc4FaYwEVmRYks5qectYgaJpZM4InoAz .
That wasn't the standard kernel, but I believe 4.4.0-34-generic is the standard kernel, and I get the same results with it as well.
Several tests fail on x86_64 linux, with and without sudo. Is this expected behaviour?
The following tests were run with 214550af0cac3d07eb6d25ef64d2a4309b8fba1b , on x86_64 with a 4.4.4-040404-generic kernel, and an Ubuntu 14.04 userspace.
Details: