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/TEST0 timeout under pmemcheck #5643

Open
grom72 opened this issue May 15, 2023 · 1 comment
Open

obj_sync/TEST0 timeout under pmemcheck #5643

grom72 opened this issue May 15, 2023 · 1 comment
Assignees
Labels
CI: Disabled Temporarily disabled from testing Priority: 3 medium 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 15, 2023

ISSUE: obj_sync/TEST0 timeout under pmemcheck

Environment Information

  • PMDK package version(s): 37292d4
  • OS(es) version(s): Rocky Linux 9.1 (Blue Onyx)
  • ndctl version(s): 71.1
  • kernel version(s): 5.14.0-162.6.1.el9_1.x86_64

Please provide a reproduction of the bug:

obj_sync/TEST0 timeout under valgrind (self-hosted, rhel, RUNTESTS -p force-enable)

https://github.com/pmem/pmdk/actions/runs/4961833388/jobs/8894945681#step:6:4612

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

Actual behavior:

obj_sync/TEST0: SETUP (check/none/debug/pmemcheck)
RUNTESTS: stopping: obj_sync/TEST0 timed out, TEST=check FS=none BUILD=debug

Expected behavior:

Details

Additional information about Priority and Help Requested:

Are you willing to submit a pull request with a proposed change? (Yes, No)

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

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

grom72 commented May 16, 2023

Very short test.

[tgromadz@wp162 test]$ ./RUNTESTS -t check -p force-enable -u 0 obj_sync
obj_sync/TEST0: SETUP (check/none/debug/pmemcheck)
obj_sync/TEST0: START: obj_sync
 ./obj_sync m 50 5
{obj_sync.c:65 mutex_write_worker} obj_sync/TEST0: pmemobj_mutex_lock
obj_sync/TEST0: DONE
obj_sync/TEST0: PASS                    [00.515 s]
obj_sync/TEST0: SETUP (check/none/nondebug/pmemcheck)
obj_sync/TEST0: START: obj_sync
 ./obj_sync m 50 5
{obj_sync.c:85 mutex_check_worker} obj_sync/TEST0: pmemobj_mutex_lock
obj_sync/TEST0: DONE
obj_sync/TEST0: PASS                    [00.506 s]

Timeout means something wrong has happened.

osalyk added a commit to osalyk/pmdk that referenced this issue May 17, 2023
@osalyk osalyk added the CI: Disabled Temporarily disabled from testing label May 19, 2023
@osalyk osalyk self-assigned this May 19, 2023
@osalyk osalyk modified the milestones: 1.13 on GHA, 1.14 May 22, 2023
@janekmi janekmi modified the milestones: 2.0.0, 2.0.1 Jul 21, 2023
@janekmi janekmi modified the milestones: 2.0.1, 2.0.2 Nov 23, 2023
@janekmi janekmi modified the milestones: 2.1.0, 2.x Feb 8, 2024
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 Priority: 3 medium 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

3 participants