The wrong reference might require a less tighter error bar, the slow test could be just accidental. (19.81 s vs threshold of 19.18s)

Apparently, the problem was solved, if there is still anything to add, feel free to reopen the issue.

Here is cp2k running on my workstation. The screen prints one hint.
I don't know what this means. just update for your information.
Maybe “generic” would be replaced by “native” for cpu flags
Some Hints.txt

Apparently, the problem was solved, if there is still anything to add, feel free to reopen the issue.

how to reopen this issue?

Apparently, the problem was solved, if there is still anything to add, feel free to reopen the issue.

how to reopen this issue?

Usually, there is a button on the bottom of the page.

We have a FAQ page regarding your issue.

Apparently, the problem was solved, if there is still anything to add, feel free to reopen the issue.

how to reopen this issue?

Usually, there is a button on the bottom of the page.

We have a FAQ page regarding your issue.

Sorry, on my visiting, there is no this choice on the page.

What is your question regarding issues with regtests?

What is your question regarding issues with regtests?

It reports errors about accuration on amd machines.
as to the hints, maybe it is from gcc and gfortran compiled with 'generic' for general normal usage.

Without any outputs, I can only guess. If the accuracy notes stems from a run on the regtest suite and the error is only a bit higher than the threshold (something like 2.1 instead of 1.0), you may ignore it: Hardware differs in execution of commands, rounding modes, etc. such that results differ between different hardware configuration.
If you do not mean this hint, I will need the full output.