Re: poudriere blocked after pkg build failed

2020-02-29 Thread Axel Rau
> Am 28.02.2020 um 01:22 schrieb Tatsuki Makino : > > Your poudriere.conf is written as PARALLEL_JOBS=4. > Combining this with writing MAKE_JOBS_NUMBER:=4 in > /usr/local/etc/poudriere.d/*make.conf, load average reaches 16. > If you are concerned about that load average reaching 16, you need to

Re: poudriere blocked after pkg build failed

2020-02-27 Thread Tatsuki Makino
Your poudriere.conf is written as PARALLEL_JOBS=4. Combining this with writing MAKE_JOBS_NUMBER:=4 in /usr/local/etc/poudriere.d/*make.conf, load average reaches 16. If you are concerned about that load average reaching 16, you need to adjust PARALLEL_JOBS and MAKE_JOBS_NUMBER. If it only rise up t

Re: poudriere blocked after pkg build failed

2020-02-27 Thread Axel Rau
> Am 27.02.2020 um 00:09 schrieb Tatsuki Makino : > > .MAKE.JOBS=4 This was the only way to force a -j 4 to make. > > If you want to limit the number of parallel jobs to 4, write: > > MAKE_JOBS_NUMBER:=4 This has no effect here, if combined with ALLOW_MAKE_JOBS=yes in poudrier

Re: poudriere blocked after pkg build failed

2020-02-27 Thread Axel Rau
> Am 27.02.2020 um 00:09 schrieb Tatsuki Makino : > > > The cause of this trouble is the following part of make.conf. > > .MAKE.JOBS=4 YEP, that’s it. Surprisingly this worked for days (weeks?) until pkg received an update. (-; Thank you for your great work, Axel --- PGP-Key: CDE74120 ☀ com

Re: poudriere blocked after pkg build failed

2020-02-26 Thread Tatsuki Makino
I have finally made the poudriere the same as yours. The cause of this trouble is the following part of make.conf. .MAKE.JOBS=4 If you want to limit the number of parallel jobs to 4, write: MAKE_JOBS_NUMBER:=4 ___ freebsd-ports@freebsd.org mailing li

Re: poudriere blocked after pkg build failed

2020-02-26 Thread Axel Rau
> Am 26.02.2020 um 00:18 schrieb Tatsuki Makino : > > TMPFS_LIMIT=4 -> 6 > MAX_MEMORY=2 -> 4 > MAX_FILES=1024 -> 2048 > PARALLEL_JOBS=4 -> 2 > PREPARE_PARALLEL_JOBS=5 Trying it. The result looks so: ——— root@db3:~ # poudriere testport -vv -j 120amd64 ports-mgmt/pkg =>> Debug: Reading /usr/local

Re: poudriere blocked after pkg build failed

2020-02-25 Thread Tatsuki Makino
Your poudriere.conf has resource limits. Would you try removing the resource limit and reducing the number of parallels? e.g. TMPFS_LIMIT=4 -> 6 MAX_MEMORY=2 -> 4 MAX_FILES=1024 -> 2048 PARALLEL_JOBS=4 -> 2 PREPARE_PARALLEL_JOBS=5 ___ freebsd-ports@free

Re: poudriere blocked after pkg build failed

2020-02-25 Thread Axel Rau
> Am 25.02.2020 um 18:43 schrieb Axel Rau : > > > I attach my poudriere.conf and portshaker.conf (which worked for years). https://www.chaos1.de/downloads/pp.tar.gz Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius signature.asc Description: Message signed with OpenPGP

Re: poudriere blocked after pkg build failed

2020-02-25 Thread Axel Rau
> Am 25.02.2020 um 09:27 schrieb Axel Rau : > > > Question: How do I reset the poudriere environment to let it start over and > bootstrap a new pkg? > Is cleaning data enough (as ports tree is maintained by portshaker here)? I cleaned jails and ports and re-created them. (created an empty ${

Re: poudriere blocked after pkg build failed

2020-02-25 Thread Axel Rau
> Am 25.02.2020 um 09:27 schrieb Axel Rau : > > Question: How do I reset the poudriere environment to let it start over and > bootstrap a new pkg? > Is cleaning data enough (as ports tree is maintained by portshaker here)? Even after removing poudriere data tree and recreating poudriere jails an

Re: poudriere blocked after pkg build failed

2020-02-25 Thread Axel Rau
> Am 24.02.2020 um 23:48 schrieb Tatsuki Makino : > > Is there a mistake in any of /usr/local/etc/poudriere.d/*make.conf ? Nothing changed recently: ——— #?# WITH_SSP_PORTS (bool) If set, enables -fstack-protector for most ports. # CC=clang # Highly recommended over GCC, CXX

Re: poudriere blocked after pkg build failed

2020-02-24 Thread Tatsuki Makino
Is there a mistake in any of /usr/local/etc/poudriere.d/*make.conf ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: poudriere blocked after pkg build failed

2020-02-24 Thread Axel Rau
Thanks for your answer! > Am 24.02.2020 um 00:00 schrieb Tatsuki Makino : > > For example, re-extracting ports tree. > >> portsnap -d "`cat /usr/local/etc/poudriere.d/ports/default/mnt`/.snap" > -p "`cat /usr/local/etc/poudriere.d/ports/default/mnt`“ extract I’m using portshaker, so I did: por

Re: poudriere blocked after pkg build failed

2020-02-23 Thread Tatsuki Makino
For example, re-extracting ports tree. > portsnap -d "`cat /usr/local/etc/poudriere.d/ports/default/mnt`/.snap" -p "`cat /usr/local/etc/poudriere.d/ports/default/mnt`" extract For example, to revert ports tree. svnlite revert -R "`cat /usr/local/etc/poudriere.d/ports/default/mnt`" _

Re: poudriere blocked after pkg build failed

2020-02-23 Thread Axel Rau
> Am 22.02.2020 um 10:58 schrieb Axel Rau : > > How to fix this situation? After cleaning distfile cache and putting the previous version pkg-1.13.1.txz into ${POUDRIERE_DATA}/packages/120amd64-default/.real_1582359892/All I’m still getting: . . . =>> Status ports-mgmt/pkg |