Skip to content

CI: re-enable checks, by changing errant tab back to spaces. #5359

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.

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
wants to merge 1 commit into from

Conversation

rustyrussell
Copy link
Contributor

FFS GH!

Changelog-None

And the Python contrib/ stuff seems to fail under VALGRIND, so attach
it to a normal make line.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Copy link
Collaborator

@vincenzopalazzo vincenzopalazzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 748ad06

@vincenzopalazzo
Copy link
Collaborator

I'm starting to think that the following error can be caused from the Rust compiler

Valgrind error file: valgrind-errors.61097
==61097== Syscall param statx(file_name) points to unaddressable byte(s)
==61097==    at 0x4B0188E: statx (statx.c:29)
==61097==    by 0x1131811: std::sys::unix::fs::try_statx (weak.rs:178)
==61097==    by 0x1124970: std::fs::buffer_capacity_required (fs.rs:851)
==61097==    by 0x1124AEB: <std::fs::File as std::io::Read>::read_to_string (fs.rs:644)
==61097==    by 0x10DA988: num_cpus::linux::Cgroup::param (linux.rs:214)
==61097==    by 0x10DA819: num_cpus::linux::Cgroup::quota_us (linux.rs:203)
==61097==    by 0x10DA6A2: num_cpus::linux::Cgroup::cpu_quota (linux.rs:188)
==61097==    by 0x10DA281: num_cpus::linux::load_cgroups (linux.rs:149)
==61097==    by 0x10D9F1D: num_cpus::linux::init_cgroups (linux.rs:129)
==61097==    by 0x10DCAA8: core::ops::function::FnOnce::call_once (function.rs:227)
==61097==    by 0x10DC429: std::sync::once::Once::call_once::{{closure}} (once.rs:276)
==61097==    by 0x21EE89: std::sync::once::Once::call_inner (once.rs:434)
==61097==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==61097== 
==61097== Syscall param statx(buf) points to unaddressable byte(s)
==61097==    at 0x4B0188E: statx (statx.c:29)
==61097==    by 0x1131811: std::sys::unix::fs::try_statx (weak.rs:178)
==61097==    by 0x1124970: std::fs::buffer_capacity_required (fs.rs:851)
==61097==    by 0x1124AEB: <std::fs::File as std::io::Read>::read_to_string (fs.rs:644)
==61097==    by 0x10DA988: num_cpus::linux::Cgroup::param (linux.rs:214)
==61097==    by 0x10DA819: num_cpus::linux::Cgroup::quota_us (linux.rs:203)
==61097==    by 0x10DA6A2: num_cpus::linux::Cgroup::cpu_quota (linux.rs:188)
==61097==    by 0x10DA281: num_cpus::linux::load_cgroups (linux.rs:149)
==61097==    by 0x10D9F1D: num_cpus::linux::init_cgroups (linux.rs:129)
==61097==    by 0x10DCAA8: core::ops::function::FnOnce::call_once (function.rs:227)
==61097==    by 0x10DC429: std::sync::once::Once::call_once::{{closure}} (once.rs:276)
==61097==    by 0x21EE89: std::sync::once::Once::call_inner (once.rs:434)
==61097==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==61097==
--------------------------------------------------------------------------------
Leaving base_dir /tmp/ltests-pq6me7dk intact, it still has test sub-directories with failure details: ['test_peers_1']

@rustyrussell
Copy link
Contributor Author

Fixed better in #5364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants