Skip to content
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

tests are broken/timeout #2501

Open
craftyguy opened this issue Sep 5, 2020 · 0 comments
Open

tests are broken/timeout #2501

craftyguy opened this issue Sep 5, 2020 · 0 comments
Labels

Comments

@craftyguy
Copy link

 * Nemo version (nemo --version): git master
 * Is issue with desktop or windowed nemo?: n/a
 * Distribution - (Mint 17.2, Arch, Fedora 25, etc...): Alpine Linux, Arch Linux
 * Graphics hardware *and* driver used: Mali and Intel graphics, Mesa 20.1.5
 * 32 or 64 bit: amd64 and aarch64

Issue
Tests are broken, and/or timeout:

❯ meson test

...
2/4 Search Engine test   TIMEOUT        30.01s

--- command ---
18:52:27 /tmp/nemo/output/test/test-nemo-search-engine
-------

3/4 Directory Async test TIMEOUT        30.01s

--- command ---
18:52:27 /tmp/nemo/output/test/test-nemo-directory-async
-------

4/4 Copy test            FAIL           0.07s (exit status 1)

--- command ---
18:52:27 /tmp/nemo/output/test/test-nemo-copy
--- stdout ---
Usage test-copy <sources...> <dest dir>
-------


Ok:                 1
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            0
Timeout:            2

The test-nemo-copy test is missing arguments in meson.build. When arguments are supplied, it hangs indefinitely.

Output from strace where it's hanging/polling continuously:

ppoll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}], 3, {tv_sec=4, tv_nsec=990000000}, NULL, 8) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47335, tv_nsec=6466169}) = 0
futex(0xffff82d5dbe0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xffff82d5dbd0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xffff82d5db80, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47335, tv_nsec=7333302}) = 0
futex(0xffff83414d90, FUTEX_WAKE_PRIVATE, 1) = 1
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}], 3, {tv_sec=0, tv_nsec=0}, NULL, 8) = 1 ([{fd=4, revents=POLLIN}], left {tv_sec=0, tv_nsec=0})
read(4, "\1\0\0\0\0\0\0\0", 16)         = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47335, tv_nsec=8925981}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47335, tv_nsec=9210067}) = 0
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}], 3, {tv_sec=4, tv_nsec=991000000}, NULL, 8) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47340, tv_nsec=6564202}) = 0
futex(0xffff82d5dbe0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xffff82d5dbd0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xffff82d5db80, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xffff83414d90, FUTEX_WAKE_PRIVATE, 1) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47340, tv_nsec=7856546}) = 0
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}], 3, {tv_sec=0, tv_nsec=0}, NULL, 8) = 1 ([{fd=4, revents=POLLIN}], left {tv_sec=0, tv_nsec=0})
read(4, "\1\0\0\0\0\0\0\0", 16)         = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47340, tv_nsec=9823562}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=47340, tv_nsec=10118148}) = 0
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)

The search engine and directory async tests report 'finish' in the log but timeout. I'm not sure why they don't return/complete.

Steps to reproduce

Build tests, and run with meson test

Expected behaviour

Tests finish and pass.

Other information

@icarter09 icarter09 added the BUG label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants