daos-stack
DAOS-11204 dfs: Resample file stat after changing size.
Bug-tracker data: Ticket title is 'dfuse mtime incorrect with caching' Status is 'In Review' Labels: 'triaged' https://daosio.atlassian.net/browse/DAOS-11204
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I'm waiting for https://github.com/daos-stack/daos/pull/9778 to land before working in this as then I can enable the tests in this PR.
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9943/2/execution/node/138/log
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9943/3/execution/node/146/log
@ashleypittman when you land this, please backport to 2.2
The dfuse unit tests aren't on 2.2 so this won't be a clean cherry-pick but I'll backport it.
The dfuse unit tests aren't on 2.2 so this won't be a clean cherry-pick but I'll backport it.
is there a reason not to backport those tests too?
The dfuse unit tests aren't on 2.2 so this won't be a clean cherry-pick but I'll backport it.
is there a reason not to backport those tests too?
We looked at this yesterday, they use a avocado !mux feature which needed a bunch of python3 patches to launch.py so a backport is non-trivial.
The dfuse unit tests aren't on 2.2 so this won't be a clean cherry-pick but I'll backport it.
is there a reason not to backport those tests too?
See my comment here: https://daosio.atlassian.net/browse/DAOS-11171
The dfuse unit tests aren't on 2.2 so this won't be a clean cherry-pick but I'll backport it.
is there a reason not to backport those tests too?
See my comment here: https://daosio.atlassian.net/browse/DAOS-11171
It would be great to keep track and backport all the required test. it sounds concerning if we don't backport tests just because of the test infrastructure.
We DO want to backport the tests - it's just going to be complicated :)
We DO want to backport the tests - it's just going to be complicated :)
got it. thanks!