You are not logged in.
virtual memory exhausted: Operation not permitted
I think, some parameters have to be raised on the build slaves..
Offline
afaik, the memory limit is 12GB
does it build on your box?
Offline
Oups. That should really be enough. I have 8 GB. I'm currently trying to build it..
Offline
Mmh. Weird. Builds without any problems on my machine. Maybe the number of parallel build jobs is too high. I'm just building with -j1.
Offline
ok, I'll retry on a different box: Because I don't know which `-j` is the right one, I'll just increase to 64GB ram.
Offline
hmm, this isn't enough - and putting "MAKEFLAGS=-j1" into /etc/makepkg.conf doesn't limit the number of parallel builds (although -j1 enters the makepkg.conf in the build container)
Offline
kmk is a modified GNU make, maybe it works a little bit differently.
I have to say: the machine I'm building on has only one core, this might have helped. :-)
Offline
Ah, stupid me. 32-bit processes can at most use 4 GB virtual address space. So raising memory doesn't help at all (above 4 GB).
I have to dig deeper why it works on my machine.
Offline
Do you have a real /tmp or a tmpfs in RAM?
Offline
I have a tmpfs in ram, but the package is being built in a tmpdir on the disk, because I expected large packages (e.g. thunderbird, firefox) to exceed the size of the ramdisk.
Offline
the strange part is, that the build uses as many processors as it finds and ignores any '-j' setting in MAKEFLAGS.
Offline
Can you try to build the package via
bin/build-packages -l virtualbox.63be256f86b1dadf6eaffdaf9ba83605aee377c4.b10417a41e2f1ce9e49e675f9e450b2eb73f551c.communityand see if it still works?
If so, I would give you build-slave access to the build master and you could simply upload that package to the database.
Offline
Yep. I could build the packages and install them. Not tested yet.
Offline
The build script deleted my tmp.* directories after building.. I'll redo the packages.. :-)
Last edited by andreas_baumann (2017-10-23 17:24:54)
Offline
Tested with host DKMS modules, installed an Archlinux 32-bit on an Archlinux 32-bit. Seems to work.
Offline
When you give me your public ssh key, I can give you slave-access to the build master. Then you can run
bin/build-packages -p virtualboxto only build virtualbox.
Offline
Sent. BTW, I think also my machine builds with two cores. I'll try to find out how to make virtualbox respect the MAKEFLAGS.
Offline
bin/build-packages -p virtualbox
come back later - there are still packages to be built, but currently none has all its dependencies ready
get-assignment told me:
2: come back later - there are still packages to be built,
but currently none has all its dependencies ready
mmh? :-)
Offline
hmm, I guess I made a mistake and it does not hand out blocked packages ... let me check
Offline
yep, should be fixed, now
Offline
it might be, though, that you still won't be able to build this package curretly, because s-nail is seen as a dependency, which is still on the build list at the moment.
Offline
I checked in a patch to PKGBUILD forcing `kmk` to `kmk -j 1`. At least on my
machine I have now only one CPU occupied building virtualbox. Maybe this
will work now also on the other slaves?
Offline
mmh. built and uploaded, but now it's signed with my key (which is not known to pacman).
And I get:
gpg: signing failed: Timeout6_64 package(s) ...
gpg: signing failed: Timeout
done.
The following packages should have been built but are missing or vice versa:
expected: virtualbox-guest-dkms i686
'return-assignment' reports too many or missing packages.
find: '/data/work/archlinux32/builder/bin/../work/tmp.UWIQhF': No such file or directory
So maybe it's better to build it on the official slave?
Offline
...and something got stuck, the build master status still shows:
2017-10-26 15:10 virtualbox 7147fc571eb69b6c646c20ef7ab4169e5e9bed3b 27c128cab8c098dc93de5ef5be34fbbe7b3cab77 community abaumann
Offline
virtualbox.7147fc571eb69b6c646c20ef7ab4169e5e9bed3b.27c128cab8c098dc93de5ef5be34fbbe7b3cab77.community.2017-10-27T05:21:38.build-log
virtual memory exhausted: Operation not permitted
happens again also with 'kmk -j 1'
Offline