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

obj_sync/TEST[2,5-6] shall be fully disabled #5700

Closed
grom72 opened this issue May 30, 2023 · 1 comment
Closed

obj_sync/TEST[2,5-6] shall be fully disabled #5700

grom72 opened this issue May 30, 2023 · 1 comment
Labels
QA: CI .github/ and utils/ related to automated testing Type: Bug A previously unknown bug in PMDK
Milestone

Comments

@grom72
Copy link
Contributor

grom72 commented May 30, 2023

ISSUE: obj_sync TEST[2,5-6] shall be fully disabled

Environment Information

Please provide a reproduction of the bug:

TEST[2,5-6] has been designed to use only with one Valgrind tool e.g.: configure_valgrind helgrind force-enable.
In case of failure (as it is mentioned in #5646), this test shall be fully disabled, as it should not be run with any other Valgrind checker (or even without Valgrind).

How often bug is revealed: (always, often, rare): always

Actual behavior:

Tests are executed with other configurations than what was originally prepared for.
https://github.com/pmem/pmdk/actions/runs/5118722870/jobs/9203078760#step:6:2013

Expected behavior:

Tests shall not be executed at all.

Details

Additional information about Priority and Help Requested:

Are you willing to submit a pull request with a proposed change? No

Requested priority: (Showstopper, High, Medium, Low) Medium

@grom72 grom72 added Type: Bug A previously unknown bug in PMDK QA: CI .github/ and utils/ related to automated testing labels May 30, 2023
@grom72 grom72 added this to the 1.14 milestone May 30, 2023
@grom72
Copy link
Contributor Author

grom72 commented May 30, 2023

DISABLE_ prefix can be used as it is done for pmem2_badblock/TEST[0-5]

grom72 added a commit to grom72/pmdk that referenced this issue May 30, 2023
Disable tests until the issue pmem#5646 is fixed.
This commit temporary adresses also the issue pmem#5700.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72 added a commit to grom72/pmdk that referenced this issue May 30, 2023
Disable tests until the issue pmem#5646 is fixed.
This commit temporary adresses also the issue pmem#5700.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72 added a commit to grom72/pmdk that referenced this issue May 30, 2023
Disable tests until the issue pmem#5646 is fixed.

Fixes: pmem#5700.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
@grom72 grom72 modified the milestones: 1.14, 1.13 on GHA May 30, 2023
@janekmi janekmi changed the title obj_sync TEST[2,5-6] shall be fully disabled obj_sync TEST/[2,5-6] shall be fully disabled May 31, 2023
@janekmi janekmi changed the title obj_sync TEST/[2,5-6] shall be fully disabled obj_sync/TEST[2,5-6] shall be fully disabled May 31, 2023
grom72 added a commit to grom72/pmdk that referenced this issue May 31, 2023
Disable tests until the issue pmem#5646 is fixed.

Fixes: pmem#5700.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72 added a commit to grom72/pmdk that referenced this issue May 31, 2023
Disable tests until the issue pmem#5646 is fixed.

Fixes: pmem#5700.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
@janekmi janekmi closed this as completed May 31, 2023
hswong3i pushed a commit to alvistack/pmem-pmdk that referenced this issue Feb 28, 2024
Disable tests until the issue pmem#5646 is fixed.

Fixes: pmem#5700.

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
QA: CI .github/ and utils/ related to automated testing Type: Bug A previously unknown bug in PMDK
Projects
None yet
Development

No branches or pull requests

2 participants