Slava> The io.monitors tests include a test that triggers an error
Slava> condition, so the trace you're seeing is part of the tests. Look
Slava> for a yellow error bar with a unit test icon at the bottom (in
Slava> the UI) or a message ':test-failures -- show 123 test failures'
Slava> in the terminal listener to see if anything failed.

There's no such bar or message, so I assume it passes; I do get a "Press
F3 to view errors" message, and three of the errors are a little odd:

  resource:basis/io/monitors/linux/linux-tests.factor: 13
  Unit Test: { [ ] [ "monitor-test-self" temp-file f <monitor> "m" set ] }
  Unix system call failed:
  No space left on device (28)
  [Traceback]

  resource:basis/io/monitors/monitors-tests.factor: 94
  Unit Test: {
      [ ]
      [ [ "" resource-path f <monitor> ] with-monitors dispose ]
  }
  Unix system call failed:
  No space left on device (28)
  [Traceback]

  resource:basis/io/monitors/monitors-tests.factor: 102
  Unit Test: {
      [ ]
      [ "monitor-timeout-test" temp-file f <monitor> "m" set ]
  }
  Unix system call failed:
  No space left on device (28)
  [Traceback]

None of my discs are anywhere near full.  The one Factor is executing on
has 19 gigabytes (34%) free.  I also get a few "wait-timeout"s and "No
suitable method"s ("Generic word set-timeout does not define a method
for the POSTPONE: f class").

Slava> You can test monitors as follows in the listener:

So I tried this in the listener (also resource:temp, and also naming a
file rather than a directory):

  USING: io.monitors ;
  "/home/conrad/factor/factor/temp" t <monitor>
  [ next-change . flush t ] curry loop

I tried touching the directory, adding, modifying and removing files and
subdirectories within it, and (with the file instead of directory
reference) modifying and saving the file.  None of these produce any
output in the listener, but nor do they result in output on a machine
where refresh works.  I assume I'm doing something wrong, will try more
carefully later.

Conrad

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


------------------------------------------------------------------------------
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

Reply via email to