Re: [racket-dev] Pre-Release Checklist for v5.3.4, Second Call
On 23 Apr 2013, at 04:29:42, Ryan Culpepper wrote: > * Kathy Gray > - Test Engine Tests Done -Kathy _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] 5.3.2 & mac os x
On 19 Jan 2013, at 18:35:13, Robby Findler wrote: > Dear all: we have a new .dmg layout setup for the mac os x version of Racket > and so if you have time to have a look and see if it looks reasonable on your > machine and report back here, that would be helpful. > It looks reasonable on my mac, OS X v10.7.5 -Kathy > Here is a pointer to the current release candidate: > >http://pre.racket-lang.org/release/installers > > Thanks, > Robby > _ > Racket Developers list: > http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Pre-Release Checklist for v5.3.2
On 17 Jan 2013, at 18:46:37, Ryan Culpepper wrote: > * Kathy Gray > - Test Engine Tests Done -Kathy _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Pre-Release Checklist for v5.3
On 24 Jul 2012, at 16:03, Ryan Culpepper wrote: > * Kathy Gray > - Test Engine Tests Done -Kathy _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Pre-Release Checklist for v5.3
On 18 Apr 2012, at 16:00, Ryan Culpepper wrote: > * Kathy Gray > - 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
On 20 Jan 2012, at 20:18, Ryan Culpepper wrote: > * Kathy Gray > - Test Engine Tests Done -Kathy _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] [racket] Disable/Enable Tests
I don't recall our original reasoning, but I envision that with such a macro students will think they are only disabling the tests "below" the "call" and become confused. This isn't to say we shouldn't switch to a macro -Kathy On 28 Nov 2011, at 13:23, Matthias Felleisen wrote: Why does this have to be a menu? Why not add a macro to the test-engine code so that students can write (disable-tests) On Nov 28, 2011, at 2:30 AM, Michael Sperber wrote: Robby Findler writes: [ moved to dev ] Apparently this broke somewhere in between v5.0 (June 2010) where it works and v5.1 (Feb 2011) where it doesn't. I can't use git bisect to find the precise commit because the earlier version doesn't compile on either my windows or my mac machine (mac is lion and windows uses too new of a version of visual studio). And I *hate* touching this code because something always ends up broken. I got really mad last time this code broke and so I hope we have better test suites now because of that, but I'm really not excited by the prospect of trying to change it again. Not only is the code hard to understand because it is poorly written, it is also unclear what parts of DrRacket it influences. Given all of this, my inclination is to simply remove this option. So far the only one who has spoken in favor of it gave a reason that (thankfully) no longer applies. Any objections? Comments? Mike? Some tests (especially check-property-based tests) are expensive, and you don't always want to run them - especially with world/universe- based code. Is there a way to have that option only with the student languages? -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla _ 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.2, Second Call
On 20 Oct 2011, at 8:36:28, Ryan Culpepper wrote: > * Kathy Gray > - 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
On 19 Jul 2011, at 10:16:01, Ryan Culpepper wrote: > * Kathy Gray > - 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
On 24 Apr 2011, at 2:04:47, Ryan Culpepper wrote: > * Kathy Gray > - Test Engine Tests Done _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] overwrite
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 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 >>> 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 : >>>>>>>>> >>>>>>>>> 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 >>>>>>>> Assistant Professor / Brigham Young University >>>>>>>> http://faculty.cs.byu.edu/~jay >>>>>>>> >>>>>>>> "The glory of God is Intelligence" - D&C 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] overwrite
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 : >>> >>> 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 >> Assistant Professor / Brigham Young University >> http://faculty.cs.byu.edu/~jay >> >> "The glory of God is Intelligence" - D&C 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
Re: [racket-dev] Pre-Release Checklist for v5.0.2
On 22 Oct 2010, at 12:07:18, Ryan Culpepper wrote: > * Kathy Gray > - Test Engine Tests Done -Kathy _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] internal definitions & stepper
On 19 Oct 2010, at 6:42:45, John Clements wrote: > Kathy, can you confirm that the test-engine code is always happy with a value > of #f for test~object? Yes. -Kathy _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] stepper UI question
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
