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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
hang forever if an ealier one caused two operations to complete at
once
this is why RAW-CONTEXT was taking 5 minutes on the build farm
(This used to be commit eeba37e25cdcaefac4a252fb4305bddaba217826)
context. We now have an event context on the torture_context, and we
can also get one from the cli_credentials structure
(This used to be commit c0f65eb6562e13530337c23e3447a6aa6eb8fc17)
might take a bit for events to propagate from one to another connection,
in particular with a process per connection.
(This used to be commit 0c7a518b2dad83dc78f3e3058fd8e1267d0e928f)
It seems most opertaions are supported, but that the values are not
consistant. I think these are very much hand-hacked stubs, which is
what they will be on Samba4 too.
I'll need to add some more 'don't fail for...' hacks before this
passes against Win2k3.
Andrew Bartlett
(This used to be commit dcb858d0c716b23be6c5d36b4aa6f155582ada63)
implementation of a opendb backend. Use it in combination with
--unclist to tell smbtorture to connect to multiple nodes in the
cluster
(This used to be commit b4e38b1b8dbc3ce817f858f39c3f0521c9832fce)
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 38f867880beb40c691e9713f854426031310629c)
acceptable.
In Samba3 with inotify we have the problem that the MODIFIED action is sent
second. I think this could also happen in Samba4, depending on the order when
the different sockets (unix domain dgram / inotify) are looked at by the
events system.
This patch accepts the NEW/OLD/MODIFIED entries in any order.
Comments welcome!
Volker
(This used to be commit 72a7771b757c3aca637eb632abebab60bdd2da9f)
If someone is feeling like solving that puzzle, contact Jeremy or me for hints
:-)
Volker
(This used to be commit 93e6dbaf5b81661d85539877fd0874480cfa5673)
particular the NT_STATUS_INVALID_PARAMETER thing was badly wrong. Remove the
changes based on it. Using gentest is much more effective in this respect, but
it will take a while to figure out the wildcard error handling of W2k3.
Volker
(This used to be commit 33d842e27d7611dd1d3cbfa71d44d63c273ba785)
under Linux we returned NT_STATUS_NOT_A_DIRECTORY. This is because in the
bad_path==True condition lstat(2) returns ENOTDIR and not ENOENT.
Not sure if we want to necessarily replicate the INVALID_PARAMETER here, but
this is what W2k3 does.
Jeremy, I tried to call you, but you were not around. So I'll leave it up to
you to merge this.
Volker
(This used to be commit 838afa8f7d2b10460725c1f0b519ce54fb84de88)
Samba3 returns the SPARSE flag for files with size > allocation, and on many
configs Samba3 does not support EAs. Cope with both.
Tridge, please check this is acceptable for this test.
Volker
(This used to be commit 4df4d37c3d4d9e6c430afd36e88684f02c73700e)
we have any?? ;-), so don't mark failure to correctly cope with the close
write time as critical.
Volker
(This used to be commit 42070b09cba8adda1e7606e08764b1f202b33321)
Samba3. This is a known deficiency also taken care of in the base-delete
test.
Volker
(This used to be commit 6b91bb93fad84e054c19f8c9bc4145234f171a3c)
communitcation in a CIFS clustered server. It tries to keep the
connections full by setting up the next lock as each lock is done.
The locking pattern is similar to the local filesystem ping pong test
in junkcode, forcing a communication between nodes on each request
(This used to be commit d57b9fb29860bd03cfa970bcc52ef45d17775638)
