ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] racket cpu hog (was: CPU time limit exceeded)
Date: Sun, 23 Oct 2022 20:25:05 +0300
Message-ID: <20221023172505.GA8234@altlinux.org> (raw)
In-Reply-To: <Y1ULxDK4bVPu6LfK@dell-vostro-5301>

On Sun, Oct 23, 2022 at 12:39:16PM +0300, Anton Zhukharev wrote:
> Добрый день!
> 
> Недавно столкнулся с проблемой следующего вида:
> 
> [ppc64le] /usr/sbin/chroot.fakechroot: line 147: 2435617 CPU time limit exceeded env -u FAKECHROOT_BASE_ORIG FAKECHROOT_CMD_ORIG= LD_LIBRARY_PATH="$fakechroot_chroot_paths" FAKECHROOT_BASE="$fakechroot_chroot_base" "$fakechroot_chroot_chroot" "${@:1:$(($fakechroot_chroot_n - 1))}" "$fakechroot_chroot_final_newroot" "${@:$(($fakechroot_chroot_n + 1))}"
> 2022-Oct-22 21:18:00 :: [ppc64le] racket-main-distribution.git 8.6-alt1: remote: build failed
> 2022-Oct-22 21:18:00 :: [ppc64le] #100 racket-main-distribution.git 8.6-alt1: build FAILED
> 
> в задании 308872.
> 
> Насколько я понимаю, эта ошибка связана с разделением времени работы
> процессора между пользовательскими процессами (воспроизвелась только на
> архитектурах i586, armh и ppc64le - на x86_64 и aarch64 полёт нормальный).
> 
> Есть способ обхода такого ограничения?

Сделать так, чтобы racket перестал быть таким неуёмно прожорливым,
что особенно проявляется на более медленных архитектурах.


-- 
ldv


  parent reply	other threads:[~2022-10-23 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23  9:39 [devel] CPU time limit exceeded Anton Zhukharev
2022-10-23 12:33 ` Leonid Krivoshein
2022-10-23 16:32   ` Anton Zhukharev
2022-10-23 18:51     ` Andrey Savchenko
2022-10-23 18:56       ` Anton Zhukharev
2022-10-23 17:25 ` Dmitry V. Levin [this message]
2022-10-23 18:52   ` [devel] racket cpu hog (was: CPU time limit exceeded) Anton Zhukharev
2022-10-23 19:05     ` Vitaly Chikunov
2022-10-23 19:37       ` Anton Farygin
2022-10-24  7:47         ` Anton Zhukharev
2022-10-24  7:54           ` Anton Farygin
2022-10-24 10:33           ` Andrey Savchenko
2022-10-24 11:00             ` Vitaly Chikunov
2022-10-24 12:09               ` Dmitry V. Levin
2022-10-24 12:19                 ` Sergey V Turchin
2022-10-24  7:54     ` Anton Zhukharev
2022-10-26 19:47       ` Anton Zhukharev
2022-10-26 20:42         ` Ivan A. Melnikov
2022-10-27  6:47         ` Anton Farygin

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=20221023172505.GA8234@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@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 Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/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 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git