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
pmem2_badblock/TEST[0-5]: failed memcheck - injecting bad block failed #5636
Labels
CI: Disabled
Temporarily disabled from testing
libpmem2
libpmem- and libpmem2-related
Priority: 1 urgent
QA: CI
.github/ and utils/ related to automated testing
Type: Bug
A previously unknown bug in PMDK
Milestone
Comments
grom72
changed the title
pmem2_badblock/TEST[0-5]: FAILED
pmem2_badblock/TEST[0-5]: failed memcheck
May 15, 2023
grom72
added
libpmem2
libpmem- and libpmem2-related
QA: CI
.github/ and utils/ related to automated testing
labels
May 15, 2023
grom72
changed the title
pmem2_badblock/TEST[0-5]: failed memcheck
pmem2_badblock/TEST[0-5]: failed memcheck - injecting bad block failed
May 15, 2023
grom72
added
Exposure: Medium
Priority: 1 urgent
and removed
libpmem2
libpmem- and libpmem2-related
Exposure: Medium
labels
May 15, 2023
osalyk
added a commit
to osalyk/pmdk
that referenced
this issue
May 16, 2023
osalyk
added a commit
to osalyk/pmdk
that referenced
this issue
May 17, 2023
osalyk
added a commit
to osalyk/pmdk
that referenced
this issue
May 17, 2023
osalyk
added a commit
to osalyk/pmdk
that referenced
this issue
May 17, 2023
osalyk
added a commit
to osalyk/pmdk
that referenced
this issue
May 17, 2023
Temporary solution until a platform supporting the tested functionality is ready
grom72
added a commit
that referenced
this issue
May 17, 2023
test: disable pmem2_badblock tests due to #5636
Explanation in #5652 |
grom72
added a commit
to grom72/pmdk
that referenced
this issue
Jul 10, 2023
Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
Jul 11, 2023
Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
Jul 11, 2023
Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
Jul 13, 2023
Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CI: Disabled
Temporarily disabled from testing
libpmem2
libpmem- and libpmem2-related
Priority: 1 urgent
QA: CI
.github/ and utils/ related to automated testing
Type: Bug
A previously unknown bug in PMDK
ISSUE: pmem2_badblock/TEST[0-5] failed under [valgrind (self-hosted, rhel, RUNTESTS.py --force-enable memcheck)] - injecting bad block failed
Environment Information
Please provide a reproduction of the bug:
pmem2_badblock/TEST[0-5] failed under valgrind (self-hosted, rhel, RUNTESTS.py --force-enable memcheck)
with error message:
failed to execute command sudo ndctl inject-error --block=0 --count=1 namespace0.2: injecting bad block failed
How often bug is revealed: (always, often, rare): always
Actual behavior:
Expected behavior:
Details
Additional information about Priority and Help Requested:
Are you willing to submit a pull request with a proposed change?
Requested priority: (Showstopper, High, Medium, Low)
The text was updated successfully, but these errors were encountered: