Sable/wu-wei-benchmarking-toolkit

Issues

• Error in the function help

  #40 opened 7 years ago by wukefe
  2

• Not installing JS dependencies

  #38 opened 7 years ago by dherre3
  0

• Naming issue when artifacts are correct in wu run

  #39 opened 7 years ago by dherre3
  0

• Find the working repository by recursively traversing the parent(s) of the current working directory

  #3 opened 9 years ago by elavoie
  1

• Add option in compiler and environment descriptions to support multiple short-names

  #37 opened 8 years ago by elavoie
  0

• Make Wu-Wei Compatible with Older versions of Node

  #35 opened 8 years ago by wukefe
  3

• Should provide better error reporting when there is no 'benchmark.json' file in a benchmark.

  #34 opened 8 years ago by elavoie
  0

• Test whether the executable-path or executable-name is available in an environment after the installation

  #32 opened 8 years ago by elavoie
  1

• Automatic dependency for scripts when initializing a suite

  #1 opened 8 years ago by elavoie
  1

• spawnSync undefined on older versions of node

  #21 opened 8 years ago by akrolik
  1

• Add automatic installation of artifact with 'wu install'

  #30 opened 8 years ago by elavoie
  0

• Support the overwrite of input-size parameters from the benchmark.json file with parameters given in the experiment.json file

  #31 opened 8 years ago by elavoie
  0

• Automate install procedure for environments, including browser-run tool

  #2 opened 8 years ago by elavoie
  1

• Automatically determine the platform information and generate a 'platform.json' file when installing the tools

  #13 opened 8 years ago by elavoie
  9

• There should be a command/option to go from benchmark to build id

  #29 opened 9 years ago by gnuvince
  1

• No report is written if a benchmark run crashes before finishing

  #28 opened 9 years ago by gnuvince
  1

• Compiler none-matlab should copy rather than cat

  #27 opened 9 years ago by gnuvince
  2

• Avoid compiling a benchmark with a compiler that is incompatible with the target environment when doing 'wu run'

  #26 opened 9 years ago by elavoie
  0

• Error when running 'wu run lud c -v'

  #20 opened 9 years ago by elavoie
  0

• Validate that the short-name for implementation.json is the same as the directory name and consistent with other names in the suite

  #25 opened 9 years ago by elavoie
  0

• Make build and run configuration generation from short-names faster

  #24 opened 9 years ago by elavoie
  0

• [BUG] wu platform #Error in linux virtual machine getting hardware info

  #19 opened 9 years ago by dridon
  1

• Add schema validation before writing artefact description files

  #22 opened 9 years ago by gnuvince
  0

• Add a few words under `wu list`

  #18 opened 9 years ago by wukefe
  0

• Add check to enforce the presence of either 'executable-name' or 'executable-path' in a compiler command

  #17 opened 9 years ago by elavoie
  0

• Output more meaningful error messages when JSON description do not conform to the expected schemas.

  #15 opened 9 years ago by elavoie
  0

• Add support for multiple arguments in input-size

  #12 opened 9 years ago by elavoie
  1

• Make some compiler configuration options optional

  #6 opened 9 years ago by elavoie
  1

• Make the hash value of results in 'run.json' depend on the content of all files and executables required to obtain it.

  #10 opened 9 years ago by elavoie
  0

• Filter out the unneeded properties from 'build.json' and 'run.json'

  #9 opened 9 years ago by elavoie
  0

• Remove the 'dependency' property from all 'implementation.json' in Ostrich

  #11 opened 9 years ago by elavoie
  0

• implementation.json: Make the dependency listing optional, and automatically computed by default

  #5 opened 9 years ago by elavoie
  0

• Add a 'check' tool to validate configurations before building or running benchmarks

  #7 opened 9 years ago by elavoie
  0

• Factor out the configuration generation and filtering from the 'run' and 'build' tools

  #8 opened 9 years ago by elavoie
  0