Shall we freeze the development till #3463 is solved?
by Fabiano Fidêncio
People,
There's a test, part of our internal CI, recurrently failing in the
past few weeks:
=================================== FAILURES ===================================
_____________________________ test_add_remove_user _____________________________
Traceback (most recent call last):
File "/var/lib/jenkins/workspace/ci/label/debian_testing/src/tests/intg/test_enumeration.py",
line 418, in test_add_remove_user
ent.assert_passwd(ent.contains_only())
File "/var/lib/jenkins/workspace/ci/label/debian_testing/src/tests/intg/ent.py",
line 345, in assert_passwd
assert not d, d
AssertionError: list mismatch:
unexpected users found:
[{'dir': '/home/user',
'gecos': '2001',
'gid': 2000,
'name': 'user',
'passwd': '*',
'shell': '/bin/bash',
'uid': 2001}]
==================== 1 failed, 226 passed in 976.19 seconds ====================
There's already an open issue for this case:
https://pagure.io/SSSD/sssd/issue/3463 in order to track the issue.
So, as the subject says, shall we officially stop pushing patches till
we have this issue solved?
Best Regards,
--
Fabiano Fidêncio
6 years, 9 months
[sssd PR#345][opened] Improve the situation of recurrent failing CI tests
by fidencio
URL: https://github.com/SSSD/sssd/pull/345
Author: fidencio
Title: #345: Improve the situation of recurrent failing CI tests
Action: opened
PR body:
"""
Taking a look in our CI the latest issues we had were related to not waiting enough time in some sleep() that are around the tests code.
For a more detailed explanation, please, take a look on each patch of this small series.
Last 6 CI runs were successful (all triggered with these patches). There were still 5 runs to go, but those jobs were aborted without any kind of notice. :-\
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/345/head:pr345
git checkout pr345
6 years, 9 months