Stardust XR•17mo ago

molecules - tests failing

    Finished test [unoptimized + debuginfo] target(s) in 0.04s
     Running unittests src/lib.rs (target/debug/deps/stardust_xr_molecules-c0b6ff7264407201)

running 2 tests
test keyboard::keyboard_events ... FAILED
test mouse::mouse_events ... FAILED

failures:

---- keyboard::keyboard_events stdout ----
thread 'keyboard::keyboard_events' panicked at 'called `Result::unwrap()` on an `Err` value: ConnectionFailure', src/keyboard.rs:155:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- mouse::mouse_events stdout ----
thread 'mouse::mouse_events' panicked at 'called `Result::unwrap()` on an `Err` value: ConnectionFailure', src/mouse.rs:101:10


failures:
    keyboard::keyboard_events
    mouse::mouse_events

test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass `--lib`

    Finished test [unoptimized + debuginfo] target(s) in 0.04s
     Running unittests src/lib.rs (target/debug/deps/stardust_xr_molecules-c0b6ff7264407201)

running 2 tests
test keyboard::keyboard_events ... FAILED
test mouse::mouse_events ... FAILED

failures:

---- keyboard::keyboard_events stdout ----
thread 'keyboard::keyboard_events' panicked at 'called `Result::unwrap()` on an `Err` value: ConnectionFailure', src/keyboard.rs:155:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- mouse::mouse_events stdout ----
thread 'mouse::mouse_events' panicked at 'called `Result::unwrap()` on an `Err` value: ConnectionFailure', src/mouse.rs:101:10


failures:
    keyboard::keyboard_events
    mouse::mouse_events

test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass `--lib`

15 Replies

Nova•17mo ago

this however really should work so i'll look into it put it as a github issue and on the roadmap project board please?

Saphira Kai•17mo ago

i first noticed the error over ssh, so i assumed it was just because it wasn't connected to a display or something, but it happens locally too on it

Nova•17mo ago

thanks :D

Saphira Kai•17mo ago

:D should i add this to Planned or? @Nova oh, probably ASAP

Nova•17mo ago

add it to MVP actually no ASAP is good

Saphira Kai•17mo ago

should there be a section specifically for bugs? actually a different project might be better for that

Nova•17mo ago

idk maybe? but we need to solve them so... augh idk

Saphira Kai•17mo ago

the way i see it is like, this project is dedicated to defining the features that will need to be in place at different stages of the project and a different project could be dedicated to the gritty details of implementing those features, including tracking bugs and things that need to be implemented before implementing something else

Nova•17mo ago

hmm i guess so augh i really wish we had someone to do project management

Saphira Kai•17mo ago

haha, yeah I think I'll create a new project called Implementation for this sound good to you?

Nova•17mo ago

ok!

Saphira Kai•17mo ago

okie! :3

Nova•17mo ago

this is where i enter choice paralysis since i have zero clue of if this is a good idea or if we'll use that or so on

Saphira Kai•17mo ago

haha i definitely get that we should write a document for contributors that just has a list of what to do when x like "filing a bug report" with instructions to follow every time for consistency basically an FAQ i guess

Nova•17mo ago

good idea

Gaming

Programming

molecules - tests failing