Bug#1092110: esys-particle: autopkgtest failure in Ubuntu
Graham Inggs
ginggs at debian.org
Sat Jan 4 16:44:05 GMT 2025
Source: esys-particle
Version: 2.3.5+dfsg2-8
Hi Maintainer
Since the upload of 2.3.5+dfsg2-8, esys-particle has been failing its
own autopkgtests in Ubuntu [1]. I've copied what I hope is the
relevant part of the log below.
I believe this is related to the dropping of '--oversubscribe' in a
recent commit [2].
Regards
Graham
[1] https://autopkgtest.ubuntu.com/packages/esys-particle/plucky/amd64
[2] https://salsa.debian.org/science-team/esys-particle/-/commit/532ba2a390ba2050ebf06dac7249528d2ae89974
1482s There are not enough slots available in the system to satisfy the 3
1482s slots that were requested by the application:
1482s
1482s esysparticle
1482s
1482s Either request fewer procs for your application, or make more slots
1482s available for use.
1482s
1482s A "slot" is the PRRTE term for an allocatable unit where we can
1482s launch a process. The number of slots available are defined by the
1482s environment in which PRRTE processes are run:
1482s
1482s 1. Hostfile, via "slots=N" clauses (N defaults to number of
1482s processor cores if not provided)
1482s 2. The --host command line parameter, via a ":N" suffix on the
1482s hostname (N defaults to 1 if not provided)
1482s 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
1482s 4. If none of a hostfile, the --host command line parameter, or an
1482s RM is present, PRRTE defaults to the number of processor cores
1482s
1482s In all the above cases, if you want PRRTE to default to the number
1482s of hardware threads instead of the number of processor cores, use the
1482s --use-hwthread-cpus option.
1482s
1482s Alternatively, you can use the --map-by :OVERSUBSCRIBE option to
ignore the
1482s number of available slots when deciding the number of processes to
1482s launch.
More information about the debian-science-maintainers
mailing list