[flake] avalanchego_conformance_sdk unit test::key

[exdx]

See https://github.com/ava-labs/avalanche-rs/actions/runs/6040807095/job/16392431819 for an example flake.

Compiling avalanchego-conformance v0.0.0 (/home/runner/work/avalanche-rs/avalanche-rs/tests/avalanchego-conformance)
    Finished test [unoptimized + debuginfo] target(s) in 2m 36s
     Running unittests src/lib.rs (target/debug/deps/avalanchego_conformance-70b5c63bbd0deef4)

running 8 tests
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
thread 'tests::key::bls::generate_bls_signature' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test tests::key::bls::generate_bls_signature ... FAILED
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
thread 'tests::key::certificates::load_certificate_to_node_id' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
test tests::key::certificates::load_certificate_to_node_id ... FAILED
thread 'tests::key::certificates::generate_certificate_to_node_id' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
test tests::key::certificates::generate_certificate_to_node_id ... FAILED
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
thread 'tests::key::secp256k1::generate' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
test tests::key::secp256k1::generate ... FAILED
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
thread 'tests::key::secp256k1::recover_hash_public_key' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
test tests::key::secp256k1::recover_hash_public_key ... FAILED
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
thread 'tests::key::secp256k1::load' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
test tests::key::secp256k1::load ... FAILED
thread 'tests::packer::build_vertex::build_vertex' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
test tests::packer::build_vertex::build_vertex ... FAILED
[2023-08-31T18:03:21Z INFO  avalanchego_conformance_sdk] creating a new client with http://127.0.0.1:22342/
thread 'tests::ping' panicked at 'called `Result::unwrap()` on an `Err` value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/runner/work/avalanche-rs/avalanche-rs/avalanchego-conformance-sdk/src/lib.rs:54:72
test tests::ping ... FAILED

successes:

successes:

failures:

failures:
    tests::key::bls::generate_bls_signature
    tests::key::certificates::generate_certificate_to_node_id
    tests::key::certificates::load_certificate_to_node_id
    tests::key::secp256k1::generate
    tests::key::secp256k1::load
    tests::key::secp256k1::recover_hash_public_key
    tests::packer::build_vertex::build_vertex
    tests::ping

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

error: test failed, to rerun pass `-p avalanchego-conformance --lib`

[Sanghren]

I see this in the failed action run :

Caught SIGILL in blst_cgo_init, consult /bindings/go/README.md.

Trying to replicate it but so far no luck.

I've seen people talking about same kind of issue here https://github.com/orgs/community/discussions/43153 or https://hackmd.io/@inphi/SJMXL1P6c#Troubleshootingassistance that adding some env variable before running the avalanchego-conformance. But as per comments it does not seems 100% certain that it would help.

[exdx]

I see this in the failed action run :

Caught SIGILL in blst_cgo_init, consult /bindings/go/README.md.

Trying to replicate it but so far no luck.

I've seen people talking about same kind of issue here https://github.com/orgs/community/discussions/43153 or https://hackmd.io/@inphi/SJMXL1P6c#Troubleshootingassistance that adding some env variable before running the avalanchego-conformance. But as per comments it does not seems 100% certain that it would help.

Thanks for taking a look. I agree we need to debug further and potentially update the go version.