Project

Profile

Help

Issue #6016

closed

pulp_file nightly builds are failing

Added by daviddavis about 4 years ago. Updated about 4 years ago.

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

Description

The performance tests in Travis are failing:

https://travis-ci.org/pulp/pulp_file/jobs/638482724

Seems to be a permissions problem:

E           PermissionError: [Errno 13] Permission denied: '/usr/local/lib/pulp'
Actions #1

Updated by lmjachky about 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to lmjachky
Actions #2

Updated by fao89 about 4 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 64
Actions #3

Updated by daviddavis about 4 years ago

For now, we've disabled the performance tests: https://github.com/pulp/pulp_file/pull/345

Actions #4

Updated by lmjachky about 4 years ago

The setup method which generates fixtures for the performance tests is dumping objects into the directory "/usr/local/lib/pulp/lib/python3.7/site-packages/rest_framework/static/fixtures/". This directory was chosen as a workaround for serving the fixtures through NGINX locally at http :80/static/rest_framework/fixtures/. But the script does not have permissions to write to the directory "/usr/local/lib/" in Travis.

Therefore, we need to change the way of how we generate the fixtures. When I was porting the performance tests to pulp_file, there was not a way for serving fixtures locally via REST API. Now, we do have support for generating fixtures locally, see https://pulp.plan.io/issues/5872 and https://pulp.plan.io/issues/5913.

As a first step, I added a new fixture in the repository pulp-fixtures (https://github.com/pulp/pulp-fixtures/pull/135). Travis failed because of a large amount of log data was being printed out during the execution (https://api.travis-ci.com/v3/job/278060877/log.txt). If we could fix this and merge the pull request, the fixture shall be served by NGINX "locally" in a separate container and the only thing that needs to be changed then is the repository's endpoint for the fixture in pulp_file.

Actions #5

Updated by daviddavis about 4 years ago

Thanks for the update and clearly defining the problem. Would it be possible to pipe the stdout from this line to /dev/null?

https://github.com/pulp/pulp-fixtures/blob/7d986a5f1d584d1b9480b32c2e56cc0a5571e0aa/file/gen-fixtures.sh#L71

Actions #6

Updated by rchan about 4 years ago

  • Sprint changed from Sprint 64 to Sprint 65
Actions #7

Updated by lmjachky about 4 years ago

  • Status changed from ASSIGNED to POST

Added by Lubos Mjachky about 4 years ago

Revision 790e3721 | View on GitHub

Use a local fixture served by a separate container

Before this commit, fixtures for the performance tests were generated in the directory /usr/local/lib/. This caused reported permission errors when the generator was trying to write to the directory. The fixture generator was removed in this commit because it has been replaced by the existing pulp-fixtures generator https://github.com/pulp/pulp-fixtures/pull/135. Functions for printing stats which are no longer used in the performance tests were removed too.

In addition, the performance tests were enabled to run again on a daily basis.

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

Actions #8

Updated by Anonymous about 4 years ago

  • Status changed from POST to MODIFIED
Actions #9

Updated by ttereshc about 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
  • Sprint/Milestone set to 0.1.1

Also available in: Atom PDF