Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reloads lose namespaces #109

Closed
sdegutis opened this issue Sep 15, 2014 · 5 comments
Closed

Reloads lose namespaces #109

sdegutis opened this issue Sep 15, 2014 · 5 comments
Labels

Comments

@sdegutis
Copy link
Contributor

Reproduction steps

  1. Run tests in an existing project using auto-run mode
  2. Define a test that calls a non-existent function
  3. Implement the function in another file

What should happen

All tests should pass again.

What actually happens

The tests fail with java.lang.Exception: No namespace: some.random.name.space and an actual namespace. Going into the file for that namespace and saving the file will make this failure go away, but the test will fail with another namespace error. This usually repeats about 4 or 5 times for me before it goes to green.

EDIT

I can reproduce this more simply:

  1. Run test suite in auto-run mode
  2. Change anything in any non-test file and save it
@sdegutis sdegutis added the bug label Sep 15, 2014
@trptcolin
Copy link
Collaborator

I just created a new project via lein new speclj foo, and so far I'm not able to reproduce this.

  1. Does a fresh project (via lein new speclj foo) have the problem for you?
    • If not, is there any trimmed-down project you can share that does, so we can see what's different?
    • If so, what leiningen version are you on? (I'm assuming you're on speclj 3.1.0, but that version might help see what the difference is too.)
  2. There is no number 2 that I can think of right now.

@sdegutis
Copy link
Contributor Author

I was using 3.0.1 when I reported this bug. Just upgraded to 3.1.0 today and cannot reproduce (although I didn't try very hard). Closing as probably fixed already.

@sdegutis sdegutis reopened this Oct 10, 2014
@sdegutis
Copy link
Contributor Author

I was able to reproduce this again this week, although I still haven't figured out a reliable way to create a small reproducable test-case. It's a very frustrating bug.

@slagyr
Copy link
Owner

slagyr commented Mar 9, 2015

I'm also unable to reproduce. And you're latest "Edit" is very suspicious. Editing and saving any file, including non-test files, is something I am ALWAYS doing and I do not see there error you describe.

Considerations:

  • Is your dev environment creating lots of extra files? Temp files?
  • Is there something unique about your file system such that the test process doesn't see changes right away?

Closing for now.

@slagyr slagyr closed this as completed Mar 9, 2015
@sdegutis
Copy link
Contributor Author

@slagyr Good points. To answer your questions:

  1. My IDE isn't creating any extra files when I save.
  2. It's a regular Mac OS X file system (HFS+ Journaled, case sensitive) in Yosemite on a Mac Pro, so I guess it's a pretty average file system.

Either way, someone else seems to be having a similar problem in #127. We should merge these two issues into that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants