From: Girar Builder awaiter robot <girar-builder@altlinux.org>
To: Igor Vlasenko <viy@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org
Subject: [#234519] FAILED srpm=byte-buddy-1.9.5-alt1_5jpp8.src.rpm
Date: Sun, 14 Jul 2019 17:52:19 +0000
Message-ID: <20190714175219.GA31962@gyle.altlinux.org> (raw)
http://git.altlinux.org/tasks/234519/logs/events.1.1.log
2019-Jul-14 17:46:49 :: task #234519 for sisyphus started by viy:
#100 build byte-buddy-1.9.5-alt1_5jpp8.src.rpm
2019-Jul-14 17:46:50 :: [i586] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build start
2019-Jul-14 17:46:50 :: [ppc64le] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build start
2019-Jul-14 17:46:50 :: [x86_64] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build start
2019-Jul-14 17:46:50 :: [aarch64] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build start
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :byte-buddy-dep
2019-Jul-14 17:48:37 :: [x86_64] byte-buddy-1.9.5-alt1_5jpp8.src.rpm: remote: build failed
2019-Jul-14 17:48:37 :: [x86_64] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build FAILED
2019-Jul-14 17:48:37 :: [x86_64] requesting cancellation of task processing
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :byte-buddy-dep
2019-Jul-14 17:48:47 :: [i586] byte-buddy-1.9.5-alt1_5jpp8.src.rpm: remote: build failed
2019-Jul-14 17:48:47 :: [i586] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build FAILED
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :byte-buddy-dep
2019-Jul-14 17:49:15 :: [ppc64le] byte-buddy-1.9.5-alt1_5jpp8.src.rpm: remote: build failed
2019-Jul-14 17:49:15 :: [ppc64le] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build FAILED
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :byte-buddy-dep
2019-Jul-14 17:52:19 :: [aarch64] byte-buddy-1.9.5-alt1_5jpp8.src.rpm: remote: build failed
2019-Jul-14 17:52:19 :: [aarch64] #100 byte-buddy-1.9.5-alt1_5jpp8.src.rpm: build FAILED
2019-Jul-14 17:48:37 :: [x86_64] build FAILED
2019-Jul-14 17:48:47 :: [i586] build FAILED
2019-Jul-14 17:49:15 :: [ppc64le] build FAILED
2019-Jul-14 17:52:19 :: [aarch64] build FAILED
2019-Jul-14 17:52:19 :: task #234519 for sisyphus FAILED
reply other threads:[~2019-07-14 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190714175219.GA31962@gyle.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=sisyphus-incominger@lists.altlinux.org \
--cc=viy@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