-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
use Watchdog in auto command #101
Conversation
Any Windows testers? I could volunteer if given a test dodo.py file. |
Windows guys: @joschkazj @gstorer. I am working on supporting the https://ci.appveyor.com/project/schettino72/doit/build/1.0.74/job/7jlkh5xuv1g282ni#L392 |
@Kwpolska better start looking at the test failure I mentioned above. At the moment I guess the code wont run at all on Windows. sample dodo.py
|
@schettino72 this could just be a race condition, maybe try to throw in a |
I dont think it is a race condition because the first assert passed. Seems the file was added twice into the list of events... I am not really willing to debug code using appveyor so I am asking for help. or windows will still lag behind. |
@schettino72 On my Mac setup with Python 3, I don't have time to look into this right now, but I wanted to let you know the results. |
Using As a point of reference, here is the
Running |
Add tests for Mac OS X
@philipbl thanks. It got stuck the same way :( and have more failures. Can you please take a look into it? |
@schettino72's sample works fine for me on the Windows command-line. I had to quit doit via Ctrl+Break though, Ctrl+C had no effect for me. EDIT: This is on Python 2.7.9 Failing tests in
To me the pickling issue is to be expected as the function ok() is not part of the test class instance but only defined at runtime of the method. I had similar issue when testing the multiprocessing fix on Windows. |
Thanks @joschkazj . It is a good news the fact the problems are specific to tests. About What about It would be great if you can investigate further the issues and propose a patch fixing them 😬 |
No, it seems to work (the skipped test is due to Python 2.x):
Ctrl+C can be caught by the application (e.g. IPython kernels react to it and exit gracefully), while Ctrl+Break is sent directly to the Windows OS and kills the application (official documentation). |
The test being skipped on python2.7 is So the |
@philipbl with which version of python you tested the command line OS X ? |
OS X works. One issue that I've noticed when using doit with TDD, a failing test causes doit to continuously run until you fix the test. I'm not sure if this is intended or not. It doesn't appear to be related to this change. |
thanks for the feedback
This is not intended and should be already be fixed in this branch. Do you have an example? There are too many issues with tests. I will not merge this branch in the current situation... Another thing that makes me think twice is the state of watchdog, |
looks like watchdog project is dead. not a single commit last year... |
Problems
all
windows
https://ci.appveyor.com/project/schettino72/doit/build/1.0.80/job/2reaoab0826imtix#L330
mac
linux