-
Notifications
You must be signed in to change notification settings - Fork 72
flaky unit test: file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api #3030
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingflaky testLabel given to flaky or otherwise faulty testsLabel given to flaky or otherwise faulty tests
Milestone
Description
Describe the bug
Flaky unit test.
Test name
tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api
Failures
FAIL [ 0.019s] tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api
--- STDOUT: tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api ---
running 1 test
test file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api ... FAILED
failures:
failures:
file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 63 filtered out; finished in 0.00s
--- STDERR: tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api ---
thread 'file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api' panicked at crates/core/tedge_agent/src/file_transfer_server/http_rest.rs:205:9:
assertion `left == right` failed
left: ""
right: "some content"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Build seen on
To Reproduce
Whilst it has not been able to be reproduced locally, you could run the following loop to stop on the first failure:
while just test-unit uploaded_file_can_be_downloaded_from_the_api; do echo running tests; doneExpected behavior
The test should pass consistently.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingflaky testLabel given to flaky or otherwise faulty testsLabel given to flaky or otherwise faulty tests