On Mon, Aug 4, 2008 at 5:00 AM, Dan McGee <[EMAIL PROTECTED]> wrote: > Instead of pausing 1.5 seconds on tests that check file mtimes, change the > mtimes to something in the far past so we can immediately tell if a file was > modified and/or touched. This saves a decent amount of time on the upgrade > tests which often check mtimes. > > 355 was a completely arbitrary time value, don't ask me why I picked it. >
This is great. Now that I think about it, I always noticed this delay when running pactests with MODIFIED rules. I tested it on cygwin, and it worked perfectly. Nice time saver too. Before: pactest/pactest.py -p src/pacman/pacman -t pactest/tests/upgrade0* 24.46s user 22.75s system 66% cpu 1:10.92 total After: pactest/pactest.py -p src/pacman/pacman -t pactest/tests/upgrade0* 24.90s user 21.81s system 95% cpu 48.818 total _______________________________________________ pacman-dev mailing list [email protected] http://archlinux.org/mailman/listinfo/pacman-dev
