feedc0de/esp-idf
1
0
Fork 0
forked from espressif/esp-idf
Code Pull Requests Activity

Merge branch 'ci/fix_get_binaries_from_pipeline_via_build_report' into 'master'

Browse Source 
ci: fix get binaries from pipeline via the build report

See merge request espressif/esp-idf!28432
This commit is contained in:
Fu Hanxi
2024-01-12 17:25:04 +08:00
parent 312a8d38f0 25e3e3b384
commit 5a17bf83ff
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
conftest.py
View File

@@ -124,7 +124,7 @@ class BuildReportDownloader:
f.seek(0) f.seek(0)
with zipfile.ZipFile(f) as zip_ref: with zipfile.ZipFile(f) as zip_ref:
zip_ref.extractall() zip_ref.extractall(IDF_PATH)
@pytest.fixture(scope='session') @pytest.fixture(scope='session')

4
docs/en/contribute/esp-idf-tests-with-pytest.rst
View File

@@ -576,6 +576,10 @@ Run pytest with ``--pipeline-id <pipeline_id>`` to force pytest to download the
Even if you have ``build_esp32_default``, or ``build`` directory locally, pytest would still download the binaries from pipeline 123456 and place the binaries in ``build_esp32_default``. Then run the test case with this binary. Even if you have ``build_esp32_default``, or ``build`` directory locally, pytest would still download the binaries from pipeline 123456 and place the binaries in ``build_esp32_default``. Then run the test case with this binary.
.. note::
<pipeline_id> should be the parent pipeline id. You can copy it in your MR page.
Pytest Tips and Tricks Pytest Tips and Tricks
====================== ======================