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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
rafal: is there a reason why we don't use libnet_AddShare() in the torture test?
metze
(This used to be commit 070a98379a78eb46ff808521e375c9874c1c0d1c)
passed to acrfour, and that assumes a byte buffer. This caused us to
fail big endian boxes (or more specifically, to be incompatible with
little endian boxes)
(This used to be commit a44f2eda1eeb134292111dd857f0f65e4bf96399)
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)
which have a ulimit -n of 100. Drop the number of searches to 20.
That should limit the maximum total fd count to about 76, most of
which is all the listening sockets on the various interfaces
(This used to be commit fb5b8c4f8c1ed69e3a813befeeb2a9627e84c454)
talloc(NULL, xxx) to allocate the registry context. That had two
consequences
1) it was a massive memory leak, as all winreg operations leaked their
entire context (including an open ldb database) every time
2) event_context_find() never found the exsting event context, so we
used a new event context each time, which called epoll_create()
each time, which caused a fd to be allocated
(This used to be commit 1c0a3de39828b43149d8981fc7f10e7c8b59a392)
descriptors in smbd on all build farm machines. I suspect we have a fd
leak somewhere, but its hard to track down.
I know part of the problem is the number of (fake) network interfaces
we define in the build farm tests, with each of them listening on a
whole bunch of different protocol ports. That chews up around 48 file
descriptors just to startup. I don't think thats the real problem
though, and I suspect something else is leaking file descriptors on
some hosts.
(This used to be commit 83bf458ec98d9f2a21b3748802f41abcbcc1e0b2)
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)
when it breaks. It isn't much good as a template for developers to use
unless it works :-)
(This used to be commit 262bee07dcb140b413d5ae5a8a754b3e57235323)
When changing a field name in idl, please remember to check for use of
those functions in any js code as well.
(This used to be commit 7005806aa6842ffc3d5ed98682f2aefc59759580)
Jerry, there is a big difference on the wire between these two:
[out] uint32 x;
and
[out] uint32 *x;
if you change from
[out] uint32 x;
then you need to change to:
[out,ref] uint32 *x;
otherwise it changes the format on the wire, which means we are no
longer compatible with MS servers.
but be aware that even if you change to a ref ptr, you also need to
change all the client code to set all the return variables in the out
part of the structure. That's why I don't like the MIDL restriction of
forcing the use of ref pointers for output variables - it makes life
much harder when writing client code, and makes the code much more
error prone (just look at all the extra code needed to make this work
again).
I know we could auto-allocate these variables in the generated client
side NDR code, but if we did that then we would have no way of doing a
_real_ ref out pointer, which we really wanted to set to some already
allocated variable.
So please hold off on changing our idl to use the MIDL convention for
output variables until Jelmer and I have had a good "chat" about this :-)
(This used to be commit 555aed43ba3c08360ca7fa921622b80732a7f657)
- change the test for net/if.h to do a full compile, not just an
existance test. net/if.h is completely broken on hpux, and can never
compile (it uses stuff before it defines it), so by using a
AC_TRY_COMPILE() test we avoid using net/if.h on hpux, which should
fix the build
(This used to be commit bde18f3d5ce837f600bae8d63f31d92a579fe1f2)
Also cope with the fact that we define the FSTYPE as NTFS by default.
We never use this anywhere else, so we may just change it, but just
detect the fact and return DISK in share_classic for now.
(This used to be commit 4daf5f7764ce69c14066f7320961c90141f0863a)
- undefine _XOPEN_SOURCE_EXTENDED for the AIX interface detection test
#define _XOPEN_SOURCE_EXTENDED 1 brings in sa_len to sockaddr on Tru64
which means the AIX code compiles...
metze
(This used to be commit 04a0a5144a249e12a9dcb327c5b6055e6a6135db)
