Project

Profile

Help

Issue #6104

closed

pulp_file performance test takes too long for Travis

Added by daviddavis over 4 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp_file/623":https://github.com/pulp/pulp_file/issues/623


Currently the pulp_file cron jobs are failing due to the performance tests. It looks like they are exceeding 50 minutes which is the threshold in Travis[0].

On my local box, it took about 24 seconds for pulp to process 400 content units. So for 100,000 units it would take about 100 minutes (100,000 / 400 * 24 / 60).

If we lowered the number of units to 10,000-20,000, the performance tests should complete under 50 minutes.

Alternatively, the maximum execution time in Github Actions is 6 hours[1].

[0] https://docs.travis-ci.com/user/customizing-the-build/#build-timeouts

[1] https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#usage-limits


Related issues

Related to Pulp - Issue #6121: Syncs of very large repositories take longer than Pulp 2CLOSED - CURRENTRELEASElmjachkyActions

Also available in: Atom PDF