This is broken and not going to go anywhere soon. I'll resubmit once fixed.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #821.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/821#event-3006041141___
Rpm-maint mailing list
> Evidently better way is to emit an error.
No kidding? :joy:
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Yeah, known. Missing/wrong arguments to built-in macros are wildly
> inconsistent in how they behave, some emit errors, some just fail silently
> etc.
Evidently better way is to emit an error.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
> * The expansion of macro %{getmem:virt}" finishes with an error. It is
> because getmem returns 0. This is caused by the fact that function
> getmem_virt returns SIZE_MAX. After dividing by 1024^2 it is still to high to
> fit into return_type of getmem (unsigned int).
Right. I probably
I tested this PR on my laptop.
- The expansion of macro %{getmem:virt}" finishes with an error. It is because
getmem returns 0. This is caused by the fact that function getmem_virt returns
SIZE_MAX. After dividing by 1024^2 it is still to high to fit into return_type
of getmem (unsigned int).
for the record, there are already packages like ceph or firefox that do their
own heuristics, and I'm not sure it's always correct, so having a system way is
definitely step in the right direction
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
This PR is to address two different but related issues:
1) On 32bit systems, available virtual memory is in practise very limited and
easy to exhaust on systems with many CPUs. (RhBug:1729382)
2) There are systems with lot of CPUs (virtual or otherwise) but relatively
limited memory, where just