Oksana Sałyk

obj: unify description with implementation pmemobj_log* fun

1

This change is [](https://reviewable.io/reviews/pmem/pmdk/6067)

doc: add pmem_log_* documentations

1

This change is [](https://reviewable.io/reviews/pmem/pmdk/6061)

Prepare platform with bad block injection support.

1

1) Prepare platform with bad block injection support 2) Enable obj_badblock and pmem2_badblock tests

tests: skip tests because DevDAX is too big & similar cases

2

# ISSUE: pmempool tests are skipped because DevDAX is too big ## Actual behavior: 

Resizing arrays (OS-dependent) after dropping Windows support

1

# FEAT: Resizing arrays (OS-dependent) after dropping Windows support ## Description 

# FEAT: Simplify code after dropping Windows handling ## Description https://github.com/pmem/pmdk/pull/5620

Using the [configure-pmem.yml](https://github.com/pmem/pmdk/blob/master/utils/ansible/configure-pmem.yml) script to re-initialize PMem, we may encounter two errors: 1) The list of DAX devices will be different 2) Access to DAX devices will not be correct

Differences between documentation and header files

1

Review the documentation and compare the function descriptions in the header files. Special attention should be paid to functions marked EXPERIMENTAL.

Missing configuration to run tests

1

USC permission: libpmempool_feature: 1,2 pmempool_check: 28,29,30 pmempool_feature: 15 unsafe shutdown count: pmem2_usc: 0 bad block: obj_badblock: 0 pmempool_check: 31,32 pmempool_create: 10,11,12 pmempool_feature: 12 pmempool_sync: 27,28,30,31,38,39,40,41 util_badblock: 2,3,4,5,6,7,8,9

When building with coverage, the keep_going option is enabled: https://github.com/pmem/pmdk/blob/master/utils/docker/run-coverage.sh#L26