ReFrame fails on Dom reporting wrong reason

[vkarak]

Originally created by @lucamar.

Several daily tests failed today with a reason like the following:
Reason: caught framework exception: could not load module VASP

See the full log here

The reason is incorrect, since the module VASP is actually loaded and it can be used correctly. However ReFrame detects an error message printed on stdout for another missing modulefile:

$ module load daint-mc
$ module load VASP
atp(3):ERROR:105: Unable to locate a modulefile for 'atp/2.1.1'
CrayIntel/.17.08(3):ERROR:102: Tcl command execution failed: if { [ is-loaded atp ] } {
module swap atp atp/2.1.1
} else {
module load atp/2.1.1
}

More details in this CSCS ticket.

I think that ReFrame should check if the target modulefile is actually present in the module list, before skipping the test and reporting a failure.

[vkarak]

This issue has two parts:

1. The error message which is not accurate
2. Whether the modules backend should accept errors in the loading process or not and rely on whether the actual module is (or is reported as) loaded.

For the first one, I agree and we can fix that. For the second one, I am not sure if this is the correct behaviour, because it might hide other problems. @victorusu What is your opinion?

[vkarak]

@lucamar I replaced this issue with a more specific one: #467.