Project

General

Profile

Actions

Bug #15260

closed

ceph-disk and ceph-detect-init builds do check-only things on every build

Added by Dan Mick about 8 years ago. Updated almost 3 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

It seems that ceph-disk and ceph-detect-init's Makefiles always create the virtualenv, whether called during make or make check, but it seems that it only needs the virtualenv for testing (when called during check).

I'm not 100% certain of the fix here but it would be nice if only the ceph-disk-install-data target were run on non-check builds.

We noticed this when the virtualenv construction was failing because of long paths and #! truncation, which prompted the question "why is a non-check build even doing this?"

Actions #1

Updated by Dan Mick about 8 years ago

  • Assignee set to Loïc Dachary

Loic, if you could clarify intent and requirements, I'm not necessarily asking you to fix it, but assigning just to get your attention on it

Actions #2

Updated by Loïc Dachary about 8 years ago

We're not currently using virtualenv during make. But we should, at least for tox -e flake8. I think removing the build dependency to virtualenv would go in the wrong direction. If anything we'll need virtualenv more and more moving foward. Not less and less.

Actions #3

Updated by Dan Mick about 8 years ago

I'm not saying to remove the dependency; I'm saying that it's not necessary outside the test build.

Actions #4

Updated by Dan Mick about 8 years ago

(and even more so that it runs every build, whether anything's changed or not)

Actions #5

Updated by Loïc Dachary about 8 years ago

I think we should run flake8 on build.

Actions #6

Updated by Dan Mick about 8 years ago

I would support that enhancement

Actions #7

Updated by Ken Dreyer about 8 years ago

It's fine to run flake8 on build, but can we not use tox or a virtualenv, and use python-flake8 from the distro instead?

That would reduce the complexity of the build considerably.

Actions #8

Updated by Loïc Dachary over 7 years ago

  • Assignee deleted (Loïc Dachary)
Actions #9

Updated by Alfredo Deza over 7 years ago

It is not necessary to install tox to run flake8. This can easily be done with the flake8 system package.

Running virtualenv everywhere every time is a burden

Actions #10

Updated by Ian Colle over 7 years ago

  • Assignee set to Loïc Dachary

Please create an RFE to run flake8 on builds, but stop creating the virtualenv for non-test builds.

Actions #11

Updated by Loïc Dachary over 7 years ago

  • Status changed from New to Fix Under Review

Here is a tentative implementation, please let me know what you think: https://github.com/ceph/ceph/pull/11177

Actions #12

Updated by Loïc Dachary over 7 years ago

  • Status changed from Fix Under Review to 12
  • Assignee deleted (Loïc Dachary)
Actions #13

Updated by Ian Colle over 7 years ago

  • Assignee set to Loïc Dachary
Actions #14

Updated by Loïc Dachary over 7 years ago

  • Assignee deleted (Loïc Dachary)

I don't know how to fix this, someone else will have to work on it.

Actions #15

Updated by Patrick Donnelly over 4 years ago

  • Status changed from 12 to New
Actions #16

Updated by Sage Weil almost 3 years ago

  • Status changed from New to Won't Fix
Actions

Also available in: Atom PDF