-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
t5000-valgrind test fails on Jetson Nano #3808
Comments
Ah thanks for reporting this Bryan. Since the failure is down in libev (which is vendored in flux-core) probably we just need to add the recommended suppression. It's not the first one for libev. Could you verify that this shuts up the failure? diff --git a/t/valgrind/valgrind.supp b/t/valgrind/valgrind.supp
index 00909e353..d963ab408 100644
--- a/t/valgrind/valgrind.supp
+++ b/t/valgrind/valgrind.supp
@@ -123,3 +123,13 @@
fun:hwloc_topology_load
...
}
+{
+ <issue_3808>
+ Memcheck:Param
+ epoll_ctl(event)
+ fun:epoll_ctl
+ fun:epoll_modify
+ fun:fd_reify
+ fun:ev_run
+ ...
+} On the other failure, if you have time, please open another bug. The way to run the python tests standalone is e.g.
|
I get this when running that command: $ diff --git a/t/valgrind/valgrind.supp b/t/valgrind/valgrind.supp
diff: unrecognized option '--git'
diff: Try 'diff --help' for more information Everything seems to indicate that I should run the following after committing the state of my code and it does that: $ git diff t/valgrind/valgrind.supp
$ But it yields no output. Is the suppression beyond v0.28.0 of flux-core? |
I'm going to redownload and build a fresh copy of v0.28.0 and see if the tests hang again before submitting that ticket. Running the python test manually ran fine and I get that same output. |
Oops, sorry, that's a patch you could cut and paste into a file, say
from the top level of the flux-core source tree. |
Patch applied, now shows this in the output: ...
make[2]: Nothing to be done for 't5000-valgrind.t'.
...
PASS: t5000-valgrind.t 1 - valgrind reports no new errors on 2 broker run
... So guess that's a success in squashing the failure for that test. Thanks, will let you know if it still hangs again and submit a new ticket if it does. |
Problem: a new valgrind test failure was encountered on aarch64, Ubuntu 20.04.2 LTS and also the official Jetson Ubuntu 18.04: ==1705645== Syscall param epoll_ctl(event) points to uninitialised byte(s) ==1705645== at 0x4BDFE38: epoll_ctl (syscall-template.S:78) ==1705645== by 0x48B37EF: epoll_modify (ev_epoll.c:96) ==1705645== by 0x48B4F57: fd_reify (ev.c:2166) ==1705645== by 0x48B4F57: ev_run (ev.c:3677) ==1705645== by 0x48B4F57: ev_run (ev.c:3623) ==1705645== by 0x48824FF: flux_reactor_run (reactor.c:126) ==1705645== by 0x1113BF: main (broker.c:449) ==1705645== Address 0x1ffefff22c is on thread 1's stack ==1705645== in frame #1, created by epoll_modify (ev_epoll.c:72) Since this is apparently internal to libev, add a suppression. Fixes flux-framework#3808
Problem: a new valgrind test failure was encountered on aarch64, Ubuntu 20.04.2 LTS and also the official Jetson Ubuntu 18.04: ==1705645== Syscall param epoll_ctl(event) points to uninitialised byte(s) ==1705645== at 0x4BDFE38: epoll_ctl (syscall-template.S:78) ==1705645== by 0x48B37EF: epoll_modify (ev_epoll.c:96) ==1705645== by 0x48B4F57: fd_reify (ev.c:2166) ==1705645== by 0x48B4F57: ev_run (ev.c:3677) ==1705645== by 0x48B4F57: ev_run (ev.c:3623) ==1705645== by 0x48824FF: flux_reactor_run (reactor.c:126) ==1705645== by 0x1113BF: main (broker.c:449) ==1705645== Address 0x1ffefff22c is on thread 1's stack ==1705645== in frame flux-framework#1, created by epoll_modify (ev_epoll.c:72) Since this is apparently internal to libev, add a suppression. Fixes flux-framework#3808
So have flux-security & flux-core building and installing fine on the Jetson Nano 4GB model B01. I've tried an official Jetson Ubuntu image (18.04) and a custom image now running Ubuntu 20.04.2 LTS.
Using the manual verbose run method mentioned in #3093 get the following output. This is the only error I got the first time I ran make check; however, now subsequent runs the check hangs on the test python/t0007-watchers which I'm unsure what's causing that or how to run that one manually.
Few system details in case they're useful:
Linux version 4.9.201-tegra (buildbrain@mobile-u64-5294-d8000) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #1 SMP PREEMPT Fri Feb 19 08:40:32 PST 2021
Python 3.8.10
Valgrind 3.15.0
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
GNU Make 4.2.1 Built for aarch64-unknown-linux-gnu
Flux-Security v0.4.0
Flux-Core v0.28.0
The text was updated successfully, but these errors were encountered: