Skip to content
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

[Task (SC-Platform)]: Fix iota-core unsafe precondition violation for slice::from_raw_parts #1667

Closed
PhilippGackstatter opened this issue Aug 7, 2024 · 2 comments
Labels
sc-platform Issues related to the Smart Contract Platform group.

Comments

@PhilippGackstatter
Copy link

Description

These are from current develop (79d0e352dab06a80100ba08f730acd06c2755f24) when running cargo nextest run --package iota-core {test_name} with the respective test name.

--- STDERR:              iota-core authority::authority_store_pruner::pprof_tests::ensure_no_tombstone_fragmentation_in_stack_frame_with_ignore_tombstones ---
thread 'authority::authority_store_pruner::pprof_tests::ensure_no_tombstone_fragmentation_in_stack_frame_with_ignore_tombstones' panicked at library/core/src/panicking.rs:220:5:
unsafe precondition(s) violated: slice::from_raw_parts requires the pointer to be aligned and non-null, and the total size of the slice not to exceed `isize::MAX`
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread caused non-unwinding panic. aborting.

and

--- STDERR:              iota-core authority::authority_store_pruner::pprof_tests::ensure_no_tombstone_fragmentation_in_stack_frame_after_flush ---
thread 'authority::authority_store_pruner::pprof_tests::ensure_no_tombstone_fragmentation_in_stack_frame_after_flush' panicked at library/core/src/panicking.rs:220:5:
unsafe precondition(s) violated: slice::from_raw_parts requires the pointer to be aligned and non-null, and the total size of the slice not to exceed `isize::MAX`
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread caused non-unwinding panic. aborting.

This requires an investigation first where this error comes from, as no one has looked into it yet.

@PhilippGackstatter PhilippGackstatter added the sc-platform Issues related to the Smart Contract Platform group. label Aug 7, 2024
@PhilippGackstatter PhilippGackstatter added this to the SC-Platform/Testnet milestone Aug 7, 2024
@DaughterOfMars
Copy link
Contributor

There is already an issue for this #958

@lzpap
Copy link
Member

lzpap commented Aug 7, 2024

There is already an issue for this #958

@DaughterOfMars since you closed this issue, please copy over the context to the already existing one. #958 doesn't have any meaningful info on what tests are failing, hence we did not find it with @PhilippGackstatter when we looked into the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sc-platform Issues related to the Smart Contract Platform group.
Projects
None yet
Development

No branches or pull requests

3 participants