Conversation
|
Ticket title is 'Generic ticket for minor code cleanup and improvement' |
github-actions
bot
added
the
priority
mchaarawi
force-pushed
the
mschaara/fi_allow_err
branch
3 times, most recently
from
15e151e to
8b2915c
Compare
|
Test stage Functional on EL 9 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17959/3/execution/node/747/log |
mchaarawi
force-pushed
the
mschaara/fi_allow_err
branch
2 times, most recently
from
30da5ea to
c242234
Compare
Skip-func-hw-test: true Skip-unit-test: true Skip-unit-test-memcheck: true Signed-off-by: Mohamad Chaarawi <mohamad.chaarawi@hpe.com>
mchaarawi
force-pushed
the
mschaara/fi_allow_err
branch
from
c242234 to
e436ce2
Compare
| if 'Sluggish EC boundary report from rank' in log_msg: | ||
| return False | ||
|
|
||
| if 'The progress callback was not called for too long' in log_msg: |
There was a problem hiding this comment.
Would it be better to increase the default value of the swim_prot_period_len parameter for NLT/FI tests using the SWIM_PROTOCOL_PERIOD_LEN environment variable?
| if 'Sluggish EC boundary report from rank' in log_msg: | ||
| return False |
There was a problem hiding this comment.
Wouldn't it be better to implement a solution similar to SWIM (see the next comment), which allows us to configure the timeout (600) introduced by the #17309 PR using an environment variable?
daos/src/container/srv_container.c
Line 2206 in b0f8277
if (pool->sp_reclaim != DAOS_RECLAIM_DISABLED &&
cur_ts > eph_ldr->cte_server_ephs[i].re_ec_agg_eph_update_ts + 600)
3 participants
Skip-func-hw-test: true
Skip-unit-test: true
Skip-unit-test-memcheck: true
Steps for the author:
After all prior steps are complete: