Tk Source Code: View Ticket

Ticket UUID:	602667
Title:	cursor-3.1 fails
Type:	Bug	Version:	obsolete: 8.4b3
Submitter:	dgp	Created on:	2002-08-30 22:35:23
Subsystem:	31. Cursor Names	Assigned To:	wolfsuit
Priority:	5 Medium	Severity:
Status:	Closed	Last Modified:	2002-09-03 08:29:33
Resolution:	Fixed	Closed By:	das
		Closed on:	2002-09-03 01:29:33
Description:	Building and testing the macosx-8-4-branch tip on Solaris/CDE shows 15 new failed tests compared to the HEAD. Would be good to fix these prior/during the merge. ==== cursor-3.1 Tk_FreeCursorFromObj - reference counts FAILED ---- Result was: {} {} {} {} ---- Result should have been (exact matching): {{3 1}} {{2 1}} {{1 1}} {} ==== cursor-3.1 FAILED ==== safe-1.1 Safe Tk loading into an interpreter FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-1.1 FAILED ==== safe-1.2 Safe Tk loading into an interpreter FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): bell cd clipboard encoding exec exit fconfigure file glob grab load menu open pwd selection send socket source tk toplevel wm ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-1.2 FAILED ==== safe-1.3 Safe Tk loading into an interpreter FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): encoding exit file load source ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-1.3 FAILED ==== safe-2.1 Unsafe commands not available FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ok ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-2.1 FAILED ==== safe-2.2 Unsafe commands not available FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ok ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-2.2 FAILED ==== safe-3.1 Unsafe commands are available hidden FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ok ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-3.1 FAILED ==== safe-3.2 Unsafe commands are available hidden FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ok ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-3.2 FAILED ==== safe-4.1 testing loadTk FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-4.1 FAILED ==== safe-4.2 testing loadTk -use FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-4.2 FAILED ==== safe-5.2 multi-level Tk loading with clearance FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-5.2 FAILED ==== safe-6.1 loadTk -use windowPath FAILED ---- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-6.1 FAILED ==== safe-7.1 canvas printing FAILED -- Result was: Can't find a usable tk.tcl in the following directories: {$p(:147:)} $p(:147:)/tk.tcl: script error script error invoked from within "source {$p(:147:)/tk.tcl}" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $file]" This probably means that tk wasn't installed properly. ---- Result should have been (exact matching): 0 ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 0 2 ==== safe-7.1 FAILED ==== send-15.1 UpdateCommWindow procedure FAILED ---- Result was: {tktest {tk #5} {tk #3}} {t_s_2 t_s_1 tktest {tk #5} {tk #3}} {t_s_2 tktest {tk #5} {tk #3}} {tktest {tk #5} {tk #3}} ---- Result should have been (exact matching): tktest {t_s_2 t_s_1 tktest} {t_s_2 tktest} tktest ==== send-15.1 FAILED ==== tk-1.2 tk command: general FAILED ---- Result was: 1 {bad option "xyz": must be appname, caret, scaling, useinputmethods, or windowingsystem} ---- Result should have been (exact matching): 1 {bad option "xyz": must be appname, caret, scaling, or useinputmethods} ==== tk-1.2 FAILED
User Comments:	das added on 2002-09-03 08:29:33: Logged In: YES user_id=90580 I've just checked, and indeed it appears that we have a heart cursor defined on macosx as well, so the tests should be fine, not sure what the reason for the change was. following this up in bug 603781 with Jim. hobbs added on 2002-09-03 07:56:09: Logged In: YES user_id=72656 We can, but that in itself exposes a problem - 'heart' is supposed to be defined on all platforms (according to the cursor man page). This is true with lots of "X" cursors on Windows, as they are defined by Tk. Perhaps we need to do something similar for OS X? das added on 2002-09-03 07:49:51: Logged In: YES user_id=90580 the trouble is that there is no 'hear' cursor on OSX. Could we set/use a platform dependent variable for the cursor? (set to hear by default and to arrow on macosx) hobbs added on 2002-09-03 07:22:48: Logged In: YES user_id=72656 I've reverted the test to use 'heart' instead of 'arrow' again. See notes - this was originally done on 2001-04-03. Do we need a 3rd cursor to test against? dgp added on 2002-09-03 07:03:12: Logged In: YES user_id=80530 re-opened just for cursor-3.1 which still fails. hobbs added on 2002-09-03 04:50:02: Logged In: YES user_id=72656 the safe.tcl tests had to do with tk windowingsystem not being available in safe interps. I corrected this to make 'tk' available, but just for the caret and windowingsystem commands. Other tests needed updated for the new subcommand.