Can't run mvn test -Dtags="@5254"

Can’t run mvn test -Dtags=“@5254
It gives these errors, please tell me how to fix it. I want to run a test.
Here are the errors:

Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building in workspace C:\ProgramData\Jenkins\.jenkins\workspace\HPSM
The recommended git tool is: git.exe
using credential 249682c5-34af-4f9e-8938-777702bd75bc
 > git.exe rev-parse --resolve-git-dir C:\ProgramData\Jenkins\.jenkins\workspace\HPSM\.git # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url # timeout=10
Fetching upstream changes from
 > git.exe --version # timeout=10
 > git --version # 'git version'
using GIT_ASKPASS to set credentials 
 > git.exe fetch --tags --force --progress -- +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git.exe rev-parse "refs/remotes/origin/test_dev^{commit}" # timeout=10
Checking out Revision 4e8aed1d7171e4c8e2a461177d3be6f56b9216ca (refs/remotes/origin/test_dev)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 4e8aed1d7171e4c8e2a461177d3be6f56b9216ca # timeout=10
Commit message: "Почта"
 > git.exe rev-list --no-walk 4e8aed1d7171e4c8e2a461177d3be6f56b9216ca # timeout=10
[HPSM] $ cmd.exe /C "mvn mvn test -Dtags=@5254 && exit %%ERRORLEVEL%%"
"mvn" ­Ґ пў«пҐвбп ў­гв७­Ґ© Ё«Ё ў­Ґи­Ґ©
Є®¬ ­¤®©, ЁбЇ®«­пҐ¬®© Їа®Ја ¬¬®© Ё«Ё Ї ЄҐв­л¬ д ©«®¬.
Build step 'Вызвать цели Maven верхнего уровня  ' marked build as failure
[HPSM] $ C:\ProgramData\Jenkins\.jenkins\tools\\Allure\bin\allure.bat generate -c -o C:\ProgramData\Jenkins\.jenkins\workspace\HPSM\allure-report
allure-results does not exist
Report successfully generated to C:\ProgramData\Jenkins\.jenkins\workspace\HPSM\allure-report
Allure report was successfully generated.
Creating artifact for the build.
Artifact was added to the build.
Finished: FAILURE

Not being able to read Russian, I can only guess what that message says. However, I do notice that you are calling mvn mvn test. Last I checked, Maven does not have a lifecycle stage named mvn. Verify your bat step to ensure that you are not doubling up the mvn call.

Thanks for the answer. The problem turned out to be that I did not select the Maven version.