michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/scripts/requirements-run-test.txt

19 lines
337 B
Plaintext
Raw Permalink Normal View History

scripts/requirements: Split & document requirement.txt Split up requirements.txt into several files so that CI tools can utilize/reference the specific requirements-<FOO>.txt they may need while keep things in sync with the development. This is to reduce both time and amount of work CI actions due to python package install. Create the following groupings: 1. BASE - needed to build or create zephyr images 2. BUILD-TEST - need to run compile/build tests 3. DOC - need to build the docs 4. RUN-TEST - need for runtime testing 5. EXTRAS - optional or useful for development/developers workflow Also tried to add a comment about what or why a given package is being pulled in for. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-02-07 21:58:00 +01:00
# RUN-TEST: required to do run time tests of zephyr
#
# things used by sanitycheck or related in run time testing
# used to connect to boards for console IO
pyserial
# used to flash & debug various boards
pyocd>=0.24.0
# used by sanitycheck for board/hardware map
tabulate
manifest: upgrade mcuboot Include build assert macros rework. Update pip requirements by cbor package required by MCUBoot since https://github.com/JuulLabs-OSS/mcuboot/pull/674 was merge. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2020-03-27 11:35:49 +01:00
# used by mcuboot
cbor>=1.0.0
requirements: add psutil, needed by sanitycheck Needed for tracking cpu time in sanitycheck. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2020-05-06 14:26:00 +02:00
# use for sanitycheck
psutil
Copy permalink