Skip to content

Conversation

@isi-mfurer
Copy link
Contributor

@isi-mfurer isi-mfurer commented Apr 5, 2019

Log of running the new tests against onefs 8.1.1, onefs staging 008, windows 7, and windows 2016

https://gist.github.com/isi-mfurer/5f6d30c25a822060e48b04e0e1a1e197

WiP

TODO: relocate the write/read tests
move TreeConnectWithDialect into pike.test package init
allow assert_error to take an arbitrary number of ntstatus to check
against
add dialect gates for dialect specific tests

use new assert_error to assert on multiple status given differing
windows behavior

fix pep8
@isi-mfurer isi-mfurer changed the title Mtu transport Additional test cases for probing MTU/transact size for various dialects Apr 5, 2019
flags=0,
file_index=0,
file_name='{0}*'.format(self.filename_prefix),
output_buffer_length=self.payload_size)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we be using max_trans_size here rather than payload_size? (Isn't the goal here to test that we can do a full max_trans_size transfer?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well windows 10 / windows server 2016 return 8mb for max_trans_size, but will still fail the request if the client asks for a buffer larger than 64k, so i'm not really sure why those servers are returning such a large max_trans_size. any ideas would be welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants