openblas: use "all" target since it's marked sequential#35905
openblas: use "all" target since it's marked sequential#35905haampie merged 2 commits intospack:developfrom
Conversation
|
Hi @haampie! I noticed that the following package(s) don't yet have maintainers:
Are you interested in adopting any of these package(s)? If so, simply add the following to the package class: maintainers("haampie")If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with $ spack blame openblasThank you for your help! Please don't add maintainers without their consent. You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer. |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
haampie
force-pushed
the
fix/openblas-again
branch
from
d949520 to
37ca263
Compare
openblas likes to concurrently writes to the same archive from different targets, and solves that through .NOTPARALLEL: all We run `make x y z` which is not affected by `NOTPARALLEL`, running into races.
alalazo
force-pushed
the
fix/openblas-again
branch
from
37ca263 to
e668acf
Compare
openblas likes to concurrently writes to the same archive from different targets, and solves that through .NOTPARALLEL: all We run `make x y z` which is not affected by `NOTPARALLEL`, running into races.
2 participants
openblas likes to concurrently write to the same archive from different
targets, and solves that through .NOTPARALLEL: all
We run
make x y zwhich is not affected byNOTPARALLEL, running intoraces.
This adds back the
teststarget unconditionally, but I don't see a betterway other than running
make x && make y && make z.