On Tue, Oct 20, 2009 at 11:17 AM, Conrad Hughes <[email protected]> wrote: > The test run ends as follows --- it's not clear to me whether this is a > pass or not, but I get this same result on another system on which > refresh works correctly:
The io.monitors tests include a test that triggers an error condition, so the trace you're seeing is part of the tests. Look for a yellow error bar with a unit test icon at the bottom (in the UI) or a message ':test-failures -- show 123 test failures' in the terminal listener to see if anything failed. > It is, but I get the same results on a local ext3 file system mounted off > /dev/hda1. If the the tests pass, then it means creating files and watching them for changes works in the Factor source tree at least (the tests create files under resource:temp/). You can test monitors as follows in the listener: USING: io.monitors ; "/path/to/some/dir" t <monitor> [ next-change . flush t ] curry loop Then try creating files and directories inside /path/to/some/dir and see if anything is logged in the listener. Let me know if you find any reproducible test case where they fail. Slava ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
