From: "Girar awaiter (cas)" <girar-builder@altlinux.org>
To: Andrey Cherepanov <cas@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org,
girar-builder-sisyphus@altlinux.org
Subject: [#407653] FAILED jetty.git=9.4.58-alt1
Date: Mon, 9 Feb 2026 04:49:56 +0000
Message-ID: <girar.task.407653.1.1@gyle.mskdc.altlinux.org> (raw)
https://git.altlinux.org/tasks/407653/logs/events.1.1.log
https://packages.altlinux.org/tasks/407653
subtask name aarch64 i586 x86_64
#100 jetty failed failed failed
2026-Feb-09 04:48:55 :: task #407653 for sisyphus started by cas:
#100 build 9.4.58-alt1 from /people/cas/packages/jetty.git fetched at 2026-Feb-09 04:48:53
2026-Feb-09 04:48:57 :: [x86_64] #100 jetty.git 9.4.58-alt1: build start
2026-Feb-09 04:48:57 :: [i586] #100 jetty.git 9.4.58-alt1: build start
2026-Feb-09 04:48:57 :: [aarch64] #100 jetty.git 9.4.58-alt1: build start
[x86_64] Unparseable macro: % Java HTTP Server and Servlet Container. This means that you
[x86_64] do not need to configure and run a separate web server (like Apache) in order
[x86_64] to use Java, servlets and JSPs to generate dynamic content. Jetty is a fully
[x86_64] featured web server for static and dynamic content. Unlike separate
[x86_64] server/container solutions, this means that your web server and web
[x86_64] application run in the same process, without interconnection overheads
[x86_64] and complications. Furthermore, as a pure java component, Jetty can be simply
[x86_64] included in your application for demonstration, distribution or deployment.
[x86_64] Jetty is available on all Java supported platforms.
[x86_64] This package contains
2026-Feb-09 04:49:25 :: [x86_64] jetty.git 9.4.58-alt1: remote: build failed
2026-Feb-09 04:49:25 :: [x86_64] #100 jetty.git 9.4.58-alt1: build FAILED
2026-Feb-09 04:49:25 :: [x86_64] requesting cancellation of task processing
[i586] Unparseable macro: % Java HTTP Server and Servlet Container. This means that you
[i586] do not need to configure and run a separate web server (like Apache) in order
[i586] to use Java, servlets and JSPs to generate dynamic content. Jetty is a fully
[i586] featured web server for static and dynamic content. Unlike separate
[i586] server/container solutions, this means that your web server and web
[i586] application run in the same process, without interconnection overheads
[i586] and complications. Furthermore, as a pure java component, Jetty can be simply
[i586] included in your application for demonstration, distribution or deployment.
[i586] Jetty is available on all Java supported platforms.
[i586] This package contains
2026-Feb-09 04:49:26 :: [i586] jetty.git 9.4.58-alt1: remote: build failed
2026-Feb-09 04:49:26 :: [i586] #100 jetty.git 9.4.58-alt1: build FAILED
[aarch64] Unparseable macro: % Java HTTP Server and Servlet Container. This means that you
[aarch64] do not need to configure and run a separate web server (like Apache) in order
[aarch64] to use Java, servlets and JSPs to generate dynamic content. Jetty is a fully
[aarch64] featured web server for static and dynamic content. Unlike separate
[aarch64] server/container solutions, this means that your web server and web
[aarch64] application run in the same process, without interconnection overheads
[aarch64] and complications. Furthermore, as a pure java component, Jetty can be simply
[aarch64] included in your application for demonstration, distribution or deployment.
[aarch64] Jetty is available on all Java supported platforms.
[aarch64] This package contains
2026-Feb-09 04:49:55 :: [aarch64] jetty.git 9.4.58-alt1: remote: build failed
2026-Feb-09 04:49:55 :: [aarch64] #100 jetty.git 9.4.58-alt1: build FAILED
2026-Feb-09 04:49:25 :: [x86_64] build FAILED
2026-Feb-09 04:49:27 :: [i586] build FAILED
2026-Feb-09 04:49:56 :: [aarch64] build FAILED
2026-Feb-09 04:49:56 :: task #407653 for sisyphus FAILED
reply other threads:[~2026-02-09 4:49 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=girar.task.407653.1.1@gyle.mskdc.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=cas@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=girar-builder-sisyphus@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