On Wed, 2021-04-21 at 12:55 -0500, Steve French wrote: > On Wed, Apr 21, 2021 at 12:42 PM Marios Makassikis > <mmakassikis@xxxxxxxxxx> wrote: > > On Wed, 2021-04-21 at 12:18 -0500, Steve French wrote: > > > Current Linux client (minus the deferred close patches) to > > > current > > > ksmbd on 5.12-rc8 as a test target passed all tests: > > > > > > http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/8/builds/32 > > > > > > > It doesn't look like any test was actually run though. > > The run times look plausible. Let me know if you see anything > suspicious. I can ssh in to make sure - but probably fine. I only > typically worry about tests that take less than 3 or 4 seconds (to > doublecheck that they aren't skipped) > > > I looked at some of the tests output and they all had umount > > errors: > > > > umount: /mnt/test: not mounted. > > umount: /mnt/test: not mounted. > > That is normal, the tests unmount at the end of the previous one > (unless it times out) and tries to unmount again before the next one > starts. > > > The warmup smb3 generic/001 hints at cifs.ko not being loaded: > > > > rmmod: ERROR: Module cifs is not currently loaded > > mount error(113): could not connect to 192.168.122.13Unable to find > > suitable address. > > That was because the test client VM had some out of memory issues and > so I shut down the windows server test target > (which is not relevant for these tests) Right, thanks for the explanations. For a second there I thought this was a case of 'the test failed successfully' :-). Marios
