Joachim Pouderoux authored 3 years ago and Spiros Tsalikis committed 1 day ago

Replace mkostemp by mkstemp as done for MACH.

Fix all-to-all in the case of a single block

See merge request diatomic/diy!89

Vicente Bolea authored 1 month ago and Kitware Robot committed 1 month ago

f6993587 ci: add spack ci

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !88

Added load balancing algorithms

See merge request diatomic/diy!87

Fixed memcheck, reduced number of ranks in tests

- changed communication of WorkInfo to be sizeof in bytes and use MPI_BYTE datatype
- reworked callback for local block work similar to Master::foreach to parameterize w/o templating on Block
- embedded WorkInfo in detail namespace
- removed templates for any functions in algorithms and detail that don't use Block anymore

- moved local work out of master, isolated to load balancing algorithms
- mpi communicating WorkInfo directly without packing/unpacking to a
  vector

Also changed uint type to unsigned int to satisfy windows compilers

Coroutines

See merge request diatomic/diy!51

Ben Boeckel authored 4 months ago and Kitware Robot committed 4 months ago

5f426245 gitlab-ci: remove `dependencies` from jobs

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !86

Historically, `needs` specifies the jobs which need to complete
successfully and `dependencies` specifies the jobs which provide
artifacts which should be used. Modern GitLab discourages using both as
`needs` now supports an `artifacts` key to say "depend on but do not use
artifacts", so remove `dependencies` and use `needs:artifacts` where
necessary.

See: https://docs.gitlab.com/ee/ci/yaml/#needsartifacts

Vicente Bolea authored 4 months ago and Kitware Robot committed 4 months ago

e5fecfc9 ci: remove executable permissions from `.ps1` scripts
68857bef ci: use JSON to transfer environment variables

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Vicente Bolea <vicente.bolea@kitware.com>
Merge-request: !85

PowerShell scripts are not inherently executable and therefore should not have
the executable bit set.

The `set` command in `cmd` has terrible properties in that there's no
real structure to it. Sensitive sequences in values or variable names
that are escaping sequences can be interpreted at the wrong time or
things like newlines in values are not escaped at all and cause
ambiguities in parsing. Avoid all of that and use PowerShell to use JSON
as a communication mechanism.

mark Collection::release as inline

See merge request diatomic/diy!84

If also `release` is marked as inline, just as all the other methods
defined outside the class definition of `Collection`, then the header
can be included from several compilation units without causing multiple
definitions of this method. This was broken in
12e3ce8c.

Fix master release, revised

See merge request diatomic/diy!83