Tom Rini
authored
When running our tests there are some cases where as part of the Python
2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as
everything wasn't yet migrated. Now that everything is, make sure to
tell virtualenv to use python3. In the case of Travis this is best done
by making the tools test happen after the main tests so that it will
already have been run in all cases, TEST_PY_TOOLS is a subset of
TEST_PY_BD.
Signed-off-by: 
Tom Rini <trini@konsulko.com>| Name | Last commit | Last update |
|---|---|---|
| .github | ||
| Licenses | ||
| api | ||
| arch | ||
| board | ||
| cmd | ||
| common | ||
| configs | ||
| disk | ||
| doc | ||
| drivers | ||
| dts | ||
| env | ||
| examples | ||
| fs | ||
| include | ||
| lib | ||
| net | ||
| post | ||
| scripts | ||
| test | ||
| tools | ||
| .azure-pipelines.yml | ||
| .checkpatch.conf | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| Kbuild | ||
| Kconfig | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| config.mk |