Skip to content

Comments

qa: disable multimds pjd suite testing#62008

Closed
batrick wants to merge 1 commit intoceph:mainfrom
batrick:i70181
Closed

qa: disable multimds pjd suite testing#62008
batrick wants to merge 1 commit intoceph:mainfrom
batrick:i70181

Conversation

@batrick
Copy link
Member

@batrick batrick commented Feb 26, 2025

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 x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox
  • jenkins test windows
  • jenkins test rook e2e

@batrick
Copy link
Member Author

batrick commented Feb 26, 2025

@batrick
Copy link
Member Author

batrick commented Feb 26, 2025

@batrick
Copy link
Member Author

batrick commented Feb 27, 2025

@batrick
Copy link
Member Author

batrick commented Feb 27, 2025

@batrick batrick requested a review from a team February 27, 2025 18:19
batrick added a commit to batrick/ceph that referenced this pull request Feb 27, 2025
* refs/pull/62008/head:
	qa: disable multimds pjd suite testing
@batrick
Copy link
Member Author

batrick commented Feb 27, 2025

@gregsfortytwo
Copy link
Member

What? Do we have a similar metadata op correctness test that we run against non-singleton cluster?

@gregsfortytwo
Copy link
Member

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.

@batrick
Copy link
Member Author

batrick commented Feb 27, 2025

What? Do we have a similar metadata op correctness test that we run against non-singleton cluster?

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.

@gregsfortytwo
Copy link
Member

What? Do we have a similar metadata op correctness test that we run against non-singleton cluster?

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?
That seems like something we straightforwardly ought to be thrashing migrations against.

batrick added a commit to batrick/ceph that referenced this pull request Feb 27, 2025
* refs/pull/62008/head:
	qa: disable multimds pjd suite testing
@batrick
Copy link
Member Author

batrick commented Feb 28, 2025

I may end up taking a different approach here. The export counter warnings are appearing for other workunits too, still.

@github-actions
Copy link

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.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@github-actions github-actions bot added the stale label Apr 29, 2025
@github-actions
Copy link

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!

@github-actions github-actions bot closed this May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants