move test-harness to lisp/ directory so it gets byte-compiled -------------------- ChangeLog entries follow: -------------------- etc/ChangeLog addition: 2010-02-22 Ben Wing <ben@xemacs.org> * dbxrc.in: test-harness.el is in lisp directory now. lisp/ChangeLog addition: 2010-02-22 Ben Wing <ben@xemacs.org> * test-harness.el: * test-harness.el (test-harness-from-buffer): * test-harness.el (batch-test-emacs): Move file from tests/automated into lisp/ so it gets byte-compiled. This significantly reduces the amount of extra crap in outputted backtraces. Delete hack in batch-test-emacs to look for test-harness.el in the test directory since it's not there any more. Also, in `Check-Message', incorporate call to `Skip-Test-Unless' in the macro output rather than its body, to avoid problems byte- compiling the file -- `Skip-Test-Unless' isn't available in the environment during byte-compilation so we can't call it then. src/ChangeLog addition: 2010-02-22 Ben Wing <ben@xemacs.org> * .gdbinit.in.in: * Makefile.in.in (batch_test_emacs): test-harness.el is in lisp directory now so change how we call it.

/* XPM */
static char * bug_xpm[] = {
"28 28 6 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c Gray60",
"O	c Gray40",
"+	c Gray60",
"@	c white",
"#	c Gray90",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXooooooooooooooooXXXXXX",
"XXXXXoooooooooOoOoOoOooXXXXX",
"XXXXXoooooooooOoOoOoOooXXXXX",
"XXXXXoooooooooooooooooo+XXXX",
"XXXXXXo@@@@@@@@@@@##Xo++XXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXo@@@@@@@@@@@@##XXoXXXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXo@@@@@@o@@oo@##XXo+XXXX",
"XXXXXo@@@o@@o@oooo##XXo+XXXX",
"XXXXXo@@@@o@oo@ooo##XXo+XXXX",
"XXXXXo@@@@@oooooo@##XXo+XXXX",
"XXXXXo@ooo@ooooo@@##XXo+XXXX",
"XXXXXo@@@oo@oooooo##XXo+XXXX",
"XXXXXo@@o@ooooo@@@##XXo+XXXX",
"XXXXXo@oooooo@@o@@##XXo+XXXX",
"XXXXXo@oooooo@@@o@##XXo+XXXX",
"XXXXXo@ooooooo@@@@##XXo+XXXX",
"XXXXXo@ooooo@o@@@@##XXo+XXXX",
"XXXXXo@@ooo@@o@@@@##XXo+XXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXXoooooooooooooooo++XXXX",
"XXXXXX++++++++++++++++++XXXX",
"XXXXXXX++++++++++++++++XXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};