Skip to content
Rust

publishing release data to dl.espressif #400

Sign in to view logs

publishing release data to dl.espressif

publishing release data to dl.espressif #400

GitHub Actions / Test Results failed Jan 7, 2025 in 0s

2 fail, 11 pass in 36m 26s

10 files  ±0  43 suites  ±0   36m 26s ⏱️ - 10m 50s
13 tests  - 4  11 ✅  - 6  0 💤 ±0  2 ❌ +2 
43 runs  ±0  39 ✅  - 4  0 💤 ±0  4 ❌ +4 

Results for commit 5fbf1c4. ± Comparison against earlier commit 5242fac.

Annotations

Check warning on line 0 in Should create a new project based on a template

See this annotation in the file changed.

@github-actions github-actions / Test Results

All 3 runs failed: Installation using default settings create and build sample project Should create a new project based on a template (Should create a new project based on a template) 

./artifacts/test-results-linux-x64-GitHub.zip/results-default-test.xml [took 10s]
./artifacts/test-results-macos-aarch64-GitHub.zip/results-default-test.xml [took 10s]
./artifacts/test-results-windows-x64-GitHub.zip/results-default-test.xml [took 10s]
Raw output 
sdkconfig.ci file not shown after a ls command, file copy failed: expected false to be true
AssertionError: sdkconfig.ci file not shown after a ls command, file copy failed: expected false to be true
    at Context.<anonymous> (file:///Users/runner/work/idf-im-cli/idf-im-cli/tests/script/postInstall.test.js:80:20)

      + expected - actual

      -false
      +true

Check warning on line 0 in Should create a new project based on a template

See this annotation in the file changed.

@github-actions github-actions / Test Results

Installation using mirror jihulab and dl.espressif.com create and build sample project Should create a new project based on a template (Should create a new project based on a template) failed 

./artifacts/test-results-linux-x64-CNRunner.zip/results-CNMirror-test.xml [took 10s]
Raw output 
sdkconfig.ci file not shown after a ls command, file copy failed: expected false to be true
AssertionError: sdkconfig.ci file not shown after a ls command, file copy failed: expected false to be true
    at Context.<anonymous> (file:///home/runner/work/idf-im-cli/idf-im-cli/tests/script/postInstall.test.js:80:20)

      + expected - actual

      -false
      +true

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / Test Results

13 tests found 

There are 13 tests, see "Raw output" for the full list of tests.
Raw output 
Should build project for the selected target ‑ Installation using non-interactive settings create and build sample project Should build project for the selected target
Should create a new project based on a template ‑ Installation using default settings create and build sample project Should create a new project based on a template
Should create a new project based on a template ‑ Installation using mirror jihulab and dl.espressif.com create and build sample project Should create a new project based on a template
Should create a new project based on a template ‑ Installation using non-interactive settings create and build sample project Should create a new project based on a template
Should detect missing requirements ‑ Check if prerequisites are installed Pre-Requisites test on non windows platform Should detect missing requirements
Should install IDF using specified parameters ‑ Installation using mirror jihulab and dl.espressif.com run custom installation using non interactive terminal Should install IDF using specified parameters
Should install IDF using specified parameters ‑ Installation using non-interactive settings run custom installation using non interactive terminal Should install IDF using specified parameters
Should install IDF using wizard and default values ‑ Installation using default settings Check IDF Install Wizard steps Should install IDF using wizard and default values
Should set the target ‑ Installation using non-interactive settings create and build sample project Should set the target
should handle invalid arguments ‑ Installation using default settings CLI Arguments Tests should handle invalid arguments
should offer to install prerequisites and exit upon negative answer ‑ Check if prerequisites are installed Pre-requisites test on Windows should offer to install prerequisites and exit upon negative answer
should show correct version number ‑ Installation using default settings CLI Arguments Tests should show correct version number
should show help with --help argument ‑ Installation using default settings CLI Arguments Tests should show help with --help argument
View more details on GitHub Actions