search for: knownfail

...would very much like to be part of the conversation around any changes we make here. It is not that the the current situation is ideal, but it has come with a number of significant advantages. In both cases the development process includes tests, and these tests are at least initially marked as knownfail for MIT Kerberos. This is not as dire as it seems, because more then 50% of a Samba development task is tests, those supporting the MIT KDC are presented with a full set of tests and a list of know failures the address. However that knownfail listing is the limit that the developers providing n...

...l --prefix=./st --builddir=. --srcdir=. --exclude=./selftest/skip --testlist="./selftest/tests.sh|" --exclude=./selftest/slow --quick --include=./selftest/quick --socket-wrapper && touch ./st/st_done) | /usr/bin/python -u ../selftest/filter-subunit --expected-failures=./selftest/knownfail | tee ./st/subunit | /usr/bin/python -u ../selftest/format-subunit --prefix=./st --immediate tee: ./st/subunit: No such file or directory SOCKET_WRAPPER_DIR=/data/samba-master/source4/st/w Version 4.0.0alpha12-GIT-4ca9683 OPTIONS --configfile=$SMB_CONF_PATH --maximum-runtime=1200 --target=samba4 -...

...a.org> ?? * BUG 14929: CVE-2022-44640 [SECURITY] Upstream Heimdal free of ???? user-controlled pointer in FAST. ?? * BUG 15219: Heimdal session key selection in AS-REQ examines wrong entry. ?? * BUG 15237: CVE-2022-37966. ?? * BUG 15258: filter-subunit is inefficient with large numbers of knownfails. o? Ralph Boehme <slow at samba.org> ?? * BUG 15240: CVE-2022-38023. ?? * BUG 15252: smbd allows setting FILE_ATTRIBUTE_TEMPORARY on directories. o? Stefan Metzmacher <metze at samba.org> ?? * BUG 13135: The KDC logic arround msDs-supportedEncryptionTypes differs from ???? Wind...

...a.org> ?? * BUG 14929: CVE-2022-44640 [SECURITY] Upstream Heimdal free of ???? user-controlled pointer in FAST. ?? * BUG 15219: Heimdal session key selection in AS-REQ examines wrong entry. ?? * BUG 15237: CVE-2022-37966. ?? * BUG 15258: filter-subunit is inefficient with large numbers of knownfails. o? Ralph Boehme <slow at samba.org> ?? * BUG 15240: CVE-2022-38023. ?? * BUG 15252: smbd allows setting FILE_ATTRIBUTE_TEMPORARY on directories. o? Stefan Metzmacher <metze at samba.org> ?? * BUG 13135: The KDC logic arround msDs-supportedEncryptionTypes differs from ???? Wind...

Hi. Where might I find some kind of reference for the messages generated by 'make test'? I would at least like to know which ones I can safely ignore. Thanks -jimc

...4096 2008-03-27 00:16 ntptr drwxr-xr-x 13 root root 4096 2008-03-27 00:16 ntvfs drwxr-xr-x 4 root root 4096 2008-03-27 00:14 param drwxr-xr-x 5 root root 4096 2008-03-27 00:15 pidl drwxr-xr-x 16 root root 4096 2008-03-27 00:15 rpc_server -rw-r--r-- 1 root root 1035 2008-03-27 00:16 samba4-knownfail -rw-r--r-- 1 root root 360 2008-03-27 00:16 samba4-quick -rw-r--r-- 1 root root 1418 2008-03-27 00:16 samba4-skip drwxr-xr-x 3 root root 4096 2008-03-27 00:16 script drwxr-xr-x 7 root root 4096 2008-03-27 00:14 scripting drwxr-xr-x 6 root root 4096 2008-03-27 00:15 selftest drwxr-xr-x 3...

...pping=nmblookup3:nmblookup3,smbclient3:smbclient3,smbtorture4:smbtorture,ntlm_auth3:ntlm_auth3 --exclude=./st/slow --quick --include=./st/quick --socket-wrapper && touch ./st/st_done) | /usr/bin/python -u /root/download/samba-4.0.0alpha16/selftest/filter-subunit --expected-failures=./st/knownfail | tee ./st/subunit | /usr/bin/python -u /root/download/samba-4.0.0alpha16/selftest/format-subunit --prefix=./st --immediate You don't have Time::Hires installed ! SOCKET_WRAPPER_DIR=/root/download/samba-4.0.0alpha16/st/w [2011/08/03 16:17:44, 0] ../lib/util/debug.c:572(reopen_logs_internal)...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...me/alex/workspace/samba-4.12.5/bin/default/third_party/socket_wrapper/libsocket-wrapper.so --use-dns-faking --socket-wrapper && touch ./st/st_done) | /usr/bin/python3 -u /home/alex/workspace/samba-4.12.5/selftest/filter-subunit --expected-failures=/home/alex/workspace/samba-4.12.5/selftest/knownfail --expected-failures=/home/alex/workspace/samba-4.12.5/selftest/knownfail.d --flapping=/home/alex/workspace/samba-4.12.5/selftest/flapping --flapping=/home/alex/workspace/samba-4.12.5/selftest/flapping.d | tee ./st/subunit | /usr/bin/python3 -u /home/alex/workspace/samba-4.12.5/selftest/format-subun...

...t/lib/socket_wrapper/libsocket-wrapper.so --uid_wrapper_so_path=/var/tmp/samba-4.2.1/bin/default/lib/uid_wrapper/libuid-wrapper.so --socket-wrapper && touch ./st/st_done) | /usr/bin/python -u /var/tmp/samba-4.2.1/selftest/filter-subunit --expected-failures=/var/tmp/samba-4.2.1/selftest/knownfail --flapping=/var/tmp/samba-4.2.1/selftest/flapping | tee ./st/subunit | /usr/bin/python -u /var/tmp/samba-4.2.1/selftest/format-subunit --prefix=./st --immediate ERROR: test failed with exit code 1 make: *** [quicktest] Error 1 the "summary" file reads: = Failed tests = == samba3.rpc....

...in/default/third_party/uid_wrapper/libuid-wrapper.so --use-dns-faking --socket-wrapper samba3.blackbox.smbclient_machine_auth.plain && touch ./st/st_done) | /usr/bin/python3 -u /home/user/src/samba-git/samba/selftest/filter-subunit --expected-failures=/home/user/src/samba-git/samba/selftest/knownfail --expected-failures=/home/user/src/samba-git/samba/selftest/knownfail.d --flapping=/home/user/src/samba-git/samba/selftest/flapping --flapping=/home/user/src/samba-git/samba/selftest/flapping.d | tee ./st/subunit | /usr/bin/python3 -u /home/user/src/samba-git/samba/selftest/format-subunit --prefix=...

Thanks for the reply, Besides the problem with source4/lib/messaging/messaging_handlers.c, Good to hear that selftest is actively used, then do I understand it right that 'make test' should succeed? My bigger problem is that it failed with lots of errors. This must be a problem with my build, then, but since this is a fresh tarball I am a bit puzzled. I would appreciate some hint on

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...to build as a distinct tarball, but is instead provided as an optional public library. If you need ldb as a public library, say to build sssd, then use ?./configure --private-libraries='!ldb' This re-integration allows LDB tests to use the Samba's full selftest system, including our knownfail infrastructure, and decreases the work required during security releases as a coordinated release of the ldb tarball is not also required. This approach has been demonstrated already in Debian, which is already building Samba and LDB is this way. As part of this work, the pyldb-util public librar...

...et-wrapper.so --uid_wrapper_so_path=/home/arjit/samba-4.5.0/bin/default/lib/uid_wrapper/libuid-wrapper.so --use-dns-faking --socket-wrapper && touch ./st/st_done) | /usr/local/bin/python -u /home/arjit/samba-4.5.0/selftest/filter-subunit --expected-failures=/home/arjit/samba-4.5.0/selftest/knownfail --flapping=/home/arjit/samba-4.5.0/selftest/flapping | tee ./st/subunit | /usr/local/bin/python -u /home/arjit/samba-4.5.0/selftest/format-subunit --prefix=./st --immediate ERROR: test command failed to complete *** Error exit code 1 Stop.