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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
platforms as it tests the system iconv with the built in iconv. Limit
the test to Linux to avoid spurious errors.
(This used to be commit 9e1a8475ca7d1f8490cf8502c08a2544cfec5599)
('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 2406af10791cd8545c598c8591a48de5515c7dc5)
'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 e1742c14a247fabba969f8698108e73997d3f420)
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 0eb6097305776325c75081356309115f445a7218)
a share to operate on, not just the qfileinfo test, so now they are named
more appropriately.
(This used to be commit eb16d5324d6e1f4e4b33993e23a6446c3289a85f)
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 542bddacc8a57d5486d0b721ddd9357179b597b5)
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 56ae0171bafe4576c6163a0198a18b8163314e20)
- 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 f792a9532d0e263984c37d32bcf059b955e20b2c)
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 5095783cdf01db9d28392ba0d88186c1a4df654b)
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 5b3c8cc036c1180c9e96d9aaacd3f2e0a83460e5)
stat() 240 files that don't exist on every broadcast. That's a bit
excessive!
reduce max virtual interfaces to 16
(This used to be commit 3c4100027c7d3806a2021cb4d70ec6adf9dd2dc6)
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 72858f859483c0c532dddb2c146d6bd7b9be5072)
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 1a48fa96bc4b096a72bf5e4455aaa43c63966c10)
framework
Brad, I know this is a bit hackish. We really need a "testit" like
function like in test_functions.sh
(This used to be commit 7120fbffa5560dcaf3d796cb72fa3a6b78a991d6)
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 ce2baf7385e019383ffb292bd30e77c31eecbbef)
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 3cee6a7863bba61c92f94087df5c6442f02a2da7)
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 c2fc3471023b613571089cb018638a40091d08ab)
