ci: install tox in py38 job
A better approach would be to backport python definition in several jobs inside gitlab-ci-templates
Status | Name | Job ID | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
Lint | |||||||||
failed | black |
#487549
lint
black
|
00:00:36
|
|
|||||
passed | check-manifest |
#487552
lint
check-manifest
|
00:00:29
|
|
|||||
passed | flake8 |
#487550
lint
flake8
|
00:00:41
|
|
|||||
failed | mypy |
#487551
lint
mypy
allowed to fail
|
00:00:53
|
|
|||||
passed | yamllint |
#487553
lint
yamllint
|
00:00:33
|
|
|||||
Tests | |||||||||
failed | py3 |
#487554
tests
py3
|
00:00:46
|
|
|||||
passed | py38 |
#487555
tests
py3
|
00:00:56
|
|
|||||
After Tests | |||||||||
skipped | trigger-cubicweb-pipeline |
#487556
bridge
|
|||||||
skipped | trigger-logilab-constraint-pipeline |
#487560
bridge
|
|||||||
skipped | trigger-logilab-database-pipeline |
#487559
bridge
|
|||||||
skipped | trigger-logilab-mtconverter-pipeline |
#487561
bridge
|
|||||||
skipped | trigger-rql-pipeline |
#487558
bridge
|
|||||||
skipped | trigger-yams-pipeline |
#487557
bridge
|
|||||||
Name | Stage | Failure | ||
---|---|---|---|---|
failed
|
py3 | Tests | ||
|
||||
failed
|
mypy | Lint | ||
|
||||
failed
|
black | Lint | ||
|