testsuite: add valgrind suppression for libev on aarch64 #3809
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 #3808