Actions
Bug #11010
closedTake into account aspects when caching models
Start date:
11/11/2021
Due date:
% Done:
0%
Estimated time:
Detected in build:
git
Platform:
Published in build:
Description
If one runs verification of several requirement specifications within one job and simultaneously requires to use aspects of those requirement specifications for weaving common models, current caching approach can fail since it will cache and then reuse models that are woven in using only one aspect(s) from one requirement specification while other ones can require other aspects being used. I suppose to distinguish not only models but also aspects when caching them.
Updated by Evgeny Novikov about 3 years ago
- Related to Bug #10476: Distinguish models by their absolute paths rather than their contents added
Updated by Evgeny Novikov about 3 years ago
- Status changed from New to Closed
I resolved this in branch bug-11010. After that branch passed tests, I merged it to master in b63d006ca.
Actions