If a new job is configured to be failed if there are some valgrind errors ( by setting the build Status Thresholds to 0 in the job configuration), the main page of the job will not display the valgrind results.
It will complain that "No valid valgrind data available This plugin will not report valgrind result until there is at least one success or unstable build.".

But job failure does not mean that there are no valgrind results, as the failure is a result of the valgrind errors.

If we go into the build history, and click on the valgrind results for one job execution, it will displayed showing the errors.

To reproduce: create a new job and parse a valgrind log containing some errors.