Make test.sh test and build secp256k1-sys

[elichai]

There are currently 2 tests in secp256k1-sys and our CI doesn't run them.
This fixes that, but instead of adding another section to tests.sh I added secp256k1-sys to the workspace and made the builds and tests run on the whole workspace.
I had to exclude no_std_test from the workspace because it only works on nightly.

I also fixed a bug where if you pass both DO_ASAN=true and DO_BENCH=true it will try to do the benchmarks on no_std_test

[elichai]

Damn it. of course 1.29 doesn't have the --workspace flag.
at least there's the --all which does the same thing (even though it's deprecated now)

[apoelstra]

concept ACK.

I'm surprised you need --all. IIRC if you run cargo build or cargo test in the root of a workspace it'll run the build/test on all crates in the workspace?

[elichai]

concept ACK.

I'm surprised you need --all. IIRC if you run cargo build or cargo test in the root of a workspace it'll run the build/test on all crates in the workspace?

It sounds like you're right, but for some reason I don't see those tests running without --all and if I add panics they don't fail

The default members of a workspace can be set explicitly with the workspace.default-members key in the root manifest. If this is not set, a virtual workspace will include all workspace members (equivalent to passing --workspace), and a non-virtual workspace will include only the root crate itself.

https://www.mankier.com/1/cargo-test#Options-Package_Selection

I'll try to find time to look into it and maybe open/find a cargo bug

[apoelstra]

ack d95cb53

[apoelstra]

Just kidding. Needs rebase.

[apoelstra]

ack 21f231b

Cool find with this VERBOSE variable.