URL:
https://github.com/SSSD/sssd/pull/461
Title: #461: responder: Fix talloc hierarchy in sized_output_name
lslebodn commented:
"""
On (29/11/17 14:20), fidencio wrote:
I can see one failure in our internal CI:
```
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M 5b05f2b1276141ae922d65eae7807749 -D
/var/lib/mock/fedora-27-x86_64/root -a --private-network --setenv=TERM=vt100
--setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock
--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf
"\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$
--setenv=LANG=en_US.UTF-8 -u mockbuild bash --login -c /usr/bin/rpmbuild -bb --target
x86_64 --nodeps /builddir/build/SPECS/sssd.spec
```
This failure happened on f27 system but is not related to this patch at all. For all other
systems, CI passed:
http://vm-031.${abc}/logs/job/81/98/summary.html
That is just not ideal report from mock. But build log shows
it was a known unit test failure.
```
FAIL: find_uid-tests
====================
Running suite(s): find_uid
(Wed Nov 29 14:34:21:085901 2017) [sssd] [get_uid_from_pid] (0x0020): read failed [3][No
such process].
(Wed Nov 29 14:34:21:086019 2017) [sssd] [get_active_uid_linux] (0x0020): get_uid_from_pid
failed.
66%: Checks: 3, Failures: 1, Errors: 0
src/tests/find_uid-tests.c:78:F:find_uid:test_get_uid_table:0: get_uid_table failed.
FAIL find_uid-tests (exit status: 1)
```
LS
"""
See the full comment at
https://github.com/SSSD/sssd/pull/461#issuecomment-348191570