From: "Girar awaiter (imz)" <girar-builder@altlinux.org>
To: Ivan Zakharyaschev <imz@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org, girar-builder-p9@altlinux.org
Subject: [#386830] [test-only] p9 FAILED (try 2) truth.git=0.28-alt2_0jpp8 srpm=junit-4.13-alt1_2jpp11.src.rpm
Date: Wed, 11 Jun 2025 13:28:17 +0000
Message-ID: <girar.task.386830.2.1@gyle.mskdc.altlinux.org> (raw)
In-Reply-To: <girar.task.386830.1.1@gyle.mskdc.altlinux.org>
https://git.altlinux.org/tasks/386830/logs/events.2.1.log
https://packages.altlinux.org/tasks/386830
subtask name aarch64 armh i586 x86_64
#200 junit failed failed failed failed
2025-Jun-11 13:26:05 :: test-only task #386830 for p9 resumed by imz:
2025-Jun-11 13:26:05 :: message: backport_protobuf_tests
#100 build 0.28-alt2_0jpp8 from /gears/t/truth.git fetched at 2025-Jun-10 11:08:38 from p10
#200 build junit-4.13-alt1_2jpp11.src.rpm from p10
2025-Jun-11 13:26:06 :: created build repo
2025-Jun-11 13:26:08 :: [x86_64] #100 truth.git 0.28-alt2_0jpp8: build start
2025-Jun-11 13:26:08 :: [armh] #100 truth.git 0.28-alt2_0jpp8: build start
2025-Jun-11 13:26:08 :: [aarch64] #100 truth.git 0.28-alt2_0jpp8: build start
2025-Jun-11 13:26:08 :: [i586] #100 truth.git 0.28-alt2_0jpp8: build start
2025-Jun-11 13:26:21 :: [x86_64] #100 truth.git 0.28-alt2_0jpp8: build OK (cached)
2025-Jun-11 13:26:21 :: [i586] #100 truth.git 0.28-alt2_0jpp8: build OK (cached)
2025-Jun-11 13:26:22 :: [i586] #200 junit-4.13-alt1_2jpp11.src.rpm: build start
2025-Jun-11 13:26:22 :: [x86_64] #200 junit-4.13-alt1_2jpp11.src.rpm: build start
2025-Jun-11 13:26:34 :: [aarch64] #100 truth.git 0.28-alt2_0jpp8: build OK (cached)
2025-Jun-11 13:26:34 :: [aarch64] #200 junit-4.13-alt1_2jpp11.src.rpm: build start
2025-Jun-11 13:26:38 :: [armh] #100 truth.git 0.28-alt2_0jpp8: build OK (cached)
2025-Jun-11 13:26:39 :: [armh] #200 junit-4.13-alt1_2jpp11.src.rpm: build start
[x86_64] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-versions) on project junit: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[x86_64] [ERROR]
[x86_64] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[x86_64] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[x86_64] [ERROR]
[x86_64] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[x86_64] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[x86_64] error: Bad exit status from /usr/src/tmp/rpm-tmp.91311 (%build)
[x86_64] RPM build errors:
[x86_64] ignored self-provides: junit = 0:4.13
2025-Jun-11 13:26:59 :: [x86_64] junit-4.13-alt1_2jpp11.src.rpm: remote: build failed
2025-Jun-11 13:26:59 :: [x86_64] #200 junit-4.13-alt1_2jpp11.src.rpm: build FAILED
2025-Jun-11 13:26:59 :: [x86_64] requesting cancellation of task processing
[i586] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-versions) on project junit: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[i586] [ERROR]
[i586] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[i586] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[i586] [ERROR]
[i586] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[i586] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[i586] error: Bad exit status from /usr/src/tmp/rpm-tmp.82232 (%build)
[i586] RPM build errors:
[i586] ignored self-provides: junit = 0:4.13
2025-Jun-11 13:27:01 :: [i586] junit-4.13-alt1_2jpp11.src.rpm: remote: build failed
2025-Jun-11 13:27:01 :: [i586] #200 junit-4.13-alt1_2jpp11.src.rpm: build FAILED
[aarch64] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-versions) on project junit: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[aarch64] [ERROR]
[aarch64] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[aarch64] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[aarch64] [ERROR]
[aarch64] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[aarch64] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[aarch64] error: Bad exit status from /usr/src/tmp/rpm-tmp.18586 (%build)
[aarch64] RPM build errors:
[aarch64] ignored self-provides: junit = 0:4.13
2025-Jun-11 13:27:47 :: [aarch64] junit-4.13-alt1_2jpp11.src.rpm: remote: build failed
2025-Jun-11 13:27:47 :: [aarch64] #200 junit-4.13-alt1_2jpp11.src.rpm: build FAILED
[armh] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-versions) on project junit: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[armh] [ERROR]
[armh] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[armh] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[armh] [ERROR]
[armh] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[armh] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[armh] error: Bad exit status from /usr/src/tmp/rpm-tmp.92223 (%build)
[armh] RPM build errors:
[armh] ignored self-provides: junit = 0:4.13
2025-Jun-11 13:28:17 :: [armh] junit-4.13-alt1_2jpp11.src.rpm: remote: build failed
2025-Jun-11 13:28:17 :: [armh] #200 junit-4.13-alt1_2jpp11.src.rpm: build FAILED
2025-Jun-11 13:26:59 :: [x86_64] build FAILED
2025-Jun-11 13:27:01 :: [i586] build FAILED
2025-Jun-11 13:27:47 :: [aarch64] build FAILED
2025-Jun-11 13:28:17 :: [armh] build FAILED
2025-Jun-11 13:28:17 :: task #386830 for p9 FAILED
next prev parent reply other threads:[~2025-06-11 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 11:15 [#386830] p9 TESTED truth.git=0.28-alt2_0jpp8 Girar awaiter (imz)
2025-06-11 13:28 ` Girar awaiter (imz) [this message]
2025-06-11 13:59 ` [#386830] [test-only] p9 FAILED (try 3) srpm=maven-enforcer-3.0.0_M2-alt1_3jpp8.src.rpm truth.git=0.28-alt2_0jpp8 Girar awaiter (imz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=girar.task.386830.2.1@gyle.mskdc.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=girar-builder-p9@altlinux.org \
--cc=imz@altlinux.org \
--cc=sisyphus-incominger@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Girar Builder robot reports
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \
sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com
public-inbox-index sisyphus-incominger
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git