Project

Profile

Help

Test #4442

closed

Test different code paths

Added by kersom about 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Version:
Platform Release:
Tags:
Sprint:
Quarter:

Description

Different code paths are used in Pulp for the cases when artifacts are already present on the filesystem during sync and when they are not downloaded yet.

It probably makes sense to test 2 subsequent syncs of the same repo with immediate policy (doesn't matter which plugin) to be sure that second one is fine.

1. no content from repo A is downloaded
2. sync/publish repo A with download policy immediate
3. sync/publish repo A (or any other repo which has at least one artifact from repo A) again with download policy immediate
No failure in 2 shows that sync went fine when content was not present on the disk and in the DB.
No failure in 3 shows that sync went fine when content was already present on the disk and in the DB.

Actions #1

Updated by kersom about 5 years ago

  • Description updated (diff)
Actions #2

Updated by kersom about 5 years ago

  • Assignee set to kersom

Added by kersom about 5 years ago

Revision ed8ba2de | View on GitHub

Add test to verify sync/publish content already in pulp

Add test to verify how pulp handles sync/publish of content already on filesystem and database.

https://pulp.plan.io/issues/4442 closes: #4442

Added by kersom about 5 years ago

Revision ed8ba2de | View on GitHub

Add test to verify sync/publish content already in pulp

Add test to verify how pulp handles sync/publish of content already on filesystem and database.

https://pulp.plan.io/issues/4442 closes: #4442

Actions #3

Updated by kersom about 5 years ago

  • Status changed from NEW to MODIFIED
Actions #4

Updated by kersom about 5 years ago

  • Status changed from MODIFIED to CLOSED - COMPLETE
Actions #5

Updated by bmbouter almost 5 years ago

  • Tags deleted (Pulp 3)

Also available in: Atom PDF