The autobuild test system (on sn-devel-144) has detected an intermittent failing test in the current master tree.
The autobuild log of the failure is available here: https://git.samba.org/autobuild.flakey.sn-devel-144/2019-02-08-1527/flakey.log The failure seems to be in the "samba" suite, whose build logs are available here: https://git.samba.org/autobuild.flakey.sn-devel-144/2019-02-08-1527/samba.stderr https://git.samba.org/autobuild.flakey.sn-devel-144/2019-02-08-1527/samba.stdout The top commit at the time of the failure was: commit 87149445af26b8577566dfe5e311b32e3650c6e6 Author: Joe Guo <[email protected]> Date: Wed Jan 30 15:52:08 2019 +1300 s4/scripting/bin: open unicode files with utf8 encoding and write unicode string In files like `libcli/util/werror_err_table.txt` and `libcli/util/ntstatus_err_table.txt`, there were unicode quote symbols at line 6: ...(âthis documentationâ)... In `libcli/util/wscript_build`, it will run `gen_werror.py` and `gen_ntstatus.py` to `open` above files, read content from them and write to other files. When encoding not specified, `open` in both python 2/3 will guess encoding from locale. When locale is not set, it defaults to POSIX or C, and then python will use encoding `ANSI_X3.4-1968`. So, on a system locale is not set, `make` will fail with encoding error for both python 2 and 3: File "/home/ubuntu/samba/source4/scripting/bin/gen_werror.py", line 139, in main errors = parseErrorDescriptions(input_file, True, transformErrorName) File "/home/ubuntu/samba/source4/scripting/bin/gen_error_common.py", line 52, in parseErrorDescriptions for line in file_contents: File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 318: ordinal not in range(128) In this case, we have to use `io.open` with `encoding='utf8'`. However, then we got unicode strs and try to write them with other strs into new file, which means the new file must also open with utf-8 and all other strs have to be unicode, too. Instead of prefix `u` to all strs, a more easier/elegant way is to enable unicode literals for the python scripts, which we normally didn't do in samba. Since both `gen_werror.py` and `gen_ntstatus.py` are bin scripts and no other modules import them, it should be ok for this case. Signed-off-by: Joe Guo <[email protected]> Autobuild-User(master): Douglas Bagnall <[email protected]> Autobuild-Date(master): Fri Feb 8 06:34:47 CET 2019 on sn-devel-144 and the last 50 lines of the stdout log were: [787(4855)/853 at 1h53m18s] samba4.rpc.samr.large-dc.two(vampire_dc) [788(4858)/853 at 1h53m28s] samba4.rpc.echo(rodc) [789(4868)/853 at 1h53m32s] samba4.rpc.echo(rodc:local) [790(4878)/853 at 1h53m36s] samba4.rpc.echo.testallowed(rodc:local) [791(4888)/853 at 1h53m39s] samba4.rpc.echo.testdenied(rodc:local) [792(4898)/853 at 1h53m42s] samba4.blackbox.smbclient(rodc:local)(rodc:local) [793(4900)/853 at 1h53m44s] samba.tests.samba_tool.rodc(rodc:local) [794(4909)/853 at 1h54m14s] samba.blackbox.rpcclient_samlogon(rodc:local) [795(4913)/853 at 1h54m14s] samba.blackbox.rpcclient_samlogon_testallowed(rodc:local) [796(4917)/853 at 1h54m15s] samba.blackbox.rpcclient_samlogon_testdenied(rodc:local) [797(4921)/853 at 1h54m15s] samba4.drs.ridalloc_exop.python(vampire_dc)(vampire_dc) [798(4932)/853 at 1h59m55s] samba4.drs.samba_tool_drs.python(vampire_dc)(vampire_dc:local) [799(4946)/853 at 2h3m28s] samba4.drs.samba_tool_drs_showrepl.python(vampire_dc)(vampire_dc:local) [800(4950)/853 at 2h3m37s] samba4.drs.replica_sync.python(vampire_dc)(vampire_dc:local) [801(4966)/853 at 2h7m41s] samba4.drs.delete_object.python(vampire_dc)(vampire_dc) [802(4968)/853 at 2h7m50s] samba4.drs.fsmo.python(vampire_dc)(vampire_dc) [803(4973)/853 at 2h8m10s] samba4.drs.repl_move.python(vampire_dc)(vampire_dc) [804(4994)/853 at 2h12m11s] samba4.drs.getnc_exop.python(vampire_dc)(vampire_dc) [805(5006)/853 at 2h12m36s] samba4.drs.getnc_unpriv.python(vampire_dc)(vampire_dc) [806(5010)/853 at 2h12m44s] samba4.drs.linked_attributes_drs.python(vampire_dc)(vampire_dc) [807(5013)/853 at 2h12m46s] samba4.drs.link_conflicts.python(vampire_dc)(vampire_dc) [808(5025)/853 at 2h23m1s] samba4.drs.samba_tool_drs.python(promoted_dc)(promoted_dc:local) [809(5039)/853 at 2h29m18s] samba4.drs.samba_tool_drs_showrepl.python(promoted_dc)(promoted_dc:local) [810(5043)/853 at 2h29m41s] samba4.drs.replica_sync.python(promoted_dc)(promoted_dc:local) UNEXPECTED(error): samba4.drs.replica_sync.python(promoted_dc).replica_sync.DrsReplicaSyncTestCase.test_ReplConflictsRenamedVsNewRemoteWin(promoted_dc:local) REASON: Exception: Exception: Traceback (most recent call last): File "/memdisk/autobuild/fl/b341606/samba/source4/torture/drs/python/replica_sync.py", line 330, in test_ReplConflictsRenamedVsNewRemoteWin self.ou2 = self._create_ou(self.ldb_dc2, "OU=Test Remote Rename Conflict") File "/memdisk/autobuild/fl/b341606/samba/source4/torture/drs/python/replica_sync.py", line 126, in _create_ou samdb.add_ldif(ldif) File "bin/python/samba/__init__.py", line 230, in add_ldif self.add(msg, controls) _ldb.LdbError: (68, 'LDAP error 68 LDAP_ENTRY_ALREADY_EXISTS - <Entry OU=Test Remote Rename Conflict,OU=replica_sync474546,DC=samba,DC=example,DC=com already exists> <>') FAILED (0 failures, 1 errors and 0 unexpected successes in 0 testsuites) A summary with detailed information can be found in: ./bin/ab/summary TOP 10 slowest tests samba4.drs.link_conflicts.python(vampire_dc)(vampire_dc) -> 615 samba4.ldap.rodc_rwdc.python(rodc)(rodc:local) -> 525 samba4.ldap.vlv.python(ad_dc_ntvfs)(ad_dc_ntvfs) -> 403 samba4.ldap.confidential_attr.python(ad_dc_ntvfs)(ad_dc_ntvfs) -> 389 samba4.drs.samba_tool_drs.python(promoted_dc)(promoted_dc:local) -> 377 samba4.drs.ridalloc_exop.python(vampire_dc)(vampire_dc) -> 340 samba4.drs.replica_sync.python(vampire_dc)(vampire_dc:local) -> 243 samba4.drs.repl_move.python(vampire_dc)(vampire_dc) -> 240 samba4.rpc.samr.passwords.lockout on ncacn_np with (ad_dc_ntvfs) -> 229 samba4.drs.samba_tool_drs.python(vampire_dc)(vampire_dc:local) -> 213 ERROR: test failed with exit code 1
