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

sbus_codegen_tests leaves processes running #3389

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

sbus_codegen_tests leaves processes running #3389

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2347

  • Created at 2014-06-02 19:40:51 by nkondras
  • Closed as Fixed
  • Assigned to pbrezina

Executing "CK_FORK=no .libs/lt-sbus_codegen_tests" succeeds, but leaves three background processes running, as such:

nkondras 32644  0.0  0.1 107616  1888 pts/0    S    20:32   0:00 /home/nkondras/projects/fedorahosted.org/sssd/x86_64/.libs/lt-sbus_codegen_tests
nkondras 32645  0.0  0.1 107616  1904 pts/0    S    20:32   0:00 /home/nkondras/projects/fedorahosted.org/sssd/x86_64/.libs/lt-sbus_codegen_tests
nkondras 32646  0.0  0.1 107616  1920 pts/0    S    20:32   0:00 /home/nkondras/projects/fedorahosted.org/sssd/x86_64/.libs/lt-sbus_codegen_tests

Each of them seems to be sleeping on an epoll wait as a gdb backtrace demonstrates:

#0  0x00007fc0b12df3a3 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fc0b438c083 in epoll_event_loop_once () from /lib64/libtevent.so.0
#2  0x00007fc0b438a6b7 in std_event_loop_once () from /lib64/libtevent.so.0
#3  0x00007fc0b4386f2d in _tevent_loop_once () from /lib64/libtevent.so.0
#4  0x000000000040262b in mock_server_child (data=0x1f93390) at ../src/tests/common_dbus.c:126
#5  0x00000000004027f6 in test_dbus_setup_mock (mem_ctx=0x1f8fd20, loop=0x0, init_fn=0x4052ba <pilot_test_server_init>, init_pvt_data=0x0) at ../src/tests/common_dbus.c:159
#6  0x0000000000408278 in test_get_basic_array_types (_i=0) at ../src/tests/sbus_codegen_tests.c:990
#7  0x00007fc0b17b213a in tcase_run_tfun_nofork.isra () from /lib64/libcheck.so.0
#8  0x00007fc0b17b23c6 in srunner_run () from /lib64/libcheck.so.0
#9  0x000000000040b7be in main (argc=1, argv=0x7fffd08c6858) at ../src/tests/sbus_codegen_tests.c:1399

Running the same command again leaves three more processes.

This interferes with CI runs as they use CK_FORK=no to speed up runs under
Valgrind and system soon begins to collect quite a lot of these processes.

Comments


Comment from pbrezina at 2014-06-04 12:51:17

Fields changed

owner: somebody => pbrezina
status: new => assigned


Comment from lslebodn at 2014-06-04 16:08:21

I think it can be related to fact that temporary directories are not removed after running sbus_codegen_test

sh-4.2$ ls -ldn /tmp/sssd-dbus*
ls: cannot access /tmp/sssd-dbus*: No such file or directory

sh-4.2$ ./sbus_codegen_tests 
Running suite(s): sbus_codegen
100%: Checks: 10, Failures: 0, Errors: 0
sh-4.2$ echo $?
0

sh-4.2$ ps
  PID TTY          TIME CMD
18511 pts/9    00:00:00 sh
18578 pts/9    00:00:00 ps

sh-4.2$ ls -ldn /tmp/sssd-dbus*
drwx------. 2 1000 1000 60 Jun  4 16:06 /tmp/sssd-dbus-tests.amj9tt
drwx------. 2 1000 1000 60 Jun  4 16:06 /tmp/sssd-dbus-tests.jR0BKh
drwx------. 2 1000 1000 60 Jun  4 16:06 /tmp/sssd-dbus-tests.RjyS15

cc: => lslebodn@redhat.com


Comment from pbrezina at 2014-06-05 11:20:26

Yes, except it is the opposite - the fact that the directories are not removed is related to this :-)

patch: 0 => 1


Comment from nkondras at 2014-06-05 11:41:39

Thanks a lot, Pavel!


Comment from dpal at 2014-06-05 15:26:29

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.0
rhbz: => 0


Comment from jhrozek at 2014-06-18 14:58:16

resolution: => fixed
status: assigned => closed


Comment from nkondras at 2017-02-24 14:38:09

Metadata Update from @nkondras:

  • Issue assigned to pbrezina
  • Issue set to the milestone: SSSD 1.12.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants