-
Notifications
You must be signed in to change notification settings - Fork 746
Closed
Description
The feature-powerset task of the daily-tests.yml
job has been broken for a little while:
Run cargo hack check --package rustls --feature-powerset --no-dev-deps --group-features aws_lc_rs,aws-lc-rs --group-features fips,aws_lc_rs --mutually-exclusive-features fips,ring --mutually-exclusive-features custom_provider,aws_lc_rs --mutually-exclusive-features custom_provider,ring
cargo hack check --package rustls --feature-powerset --no-dev-deps --group-features aws_lc_rs,aws-lc-rs --group-features fips,aws_lc_rs --mutually-exclusive-features fips,ring --mutually-exclusive-features custom_provider,aws_lc_rs --mutually-exclusive-features custom_provider,ring
shell: /usr/bin/bash -e {0}
env:
CARGO_HOME: /home/runner/.cargo
CARGO_INCREMENTAL: 0
CARGO_TERM_COLOR: always
RUSTFLAGS: --deny warnings
info: --no-dev-deps modifies real `Cargo.toml` while cargo-hack is running and restores it when finished
/home/runner/work/_temp/bde848db-eb3d-4309-bc61-4db425eaf180.sh: line 1: 2075 Segmentation fault (core dumped) cargo hack check --package rustls --feature-powerset --no-dev-deps --group-features aws_lc_rs,aws-lc-rs --group-features fips,aws_lc_rs --mutually-exclusive-features fips,ring --mutually-exclusive-features custom_provider,aws_lc_rs --mutually-exclusive-features custom_provider,ring
Error: Process completed with exit code 139.
It looks like the last passing run was Feb 27th. In both the passing runs and the failing runs we're using cargo-hack 0.6.35
so something else must have shifted.
Metadata
Metadata
Assignees
Labels
No labels