-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAOS-15992 client: set st_blksize in ostatx_cb() and add unit test #14666
Conversation
…14534) Python buffered read/write relies on st_blksize as default buffer size. dfuse calls dfs_ostatx() which returns stat with zero st_blksize. Consequently, 4096 for st_blksize is returned to application. Signed-off-by: Lei Huang <[email protected]>
Ticket title is 'st_blksize in stat is not set inside ostatx_cb' |
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14666/2/execution/node/1563/log |
Test stage Functional Hardware Medium UCX Provider completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14666/2/execution/node/1709/log |
The failures in hardware tests in CI are not related to this PR. Existing tickets, |
could you please rebase with latest 2.6 and push again? thanks |
Required-githooks: true Signed-off-by: Lei Huang <[email protected]>
Thank you! I just merged this PR with release/2.6. |
Allow-unstable-test: true Features: pil4dfs Signed-off-by: Lei Huang <[email protected]>
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14666/4/execution/node/1508/log |
The only failure is an existing issue. |
Python buffered read/write relies on st_blksize as default buffer size. dfuse calls dfs_ostatx() which returns stat with zero st_blksize. Consequently, 4096 for st_blksize is returned to application.
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: