nvmesensor: increase timeout for namespace management/attach/sanitize

When testing those commands on multiple 8T SSD, we found the default
5 seconds timeout are not sufficient.

Thus we set their timeouts to 20 seconds as a workaround.
Will further investigate the long execution time device issue in b/300524907.

Tested:
After the fix, below commands won't timeout:
nvme_mi_admin_sanitize_nvm Elapsed(sec):5.15316
nvme_mi_admin_ns_attach Elapsed(sec):5.37624
nvme_mi_admin_ns_mgmt_delete Elapsed(sec):6.22645
nvme_mi_admin_ns_mgmt_delete Elapsed(sec):9.65004

Change-Id: Ic9a02a73d8f0e019a51d93914884df6b3ccc5b64
Signed-off-by: Jinliang Wang <jinliangw@google.com>
(cherry picked from commit 3da05fa6d3d704fa7c09a9b0c278967877a27981)
3 files changed
tree: 338399a7f3387f913050df9c899b4b007b98af60
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-devtools/
  7. recipes-extended/
  8. recipes-google/
  9. recipes-kernel/
  10. recipes-phosphor/
  11. LICENSE
  12. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.