Skip to content

Fix parallel CLI test name collisions - #169

Merged
pedro-psb merged 1 commit into
pulp:mainfrom
jobselko:fix_tests
Aug 18, 2026
Merged

pedro-psb merged 1 commit into
pulp:mainfrom
jobselko:fix_tests

Conversation

@jobselko

Copy link
Copy Markdown
Member

No description provided.

Assisted By: Claude Opus 4.6
@jobselko jobselko self-assigned this Aug 17, 2026
@jobselko
jobselko marked this pull request as ready for review August 17, 2026 12:44
@pedro-psb
pedro-psb enabled auto-merge (rebase) August 18, 2026 13:34
@pedro-psb
pedro-psb merged commit 8bb46ed into pulp:main Aug 18, 2026
10 checks passed
@jobselko
jobselko deleted the fix_tests branch August 18, 2026 13:40
@patchback

patchback Bot commented Aug 18, 2026 •

Copy link
Copy Markdown

Backport to 0.6: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 8bb46ed on top of patchback/backports/0.6/8bb46eda711b20407889533fbdcfc580359221e9/pr-169

Backporting merged PR #169 into main

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it:
    $ git remote add upstream https://github.com/pulp/pulp-cli-gem.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code:
    $ git fetch upstream
    $ git checkout -b patchback/backports/0.6/8bb46eda711b20407889533fbdcfc580359221e9/pr-169 upstream/0.6
  4. Now, cherry-pick PR Fix parallel CLI test name collisions #169 contents into that branch:
    $ git cherry-pick -x 8bb46eda711b20407889533fbdcfc580359221e9
    If it'll yell at you with something like fatal: Commit 8bb46eda711b20407889533fbdcfc580359221e9 is a merge but no -m option was given., add -m 1 as follows instead:
    $ git cherry-pick -m1 -x 8bb46eda711b20407889533fbdcfc580359221e9
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Fix parallel CLI test name collisions #169 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub:
    $ git push origin patchback/backports/0.6/8bb46eda711b20407889533fbdcfc580359221e9/pr-169
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants