-
Notifications
You must be signed in to change notification settings - Fork 58
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
All tests hang on alpha #200
Comments
SSH access would be useful indeed, as there are no Debian porter boxes for alpha. my SSH key As a first diagnosis, can you please run a single test in verbose mode, to see how far that gets? (in the build tree):
Does this simplest possible test case work?
|
Nope, just tried - both commands just hang with no output. They don't respond to SIGINT either, have to kill them. I've added you as a user - should be able to log in to martinpitt [at] alphadev [dot] matoro [dot] tk (IPv6 only). Let me know if you're able to take a look - thank you so much!! |
@matoro Thanks! I can log in, but umockdev's build dependencies are missing. I started a tmux session if you want to attach/have a look. First error:
Could you install these? Or is there some kind of build chroot on that box which I can access without root? |
Oops, sorry - gobject-introspection is installed now. Vala was actually already installed, but Gentoo does not symlink the plain |
Initial notes:
This locks up hard, not even Control-C or Control-\ help. Needs to be SIGKILLed. This makes gdb unusable as well, and strace isn't installed. @matoro, installing strace would be much appreciated!
that works fine.
that segfaults immediately. This once again means that I can't run gdb inside of umockdev-run, and running it outside is rather pointless as the only backtrace that it gives me is for the Same conundrum with a core dump -- dumping "outside" isn't useful, and dumping "inside" with
crashes before bash loads properly. So it seems this needs some fine-grained printf debugging.. The closest that I can get to is the struct statx st;
res = _statx(AT_FDCWD, path, 0, STATX_MODE, &st); doesn't help either. Disabling the whole path_exists() check also doesn't help; this smells like a memory corruption that happened before already. |
@matoro , can you please install strace and valgrind? This is a really hairy one, I'm afraid.. |
Normally I have strace installed, 5.19 is just blocked by strace/strace#220 at the moment. But I just made a local repo and installed 5.18 from it for now. Valgrind unfortunately requires platform-specific code, so there is of course no support for most of the more obscure platforms: https://valgrind.org/info/platforms.html Let me know if there is anything else that would help the investigation. Thank you so much for looking at this! |
Ah right, no valgrind.. Perhaps there's something simpler like electric-fence. I ran with strace, but this is inconclusive. With printf debugging and
it keeps hanging when calling the real glibc functions like access() and open(), and I don't know how to sensibly debug that. OTOH, when calling If someone has another idea how to debug this, I'm all ears -- but there's only so much time I can throw at this, sorry. |
Hi, in both of the two extant distros supporting alpha (Debian & Gentoo) all tests in the test suite timeout. I tried increasing the meson timeout past the 150-second limit but the tests hung indefinitely.
Test log from my run (Gentoo):
Downstream Gentoo bug: https://bugs.gentoo.org/805083
Debian: https://buildd.debian.org/status/fetch.php?pkg=umockdev&arch=alpha&ver=0.17.13-1&stamp=1663045653&raw=1
(build history at https://buildd.debian.org/status/logs.php?pkg=umockdev&arch=alpha )
I have real hardware available that I can provide access to if it would be helpful for debugging. Thanks!
The text was updated successfully, but these errors were encountered: