Slow filenotify-tests
Eli Zaretskii <[email protected]>
| Newsgroups | gmane.emacs.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, I've run filenotify-tests today on a GNU/Linux machine, and found many of the remote tests to be too slow: passed 2/28 file-notify-test00-availability-remote (1.716848 sec) passed 4/28 file-notify-test01-add-watch-remote (1.238100 sec) passed 6/28 file-notify-test02-rm-watch-remote (17.882603 sec) passed 8/28 file-notify-test03-events-remote (166.341733 sec) passed 10/28 file-notify-test04-autorevert-remote (19.500194 sec) passed 12/28 file-notify-test05-file-validity-remote (51.576937 sec) passed 16/28 file-notify-test07-many-events-remote (324.932327 sec) passed 18/28 file-notify-test08-backup-remote (30.162599 sec) passed 20/28 file-notify-test09-watched-file-in-watched-dir-remote (127.011329 sec) passed 22/28 file-notify-test10-move-file-to-another-watched-dir-remote (43.803668 sec) passed 26/28 file-notify-test12-symlinks-remote (44.753902 sec) passed 28/28 file-notify-test12-unmount-remote (14.924635 sec) This is with gio library, in case it matters. Shouldn't the remote tests be marked as "expensive"?