search

linemanjs / lineman

Lineman helps you build fat-client JavaScript apps. It produces happiness by building assets, mocking servers, running specs on every file change
MIT License
1.18k stars 80 forks source link

Does lineman cache the testem config somewhere? #308

Closed tandrewnichols closed 10 years ago

tandrewnichols commented 10 years ago

I opened airportyh/testem#395 because I was seeing some testem changes persist even after switching branches and was told they don't cache the config. Could this be from lineman somehow? Doesn't seem likely since I tried restarting lineman . . . just trying to track down the problem.

davemo commented 10 years ago

Given Testem reads files from the generated directory it is possible that switching branches can leave behind stale copies of files which would get picked up. I've seen this behaviour before and have just built up muscle memory where I do a lineman clean run after switching branches.

tandrewnichols commented 10 years ago

Maybe, though I never ran lineman clean to fix the problem... restarting the terminal was what finally fixed it for me.

davemo commented 10 years ago

I imagine lineman clean would fix it as well; but that's just a hunch.

searls commented 10 years ago

Yeah, to my knowledge testem does not cache anything between runs (obviously it holds onto its own config in memory and that sticks for the life of the process.

Usually we get this feedback when someone is (a) not running lineman run while running lineman spec, and both need to run simultaneously during development to keep the code up-to-date, or (b) lineman run is triggering errors preventing concatenation which the downstream tests can't see

On Fri, Aug 8, 2014 at 10:43 AM, David Mosher notifications@github.com wrote:

I imagine lineman clean would fix it as well; but that's just a hunch.

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/308#issuecomment-51611195

tandrewnichols commented 10 years ago

@davemo @searls Indeed, lineman clean also fixed the problem.