Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tango
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira issues
Open Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
LOFAR2.0
tango
Commits
85c37f34
Commit
85c37f34
authored
2 years ago
by
Corné Lukken
Browse files
Options
Downloads
Patches
Plain Diff
L2SS-951
: Update tox.ini documentation
parent
1f7b292c
No related branches found
No related tags found
1 merge request
!423
L2SS-951: Disable site-packages and install pytango in tox
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tangostationcontrol/tox.ini
+6
-10
6 additions, 10 deletions
tangostationcontrol/tox.ini
with
6 additions
and
10 deletions
tangostationcontrol/tox.ini
+
6
−
10
View file @
85c37f34
...
@@ -5,21 +5,15 @@ skipsdist = True
...
@@ -5,21 +5,15 @@ skipsdist = True
[testenv]
[testenv]
usedevelop
=
True
usedevelop
=
True
; Module access is a bit of an ugly hack. This is due to testenv inheritance
; Python and tox variables are used to access modules and binaries instead of
; with sitepackages = True`, meaning that global packages can be accessed by the
; directly. This is an artifact of having used sitepackages = true in the past.
; tox environment. Our tango images already have several dependencies system
; wide installed, however, the system wide installation will never look inside
; tox its virtualenv for packages. So accessing stestr and others fail.. We
; can't remove `sitepackages = True` either as we need access to tango and
; installing this package is non-trivial. The solution is to prevent calling
; binaries directly and utilizing python and tox variables to resolve the
; requested module.
; sitepackages = True
install_command
=
{envbindir}/pip3 install {opts} {packages}
install_command
=
{envbindir}/pip3 install {opts} {packages}
passenv
=
HOME
passenv
=
HOME
setenv
=
setenv
=
VIRTUAL_ENV
=
{envdir}
VIRTUAL_ENV
=
{envdir}
PYTHONWARNINGS
=
default::DeprecationWarning
PYTHONWARNINGS
=
default::DeprecationWarning
; Share the same envdir with as many jobs as possible due to extensive time it
; takes to compile the pytango wheel, in addition to its large install size.
envdir
=
{toxworkdir}/testenv
envdir
=
{toxworkdir}/testenv
deps
=
deps
=
-r{toxinidir}/requirements.txt
-r{toxinidir}/requirements.txt
...
@@ -32,6 +26,8 @@ commands =
...
@@ -32,6 +26,8 @@ commands =
{envpython}
-m
stestr
--version
{envpython}
-m
stestr
--version
{envpython}
-m
stestr
run
{posargs}
{envpython}
-m
stestr
run
{posargs}
; We can't detect the current Python version for an environment dynamically
; so each Python version specific job needs its own envdir.
[testenv:py37]
[testenv:py37]
envdir
=
{toxworkdir}/testenvpy37
envdir
=
{toxworkdir}/testenvpy37
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment