In CI, for your #rustlang programs, what do you run?
-
-
yeah i looked at yours before tweeting this and decided it was TMI. my favorite part is your branch names
- 1 more reply
New conversation -
-
I usually run them on steps, so cargo build is used to download dependencies to the cache and ensure the code compiles
-
right, but cargo test downloads dependencies and ensures the code compiles too
- 1 more reply
New conversation -
-
-
cross compilation. Or when you need to link to other libraries that aren't present -- Firefox/Stylo have this problem though we solve it by moving tests that rely on gecko symbols into gecko itself.
-
Also, `cargo test` will change cfg(test), so your non-mocking code may never get tested.
- 1 more reply
New conversation -
-
-
Running `cargo build` catches compile errors which only emerge when cfg(test) does not hold (I think dead code is the common case). I'm not sure if `cargo test` also builds the binary in a crate which has a lib and bin.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'm building a different crate than the one I test (building a C API, while I'm testing the main crate)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I have certain things (like time consuming animations) disabled via cfg during testing. I still want those things to be built though in case something is wrong.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think defaults for workspaces have changed, but I still don't trust it to build and test everything, so just in case I do build & test, and with --all --verbose args.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.