Update reqwest requirement from 0.11.18 to 0.12.1 #113
4 passed, 6 failed and 0 skipped
❌ target/nextest/ci/junit.xml
10 tests were completed in 10s with 4 passed, 6 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| ha-mitaffald | 4✅ | 5❌ | NaNms | |
| ha-mitaffald::full_flow | 1❌ | NaNms |
❌ ha-mitaffald
✅ mitaffald::tests::can_calculate_next_date_at_year_end
✅ mitaffald::tests::can_calculate_next_date_future
✅ mitaffald::tests::can_calculate_next_date_today
❌ mitaffald::tests::can_extract_data_using_address_id
thread 'mitaffald::tests::can_extract_data_using_address_id' panicked at src/mitaffald/mod.rs:189:26:
❌ mitaffald::tests::can_extract_data_using_traditional_address
thread 'mitaffald::tests::can_extract_data_using_traditional_address' panicked at src/mitaffald/mod.rs:217:26:
❌ mitaffald::tests::can_handle_server_error
thread 'mitaffald::tests::can_handle_server_error' panicked at src/mitaffald/mod.rs:305:26:
❌ mitaffald::tests::using_traditional_address_can_detect_address_not_found
thread 'mitaffald::tests::using_traditional_address_can_detect_address_not_found' panicked at src/mitaffald/mod.rs:247:26:
❌ mitaffald::tests::using_addressid_can_detect_address_not_found
thread 'mitaffald::tests::using_addressid_can_detect_address_not_found' panicked at src/mitaffald/mod.rs:276:26:
✅ mitaffald::tests::can_handle_no_responses
❌ ha-mitaffald::full_flow
❌ smoke_test
thread 'smoke_test' panicked at tests/full_flow.rs:27:33:
Annotations
Check failure on line 0 in target/nextest/ci/junit.xml
github-actions / Unit Tests
ha-mitaffald ► mitaffald::tests::can_extract_data_using_address_id
Failed test found in:
target/nextest/ci/junit.xml
Error:
thread 'mitaffald::tests::can_extract_data_using_address_id' panicked at src/mitaffald/mod.rs:189:26:
Raw output
thread 'mitaffald::tests::can_extract_data_using_address_id' panicked at src/mitaffald/mod.rs:189:26:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Check failure on line 0 in target/nextest/ci/junit.xml
github-actions / Unit Tests
ha-mitaffald ► mitaffald::tests::can_extract_data_using_traditional_address
Failed test found in:
target/nextest/ci/junit.xml
Error:
thread 'mitaffald::tests::can_extract_data_using_traditional_address' panicked at src/mitaffald/mod.rs:217:26:
Raw output
thread 'mitaffald::tests::can_extract_data_using_traditional_address' panicked at src/mitaffald/mod.rs:217:26:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Check failure on line 0 in target/nextest/ci/junit.xml
github-actions / Unit Tests
ha-mitaffald ► mitaffald::tests::can_handle_server_error
Failed test found in:
target/nextest/ci/junit.xml
Error:
thread 'mitaffald::tests::can_handle_server_error' panicked at src/mitaffald/mod.rs:305:26:
Raw output
thread 'mitaffald::tests::can_handle_server_error' panicked at src/mitaffald/mod.rs:305:26:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Check failure on line 0 in target/nextest/ci/junit.xml
github-actions / Unit Tests
ha-mitaffald ► mitaffald::tests::using_traditional_address_can_detect_address_not_found
Failed test found in:
target/nextest/ci/junit.xml
Error:
thread 'mitaffald::tests::using_traditional_address_can_detect_address_not_found' panicked at src/mitaffald/mod.rs:247:26:
Raw output
thread 'mitaffald::tests::using_traditional_address_can_detect_address_not_found' panicked at src/mitaffald/mod.rs:247:26:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Check failure on line 0 in target/nextest/ci/junit.xml
github-actions / Unit Tests
ha-mitaffald ► mitaffald::tests::using_addressid_can_detect_address_not_found
Failed test found in:
target/nextest/ci/junit.xml
Error:
thread 'mitaffald::tests::using_addressid_can_detect_address_not_found' panicked at src/mitaffald/mod.rs:276:26:
Raw output
thread 'mitaffald::tests::using_addressid_can_detect_address_not_found' panicked at src/mitaffald/mod.rs:276:26:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Check failure on line 0 in target/nextest/ci/junit.xml
github-actions / Unit Tests
ha-mitaffald::full_flow ► smoke_test
Failed test found in:
target/nextest/ci/junit.xml
Error:
thread 'smoke_test' panicked at tests/full_flow.rs:27:33:
Raw output
thread 'smoke_test' panicked at tests/full_flow.rs:27:33:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace