coy-humphrey/nvme-hpe

Issues

• Name CSV for fio as fio-remote.csv and fio-local.csv

  #24 opened 8 years ago
  0

• Record CPU usage during tests

  #23 opened 8 years ago
  0

• Move fio static flags to the end and then remove their output headers so they aren't displayed

  #22 opened 8 years ago
  0

• Debug mode that runs single command, not all

  #21 opened 8 years ago
  0

• Install pdb and pylint on both servers

  #20 opened 8 years ago
  0

• Clone repo on devel accounts

  #19 opened 8 years ago
  0

• Restrict bench_dev to specific sudo commands

  #18 opened 8 years ago
  0

• Make sure teardown happens after setup for environments even if a command failed in the middle.

  #17 opened 8 years ago
  0

• Modify ib_send_bw test to have -R flag

  #16 opened 8 years ago
  0

• Create FIO test

  #15 opened 8 years ago
  0

• Create benchmarking devel account to run sudo (without password) python subprocesses

  #14 opened 8 years ago
  0

• Automate overnight runs between client and server (use chron or something similar)

  #13 opened 8 years ago
  0

• Generate ib_send_lat and other ib_*_* scripts

  #12 opened 8 years ago
  0

• Polish up ib_send_bw.py to be used as a template for future scripts

  #11 opened 8 years ago
  1

• Have run_all script generate new directory with time stamp name inside of CSV folder for each run

  #10 opened 8 years ago
  1

• Use remote commands to run subprocesses from client to server (or vice versa) to avoid race conditions and make code shorter

  #9 opened 8 years ago
  1

• Use remote commands to run subprocesses from client to server (or vice versa) to avoid race conditions and make code shorter

  #8 opened 8 years ago
  0

• Create function that outputs pairs of flag and value for each command to be used for easy CSV output

  #7 opened 8 years ago
  0

• If a command encounters an error, note the error in the log, but then make sure you continue

  #6 opened 8 years ago
  2

• Environment (RAIO, Local Ramdisk etc) setup and teardown is supported in the framework

  #5 opened 8 years ago
  0

• CSV Parser Framework is setup

  #4 opened 8 years ago
  0

• Look into sorted dictionary, so that the output is organized better

  #3 opened 8 years ago
  0

• Figure out how to capture stderr in Python, and what to do with the errors we capture

  #2 opened 8 years ago
  1

• Make race condition timer a variable in the framework that can be specified by the test

  #1 opened 8 years ago
  0