diff options
| author | Todd Gamblin <gamblin2@llnl.gov> | 2022-04-25 00:46:21 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-25 07:46:21 +0000 |
| commit | d729b4e72bf85024bccf87f7a4fb7163cd2407ff (patch) | |
| tree | fd5da7a694d735a1ad4098c47b21e4b88a354459 /var | |
| parent | 35a4c2325ed4c040d95c7bd62892f465cfaa2cca (diff) | |
| download | spack-d729b4e72bf85024bccf87f7a4fb7163cd2407ff.tar.gz spack-d729b4e72bf85024bccf87f7a4fb7163cd2407ff.tar.bz2 spack-d729b4e72bf85024bccf87f7a4fb7163cd2407ff.tar.xz spack-d729b4e72bf85024bccf87f7a4fb7163cd2407ff.zip | |
bugfix: `installed` and `installed_upstream` should not assert (#30271)
Fix bug introduced in #30191. `Spec.installed` and `Spec.installed_upstream` should just return
`False` for abstract specs, as they can be called in that context.
- [x] `Spec.installed` returns `False` now instead of asserting that the `Spec`
is concrete.
- [x] `Spec.installed_upstream` returns `False` now instead of asserting that the `Spec`
is concrete.
- [x] `Spec.installed_upstream` no longer caches its result, as install status seems
like a bad thing to cache -- it can easily be invalidated. Calling code should
use transactions if there are peformance issues, as with other places in Spack.
- [x] add tests for `Spec.installed` and `Spec.installed_upstream`
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions