Skip to content

bump(dpdk-sys): Manual bump to investigate update failures #1102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
qmonnet wants to merge 1 commit into from

bump(dpdk-sys): Manual bump to investigate update failures

d9940b4
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Closed

bump(dpdk-sys): Manual bump to investigate update failures #1102

bump(dpdk-sys): Manual bump to investigate update failures
d9940b4
Select commit
Loading
Failed to load commit list.
GitHub Actions / test-report-fuzz-sterile:true failed Dec 2, 2025 in 0s

327 tests run, 321 passed, 0 skipped, 6 failed.

Annotations

Check failure on line 1 in dataplane-hardware

See this annotation in the file changed.

@github-actions github-actions / test-report-fuzz-sterile:true

dataplane-hardware.scan::test::bind_nic_test 

thread 'scan::test::bind_nic_test' (13213) panicked at hardware/src/scan.rs:282:5
Raw output 
thread 'scan::test::bind_nic_test' (13213) panicked at hardware/src/scan.rs:282:5:
test container exited with code 127
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test scan::test::bind_nic_test ... FAILED

failures:

failures:
    scan::test::bind_nic_test

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

Check failure on line 1 in dataplane-hardware

See this annotation in the file changed.

@github-actions github-actions / test-report-fuzz-sterile:true

dataplane-hardware.scan::test::bind_fabric_nics_and_skip_mgmt_nic 

thread 'scan::test::bind_fabric_nics_and_skip_mgmt_nic' (13194) panicked at hardware/src/scan.rs:254:5
Raw output 
thread 'scan::test::bind_fabric_nics_and_skip_mgmt_nic' (13194) panicked at hardware/src/scan.rs:254:5:
test container exited with code 127
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test scan::test::bind_fabric_nics_and_skip_mgmt_nic ... FAILED

failures:

failures:
    scan::test::bind_fabric_nics_and_skip_mgmt_nic

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

Check failure on line 1 in dataplane-hardware

See this annotation in the file changed.

@github-actions github-actions / test-report-fuzz-sterile:true

dataplane-hardware.scan::test::collect_them_all_and_bind_them 

thread 'scan::test::collect_them_all_and_bind_them' (13234) panicked at hardware/src/scan.rs:228:5
Raw output 
thread 'scan::test::collect_them_all_and_bind_them' (13234) panicked at hardware/src/scan.rs:228:5:
test container exited with code 127
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test scan::test::collect_them_all_and_bind_them ... FAILED

failures:

failures:
    scan::test::collect_them_all_and_bind_them

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

Check failure on line 1 in dataplane::bin/dataplane

See this annotation in the file changed.

@github-actions github-actions / test-report-fuzz-sterile:true

dataplane::bin/dataplane.test::root_filesystem_in_vm_is_read_only 

thread 'test::root_filesystem_in_vm_is_read_only' (13790) panicked at dataplane/src/main.rs:188:5
Raw output 
thread 'test::root_filesystem_in_vm_is_read_only' (13790) panicked at dataplane/src/main.rs:188:5:
test container exited with code 127
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test test::root_filesystem_in_vm_is_read_only ... FAILED

failures:

failures:
    test::root_filesystem_in_vm_is_read_only

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 4 filtered out; finished in 0.28s

Check failure on line 1 in dataplane::bin/dataplane

See this annotation in the file changed.

@github-actions github-actions / test-report-fuzz-sterile:true

dataplane::bin/dataplane.test::run_filesystem_in_vm_is_read_write 

thread 'test::run_filesystem_in_vm_is_read_write' (13945) panicked at dataplane/src/main.rs:195:5
Raw output 
thread 'test::run_filesystem_in_vm_is_read_write' (13945) panicked at dataplane/src/main.rs:195:5:
test container exited with code 127
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test test::run_filesystem_in_vm_is_read_write ... FAILED

failures:

failures:
    test::run_filesystem_in_vm_is_read_write

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 4 filtered out; finished in 0.17s

Check failure on line 1 in dataplane::bin/dataplane

See this annotation in the file changed.

@github-actions github-actions / test-report-fuzz-sterile:true

dataplane::bin/dataplane.test::tmp_filesystem_in_vm_is_read_write 

thread 'test::tmp_filesystem_in_vm_is_read_write' (14021) panicked at dataplane/src/main.rs:201:5
Raw output 
thread 'test::tmp_filesystem_in_vm_is_read_write' (14021) panicked at dataplane/src/main.rs:201:5:
test container exited with code 127
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test test::tmp_filesystem_in_vm_is_read_write ... FAILED

failures:

failures:
    test::tmp_filesystem_in_vm_is_read_write

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 4 filtered out; finished in 0.13s
View more details on GitHub Actions