17 May
2013
17 May
'13
10:03 a.m.
The testsuite does check whether the package.cache timestamp changed while running a test. If it did then you'll get a Package cache timestamps do not match: [...] framework failure. Do you know whether that happened? If it checks cache local to the build tree, then I have no idea. I just run the validation and don't touch the tree until validation ends. If it checks the global cache in ~ then I have a suspicion of what might have happened - will check that.
Otherwise, looking at why the package.cache is out of date, along with what tests were run around the time that it happened, might give a clue as to what went wrong. Thanks Ian, I will keep that in mind and try to investigate the problem when it happens again.
Janek