Re: DAOS_test failed
|
Wang, Di
Hello,
This basically means there are not enough servers to run rebuild tests, so they were being skipped.
The failure here is probably due to the incorrect usage of cmoka, which are used by some DAOS tests. Anyway it is not a real “failure”.
If you are interested in running rebuild tests. You need at least 6 DAOS servers.
Thanks WangDi
On 9/15/20, 2:07 PM, "daos@daos.groups.io on behalf of anton.brekhov@..." <daos@daos.groups.io on behalf of anton.brekhov@...> wrote:
I've set this env vars:
export POOL_NVME_SIZE=4 REBUILD12: rebuild send objects failed setup: creating pool, SCM size=2 GB, NVMe size=4 GB setup: created pool 8abfd4aa-0fb4-4122-aef7-f58b3fe6d81f setup: connecting to pool connected to pool, ntarget=4 setup: creating container ac978bdb-cb4c-4729-a0e4-cf3f3973696d setup: opening container No enough targets, skipping (4/0) teardown: destroyed pool 8abfd4aa-0fb4-4122-aef7-f58b3fe6d81f REBUILD13: rebuild empty pool offline setup: creating pool, SCM size=2 GB, NVMe size=4 GB setup: created pool 803c465f-6547-4c8f-a473-2dea0d457081 setup: connecting to pool connected to pool, ntarget=4 setup: creating container a7490729-0d9a-4935-900e-ede0f656871d setup: opening container No enough targets, skipping (4/0) teardown: destroyed pool 803c465f-6547-4c8f-a473-2dea0d457081 REBUILD14: rebuild no space failure setup: creating pool, SCM size=2 GB, NVMe size=4 GB setup: created pool cf718311-93cb-4b9f-a159-419585af99e8 setup: connecting to pool connected to pool, ntarget=4 setup: creating container f5a357b4-3af8-4670-9032-f5e9fc2944af setup: opening container No enough targets, skipping (4/0) -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpirun detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was:
Process name: [[25434,1],0] Exit code: 255
--------------------------------------------------------------------------
|
|
|