6c9467e8c6
Our `LockTransaction` class was reading overly aggressively. In cases
like this:
```
1 with spack.store.db.read_transaction():
2 with spack.store.db.write_transaction():
3 ...
```
The `ReadTransaction` on line 1 would read in the DB, but the
WriteTransaction on line 2 would read in the DB *again*, even though we
had a read lock the whole time. `WriteTransaction`s were only
considering nested writes to decide when to read, but they didn't know
when we already had a read lock.
- [x] `Lock.acquire_write()` return `False` in cases where we already had
a read lock.
|
||
|---|---|---|
| .. | ||
| cpu | ||
| tty | ||
| __init__.py | ||
| argparsewriter.py | ||
| filesystem.py | ||
| lang.py | ||
| link_tree.py | ||
| lock.py | ||
| multiproc.py | ||