IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
current test makes no sense with the new test system. For example, it
does "mkdir bla" then "cd bla" then "cd ..", but it now does these as
separate smbclient commands, which makes no sense at all. It even
seems to try to run them in parallel???
The test fails (segfault, plus lots of errors), but gets reported as a
success
(This used to be commit 9e3bbdee50)
This changes the main selftest code to be in perl rather than in shell script.
The selftest script is now no longer a black box but a regular executable that takes
--help.
This adds the following features:
* "make test TESTS=foo" will run only the tests that match the regex "foo"
* ability to deal with expected failures. the suite will not warn about tests
that fail and are known to fail, but will warn about other failing tests and
tests that are succeeding tests but incorrectly marked as failing.
* ability to print a summary with all failures at the end of the run
It also opens up the way to the following features, which I hope to implement later:
* "environments", for example having a complete domains with DCs and domain members
in a testenvironment
* only set up smbd if necessary (not when running LOCAL tests, for example)
* different mktestsetup scripts per target. except for the mktestsetup script, we can
use the same infrastructure for samba 3 or windows.
(This used to be commit 38f867880b)
Fedora DS CVS, plus changes to split up 00core.ldif.
Now we 'just' need to work to make the tests pass...
Andrew Bartlett
(This used to be commit d214cb1ccf)
exit.
If we kill smbd right away, we can interrupt the gcov data file
writeout. Instead, we now wait up to 20 seconds for the process to
exit, before sending it a kill -9.
Andrew Bartlett
(This used to be commit c547bce3d3)
using the pattern in the clilsa code, it didn't fill in the p->binding
structure. This affects nearly all users of dcerpc_pipe_open_smb(), so
the simplest fix is to ensure that dcerpc_pipe_open_smb() initialises
the binding if its not already there.
- re-enable the RAW-ACLS test
(This used to be commit d8875c286d)
Stop passing the VM config file path to wintest_2k3_dc.sh on the command line as it is now properly passed through the environment.
Windows tests, including the DC tests found in test_w2k3.sh should work properly with 'make wintest' and a configured VMware environment.
These tests are executed on build-farm host bnhtest.
(This used to be commit 7496a28b43)
Restructure existing tests to work with the recent build farm changes.
Added windows DC testing to 'make wintest'.
Some improvements and generalization to the way errors are handled.
(This used to be commit de9687404e)
wintest_2k3_dc.sh is a new script which will run a group of tests against a Windows 2003 DC.
The group of tests to run should be passed in on the command line.
These tests were taken from the source/script/tests/test_win2k3.sh script.
tests_win2k3_dc.sh is a new script intended to be called by 'make wintest_dc' (patch to source/main.mk forthcoming).
This is intended to provide the basis for Windows 2003 DC testing in the build farm.
In order to use these tests, you should have a DC setup as a VM in VMware server.
This process is not automated yet, but can be done by following a few steps:
1. Prepare a Windows 2003 VM in VMware Server by downloading and extracting:
svn://svn.samba.org/home/svn/samba/branches/SOC/bnh/vm_setup.tar.gz
and following the instructions in the README file.
2. Copying the following file onto the filesystem of the VM configured in step 1:
svn://svn.samba.org/home/svn/samba/branches/SOC/bnh/dcpromo_2k3dc_newdomain.answerfile.txt
and use it to promote the VM.
For example: "dcpromo /answer:<path to answerfile>"
3. On the system you are testing from, set the environment variable WINTESTCONF, and SRCDIR.
WINTESTCONF should point to the path of a test_win.conf file modified for your environment.
There's a default copy in source/script/tests/win/test_win.conf.
SRCDIR should point to the base of your Samba 4 source tree.
At that point, you should be able to run wintest_2k3_dc.sh by passing a group of tests at the command line.
For example: source/script/tests/win/wintest_2k3_dc.sh RPC-DRSUAPI
Sorry for the long-winded commit message!
(This used to be commit a0d1c690de)
Made the restore_snapshot() routine in wintest_functions.sh more robust.
This change would have broken the existing windows tests, if they weren't already broken.
Will fix those once the windows DC tests are committed and working in the build farm.
(This used to be commit 76c6c5b8de)
always bring it back if we need to. This code was getting in the way while
refactoring.
Add some tests for TDR.
Get rid of typedef in lib/registry/tdr_regf.idl and fix the
TDR code to be able to deal with it.
(This used to be commit 1ad0f99a43)
- No path given to web server means use old scripts (missed check-in)
- Build Web Application (qooxdoo stuff) from autogen.sh since python isn't
available or is differently-configured on various build-farm machines
- Don't continually check in generated files
- Properly identify SWAT "Statistics" module as "Status and Statistics"
(This used to be commit 9d89b7663a)
way to setup a Samba4 DC is to set 'server role = domain controller'.
We use the fSMORoleOwner attribute in the base DN to determine the PDC.
This patch is quite large, as I have corrected a number of places that
assumed taht we are always the PDC, or that used the smb.conf
lp_server_role() to determine that.
Also included is a warning fix in the SAMR code, where the IDL has
seperated a couple of types for group display enumeration.
We also now use the ldb database to determine if we should run the
global catalog service.
In the near future, I will complete the DRSUAPI
DsGetDomainControllerInfo server-side on the same basis.
Andrew Bartlett
(This used to be commit 67d8365e83)
Remove kerberos_verify.c, as we don't need that code any more.
Replace with code for using the new krb5_rd_req_ctx() borrowed from
Heimdal's accecpt_sec_context.c
Andrew Bartlett
(This used to be commit 13c9df1d4f)
Ensure that we don't accept kerberos logins without a PAC (to ensure
we actually produce a PAC in the KDC)
Andrew Bartlett
(This used to be commit 5fda92783f)
('configure.developer' or 'configure --enable-developer') may still have
problems as I'm not sure I got all of the paths right for that.
With the changes Tridge has made to the Main Menu in swat, given a
non-developer installation, you should be able to get to ldbbrowse via:
JSON/qooxdoo -> ldb browser
Derrell
(This used to be commit 2406af1079)
'subunit' protocol. This allows us to easily plug EJS scripts or binaries that
can't depend on -ltorture into smbtorture. The protocol is very simple:
- write "comments" to stderr
Example output on stdout:
test: foo
success: foo
test: bar
success: bar
test: blah
failure: blah [
dummy.c:30: Expression 1 != 2 failed!
]
test: blie
skip: blie [
Iconv support not built in
]
I've already converted the talloc testsuite.
(This used to be commit e1742c14a2)
output in the testsuite rather than just True or False for a
set of tests.
The aim is to use this for:
* known failure lists (run all tests and detect tests that
started working or started failing). This
would allow us to get rid of the RPC-SAMBA3-* tests
* nicer torture output
* simplification of the testsuite system
* compatibility with other unit testing systems
* easier usage of smbtorture (being able to run one test
and automatically set up the environment for that)
This is still a work-in-progress; expect more updates over the next couple of
days.
(This used to be commit 0eb6097305)
RPC-DSSETUP RPC-EPMAPPER RPC-INITSHUTDOWN RPC-LSA-GETUSER RPC-MULTIBIND RPC-ROT
RPC-SECRETS RPC-SRVSVC RPC-SVCCTL RPC-WKSSVC tests against windows, either
by 'make wintest' or in the build farm.
I was surprised when RPC-EVENTLOG and RPC-LSA failed, so i'll investigate today.
(This used to be commit 542bddacc8)
just compile it with
cc -g -o gdb_backtrace_test gdb_backtrace_test.c
and run it in the same directory where your gdb_backtrace script is.
metze
(This used to be commit 56ae0171ba)
- try /proc/${PID}/exe first
- fallback to the binary given on the commandline
- fallback searching the binary with 'which' from the
commandline argument
- use 'ladebug' debugger on Tru64
metze
(This used to be commit f792a9532d)
export MAKE_TEST_ENABLE_PCAP=yes
make test will use SOCKET_WRAPPER_PCAP_FILE support
and will run each test with a different file
the capture will be removed unless the test fails.
the TEST PCAP: line will show the location of the file
metze
(This used to be commit 5095783cdf)
DB_CONFIG file, we now get reasonable enought performance to pass
'make test' against OpenLDAP.
We do have to double the maximum runtime for the torture client however.
Andrew Bartlett
(This used to be commit 5b3c8cc036)
This moves these attributes from objectguid into an optional backend
(objectguid), used by ltdb. For OpenLDAP, the entryUUID module
converts entryCSN into usnChanged.
This also changes the sequence number API, and uses 'time based'
sequence numbers, when an LDAP or similar backend is detected.
To assist this, we also store the last modified time in the TDB,
whenever we change a value.
Andrew Bartlett
(This used to be commit 72858f8594)
with all the helpful env variables set.
TEST_LDAP=yes script/tests/selftest.sh st/ xterm SOCKET_WRAPPER
Andrew Bartlett
(This used to be commit 1a48fa96bc)
filesystems and the tests are taking more than 1.5 hours. We will
still be testing the sync code paths, as the ldb tests still run
synchronous, but doing all of our other tests synchronously just costs
too much time.
(This used to be commit ce2baf7385)
completes in a minute on my laptop (the benchmark I usually use).
Simo, I removed th ldb tests, as ldb is pretty well tested by lots of
the other tests, and its a pretty slow test. We could instead add a
"ldb-testquick.sh" which does only minimal testing. The full tests
will of course be run with 'make test' and in the build farm.
(This used to be commit 3cee6a7863)
when I changed the test output to be easier to read, I also broke it
so that it always gives a zero exit status. Fix now, and unfortunately
I expect to see some more red in the farm as a result :(
(This used to be commit c2fc347102)
Let me know if there's anything that looks strange or could use clarification.
vm_setup.tar.gz is currently located at the root of my SVN branch, svn://svnanon.samba.org/samba/branches/SOC/bnh.
(This used to be commit 849fe757bb)
