[riscv-reports] [#84732] sisyphus_riscv64 FAILED srpm=assertj-core-3.19.0-alt1_3jpp11.src.rpm ...

[Girar sisyphus_riscv64 awaiter iv]

http://web.build.srt.basealt.ru/tasks/84732/logs/events.1.1.log

subtask  name          riscv64
   #100  assertj-core   failed

2025-May-29 15:14:11 :: task #84732 for sisyphus_riscv64 started by iv:
2025-May-29 15:14:11 :: message: sync
#100 build assertj-core-3.19.0-alt1_3jpp11.src.rpm
#200 build junit5-5.8.2-alt1.src.rpm
#300 build mockito-5.17.0-alt1.src.rpm
#400 build byte-buddy-1.12.0-alt1_3jpp11.src.rpm
#500 build ant-1.10.12-alt1_8jpp11.src.rpm
2025-May-29 15:14:11 :: created build repo
2025-May-29 15:14:14 :: [riscv64] #100 assertj-core-3.19.0-alt1_3jpp11.src.rpm: build start
[riscv64] [INFO] Total time:  3.172 s
[riscv64] [INFO] Finished at: 2025-05-29T15:17:58Z
[riscv64] [INFO] ------------------------------------------------------------------------
[riscv64] [ERROR] Failed to execute goal on project assertj-core: Could not resolve dependencies for project org.assertj:assertj-core:jar:3.19.0: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.hamcrest:hamcrest:jar:2.2 has not been downloaded from it before. -> [Help 1]
[riscv64] [ERROR] 
[riscv64] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[riscv64] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[riscv64] [ERROR] 
[riscv64] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[riscv64] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
2025-May-29 15:17:59 :: [riscv64] assertj-core-3.19.0-alt1_3jpp11.src.rpm: remote: build failed
2025-May-29 15:17:59 :: [riscv64] #100 assertj-core-3.19.0-alt1_3jpp11.src.rpm: build FAILED
2025-May-29 15:17:59 :: [riscv64] requesting cancellation of task processing
2025-May-29 15:17:59 :: [riscv64] build FAILED
2025-May-29 15:17:59 :: task #84732 for sisyphus_riscv64 FAILED