Re: [racket-dev] Pre-Release Checklist for v5.3.4, Second Call

2013-04-23 Thread Kathy Gray

On 23 Apr 2013, at 04:29:42, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

Done
-Kathy
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Pre-Release Checklist for v5.3

2012-07-25 Thread Kathy Gray

On 24 Jul 2012, at 16:03, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests
Done
-Kathy
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Pre-Release Checklist for v5.3

2012-04-19 Thread Kathy Gray

On 18 Apr 2012, at 16:00, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

Done

-Kathy
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Pre-Release Checklist for v5.2.1, second call

2012-01-24 Thread Kathy Gray

On 20 Jan 2012, at 20:18, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

Done
-Kathy
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Pre-Release Checklist for v5.2, Second Call

2011-10-20 Thread Kathy Gray

On 20 Oct 2011, at 8:36:28, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

Done
-Kathy
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Pre-Release Checklist for v5.1.2

2011-07-24 Thread Kathy Gray
On 19 Jul 2011, at 10:16:01, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests
Done
-Kathy
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Pre-Release Checklist for v5.1.1, second call

2011-04-27 Thread Kathy Gray
On 24 Apr 2011, at 2:04:47, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

Done
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] overwrite

2011-02-26 Thread Kathy Gray
Same answers.
-Kathy

On 26 Feb 2011, at 5:23:56, Matthias Felleisen wrote:

 
 On Feb 26, 2011, at 12:12 PM, Robby Findler wrote:
 
 Are any of you, by any chance:
 
 - using a teaching language (via the language menu, not #lang
 2htdp/bsl or similar)
 
 #lang racket 
 
 
 - hitting run and then save right *after* run
 
 no 
 
 
 
 when you get this message?
 
 Robby
 
 On Sat, Feb 26, 2011 at 11:10 AM, Nadeem Abdul Hamid nad...@acm.org wrote:
 I get this a lot, using just the binary installer version downloaded
 from racket-lang.org. And it happens even when I'm not using
 check-syntax, though it might happen more frequently when I do use
 check-syntax; hard to tell.
 
 
 
 On Sat, Feb 26, 2011 at 12:05 PM, Matthias Felleisen
 matth...@ccs.neu.edu wrote:
 
 Well it just occurred for a file under Git but WITHOUT check syntax.
 
 
 
 On Feb 26, 2011, at 11:48 AM, Matthias Felleisen wrote:
 
 
 I confirm the check syntax observation.
 
 On Feb 26, 2011, at 11:39 AM, Kathy Gray wrote:
 
 I also see this quite frequently (for files not under Git control). I 
 was thinking at one point it might be related to when I run check 
 syntax, but I haven't confirmed a repeatable pattern.
 
 -Kathy
 
 
 
 
 On 26 Feb 2011, at 4:36:37, Matthias Felleisen wrote:
 
 
 The files I have been editing this morning are not under Git control.
 (And yes, I have on one occasion checked the file via Emacs and didn't
 see any difference.)
 
 
 On Feb 26, 2011, at 11:35 AM, Jay McCarthy wrote:
 
 It's from git touching the files and giving them a new timestamp. It
 probably didn't really change.
 
 Jay
 
 2011/2/26 Matthias Felleisen matth...@ccs.neu.edu:
 
 When I use drracket, I frequently get a warning that my file has been 
 modified on disk and the question of whether I want to save the file 
 or revert. Is anyone else suffering from this problem?
 _
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev
 
 
 
 
 --
 Jay McCarthy j...@cs.byu.edu
 Assistant Professor / Brigham Young University
 http://faculty.cs.byu.edu/~jay
 
 The glory of God is Intelligence - DC 93
 
 
 _
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev
 
 
 
 _
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev
 
 
 _
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev
 
 
 
 
 --
 Nadeem Abdul Hamid
 Associate Professor, Computer Science
 Berry College
 PO Box 5014
 2277 Martha Berry Hwy NW
 Mount Berry, GA 30149-5014
 (706) 368-5632
 http://cs.berry.edu/~nhamid/
 
 _
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev
 
 
 
 _
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Pre-Release Checklist for v5.0.2

2010-10-24 Thread Kathy Gray

On 22 Oct 2010, at 12:07:18, Ryan Culpepper wrote:

 * Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

Done
-Kathy
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] stepper UI question

2010-08-26 Thread Kathy Gray
On 26 Aug 2010, at 11:32:48, John Clements wrote:

 3) It's not clear how you want to handle test cases; they don't currently 
 generate anything in the interactions window, and yet this sounds like the 
 thing that you're *most* likely to want to be able to step.  For the sake of 
 argument, let me propose something:
 
 the result of generate-report (the hidden summary-generation call that 
 check-expect inserts) should be a snip that shows up in the interactions 
 window, called (e.g.) Test Report.  Clicking on this (right-clicking on 
 this?) should open a window showing the test cases in some tabular format, 
 indicating which ones succeeded and which ones failed.  Selecting one of 
 these, the user could choose to see its steps. 
 
 Additional hidden benefit of this structure: because of the syntactic 
 fol-de-rol that surrounds test cases, it should be fairly easy in such a 
 tabular window to also show those test cases that didn't get run at all, 
 because an earlier one caused a runtime error.

What about tying the stepper in with the current test result window (that's 
either docked or a free floating window) for stepping through tests? So the 
step = button would appear along with the failed tests and a different drop 
down expansion point with the successful tests to list the separate tests and 
respective step = buttons.

Cheers,
-Kathy
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev