cargo test fails
- Dominant language
- Rust
- Stars
- 326
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
`cargo test` fails for me with this error -
``` bash
running 2 tests
test post_backend ... FAILED
test get_backend ... FAILED
failures:
---- post_backend stdout ----
thread 'post_backend' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Error { repr: Os { code: 61, message: "Connection refused" } })', ../src/libcore/result.rs:785
---- get_backend stdout ----
thread 'get_backend' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Error { repr: Os { code: 61, message: "Connection refused" } })', ../src/libcore/result.rs:785
note: Run with `RUST_BACKTRACE=1` for a backtrace.
```
Am I missing something? I am running rustup with stable channel -
```
$ cargo -V
cargo 0.11.0-nightly (259324c 2016-05-20)
$ rustc -V
rustc 1.10.0 (cfcb716cf 2016-07-03)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running `cargo test` with the reported Rust toolchain and inspect the `post_backend` and `get_backend` tests to identify which service or endpoint refuses the connection. Done means both tests run successfully without the connection-refused panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100