Compiler version not captured into the database

[mikebentley15]

You can specify the location of the compiler in the flit-config.toml file, but that may not be good enough. For the sake of reproducibility, the versions of each compiler that is used is not recorded into the database. This may or may not be something that is easy to do, but it is necessary for the sake of reproducibility of results (which is what we're all about here).

[IanBriggs]

We could add a DB table - (key, compiler_name, compiler_info) where the key is used in the other tables to identify the compiler, compiler_name is the command used (g++, clang, etc) and compiler_info is the output of compiler_name --version.

This does add yet another table making it more confusing to users, but the key value could be made slightly transparent (e.g. gcc_540 with additional suffixes if two gcc executables have the same version, but different builds)

[mikebentley15]

Yeah, I think this is a good suggestion. I'd probably want to use the name of the compiler (as specified in flit-config.toml) as the key, and then the separate table would specify (run#, name, binary path, type, version). Yes, it does add to the total number of tables, but hopefully, it shouldn't make the tests table any less readable. Good suggestion Ian.