Skip to content

tests/run-tests.py: Use TEST_TIMEOUT as timeout for bare-metal tests. #17697

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

dpgeorge
Copy link
Member

Summary

This TEST_TIMEOUT parameter is already used for PC-based tests (eg unix and webassembly ports), and it makes sense for it to be used for bare-metal ports as well. That way the timeout is configurable for all targets.

Because this increases the default timeout from 10s to 30s, this fixes some long-running tests that would previously fail due to a timeout such as thread/stress_aes.py on ESP32.

Testing

Tested with ESP32_GENERIC firmware. The thread/stress_aes.py test now passes (previously it would fail due to timeout).

@dpgeorge dpgeorge added the tests Relates to tests/ directory in source label Jul 17, 2025
@dpgeorge
Copy link
Member Author

@hmaerki FYI. This should fix both octoprobe/testbed_micropython#37 and octoprobe/testbed_micropython#40

Copy link

codecov bot commented Jul 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.37%. Comparing base (b7e734b) to head (941b7e3).
Report is 6 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #17697   +/-   ##
=======================================
  Coverage   98.37%   98.37%           
=======================================
  Files         171      171           
  Lines       22210    22210           
=======================================
  Hits        21849    21849           
  Misses        361      361           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

@hmaerki
Copy link
Contributor

hmaerki commented Jul 20, 2025

stress_aes.py / pow3_intbig.py.out does not timeout anymore in https://reports.octoprobe.org/github_selfhosted_testrun_185/octoprobe_summary_report.html.

Please merge this PR - thanks!

dpgeorge added 2 commits July 23, 2025 12:42
Signed-off-by: Damien George <damien@micropython.org>
This parameter is already used for PC-based tests (eg unix and webassembly
ports), and it makes sense for it to be used for bare-metal ports as well.
That way the timeout is configurable for all targets.

Because this increases the default timeout from 10s to 30s, this fixes some
long-running tests that would previously fail due to a timeout such as
`thread/stress_aes.py` on ESP32.

Signed-off-by: Damien George <damien@micropython.org>
@dpgeorge dpgeorge force-pushed the tests-run-tests-use-timeout-for-pyboard-exec branch from 2a7e80e to 941b7e3 Compare July 23, 2025 02:43
@dpgeorge dpgeorge merged commit 941b7e3 into micropython:master Jul 23, 2025
69 checks passed
@dpgeorge dpgeorge deleted the tests-run-tests-use-timeout-for-pyboard-exec branch July 23, 2025 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Relates to tests/ directory in source
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy