Conversation
Fixes: https://tracker.ceph.com/issues/70181 Signed-off-by: Patrick Donnelly <[email protected]>
|
This PR is under test in https://tracker.ceph.com/issues/70184. |
|
This PR is under test in https://tracker.ceph.com/issues/70189. |
|
This PR is under test in https://tracker.ceph.com/issues/70195. |
|
This PR is under test in https://tracker.ceph.com/issues/70197. |
* refs/pull/62008/head: qa: disable multimds pjd suite testing
|
This PR is under test in https://tracker.ceph.com/issues/70218. |
|
What? Do we have a similar metadata op correctness test that we run against non-singleton cluster? |
|
Having a tracker with only an error asserting it doesn't make sense to run the workload, and a PR description which only points to the tracker, is not a great way to track or justify this, regardless of any code comment btw. |
Not for multimds, no. To be clear: this pjd test suite is evaluating POSIX compliance for corner cases of system calls. I do not see much added value by randomly exporting subtrees under this. |
Do we have a better validation suite that we maintain our posix requirements under migration? |
* refs/pull/62008/head: qa: disable multimds pjd suite testing
|
I may end up taking a different approach here. The export counter warnings are appearing for other workunits too, still. |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
|
This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution! |
Fixes: https://tracker.ceph.com/issues/70181
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e