mirror of
https://github.com/trezor/trezor-firmware.git
synced 2025-08-02 20:08:31 +00:00
![]() Most of the tests complete after a few seconds: ``` ============================================= slowest durations ============================================= 3.94s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.4.0] 3.61s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.6.3] 3.59s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.3.1] 3.50s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_no_backup[core-v2.1.8] 3.48s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_no_backup[core-v2.2.0] 3.48s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_skip_backup[core-v2.1.6] 3.48s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_no_backup[core-v2.1.6] 3.45s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_skip_backup[core-v2.2.0] 3.41s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.6.2] 3.31s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.7.0] 3.10s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.3.5] 3.09s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.3.4] 2.73s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_shamir_recovery[core-v2.5.3] 2.56s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_no_backup[core-v2.1.5] 2.55s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_skip_backup[core-v2.1.4] 2.55s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_reset_skip_backup[core-v2.1.2] 2.45s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_load[core-v2.1.6] 2.44s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_load[core-v2.1.7] 2.43s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_load[core-v2.1.8] 2.43s call tests/upgrade_tests/test_firmware_upgrades.py::test_upgrade_load[core-v2.2.0] ``` [no changelog] |
||
---|---|---|
.clusterfuzzlite | ||
.github | ||
ci | ||
common | ||
core | ||
crypto | ||
docs | ||
legacy | ||
nordic | ||
python | ||
rust | ||
storage | ||
tests | ||
tools | ||
vendor | ||
.clang-format | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.pylintrc | ||
.yamllint.yml | ||
build-docker.sh | ||
CODEOWNERS | ||
COMMITS.md | ||
CONTRIBUTING.md | ||
COPYING | ||
create_monorepo.py | ||
LICENSE.md | ||
Makefile | ||
poetry.lock | ||
poetry.toml | ||
pyproject.toml | ||
README.md | ||
SECURITY.md | ||
setup.cfg | ||
shell.nix |
Trezor Firmware
Repository Structure
ci
: Ancillary files, data, and scripts for the CI pipelinecommon/defs
: JSON coin definitions and support tablescommon/protob
: Common protobuf definitions for the Trezor protocolcommon/tools
: Tools for managing coin definitions and related datacore
: Trezor Core, firmware implementation for Trezor Tcrypto
: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmwaredocs
: Assorted documentationlegacy
: Trezor One firmware implementationpython
: Python client library and thetrezorctl
commandstorage
: NORCOW storage implementation used by both Trezor Core and the Trezor One firmwaretests
: Firmware unit test suitetools
: Miscellaneous build and helper scriptsvendor
: Submodules for external dependencies
Contribute
See CONTRIBUTING.md.
Using Conventional Commits is strongly recommended and might be enforced in future.
Also please have a look at the docs, either in the docs
folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.
Security vulnerability disclosure
Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.
Documentation
See the docs
folder or visit docs.trezor.io.