| 01:39.02 | *** join/#devlounge kergoth_ (~kergoth@ip71.churchill-park.dfw.ygnition.net) |
| 01:40.46 | *** join/#devlounge kergoth (~kergoth@ip71.churchill-park.dfw.ygnition.net) |
| 01:47.49 | *** join/#devlounge kergoth (~kergoth@ip71.churchill-park.dfw.ygnition.net) |
| 02:26.59 | kergoth | bleh |
| 03:08.40 | *** join/#devlounge kergoth_ (~kergoth@li11-226.members.linode.com) |
| 07:15.07 | *** join/#devlounge gma (~graham@capella.plus.com) |
| 10:06.00 | *** join/#devlounge bertheau (~bertheau@dicaprio.akademie1.de) |
| 13:13.04 | *** join/#devlounge __moray (~moray@dsl-217-155-67-241.zen.co.uk) |
| 14:38.46 | TD | hola |
| 16:25.07 | kergoth | bleh |
| 17:04.09 | CosmicPenguin | <PROTECTED> |
| 17:04.10 | CosmicPenguin | A C compiler that generates Java Byte Code for the Java Virtual Machine? !! |
| 17:04.10 | CosmicPenguin | Sounds like a developer's pipe-dream? Well, we have it here for you to download. |
| 17:04.17 | CosmicPenguin | Sounds like a developers crack pipe dream to me |
| 17:05.48 | TD | lol |
| 17:20.54 | *** join/#devlounge nullpuppy (~dustin@c-67-168-57-175.client.comcast.net) |
| 19:38.41 | *** join/#devlounge mathrick (~mathrick@195.116.35.55) |
| 22:16.23 | *** join/#devlounge sri ([Xh0M+fybD@onyx.spiritone.com) |
| 23:13.36 | kergoth | ugh |
| 23:13.39 | kergoth | i want my motivation back |
| 23:13.39 | kergoth | damnit |
| 23:16.46 | CosmicPenguin | kergoth: with check, are each of the tests in a case generally considered seperate? |
| 23:17.01 | CosmicPenguin | ie - if I set something up with one test, then execute it in a subsequent test, is that good form? |
| 23:17.25 | kergoth | not sure, i'd wondered about that myself. some tests by their nature do the same things as others |
| 23:17.34 | kergoth | like read, write, then a test to write and read and compare the values |
| 23:18.59 | kergoth | if you find a clean way to do that, let me know |
| 23:19.44 | CosmicPenguin | Ok... |
| 23:19.50 | CosmicPenguin | Its starting to sound like they have to be seperate tests |
| 23:19.52 | CosmicPenguin | which is annoying |
| 23:19.58 | kergoth | currently i'm keeping them all completely seperate, and doing everything manually |
| 23:20.00 | CosmicPenguin | though I guess we could always share code |
| 23:20.07 | kergoth | the tests are declared as static |
| 23:20.12 | kergoth | so tests within the same file could call one another |
| 23:20.13 | kergoth | but thats about it |
| 23:20.20 | CosmicPenguin | Thats what I'm talking about actually |
| 23:20.20 | kergoth | keep that in mind |
| 23:20.28 | kergoth | i got bit by that when i was trying to put each test in its own file |
| 23:20.33 | kergoth | heh |
| 23:20.33 | CosmicPenguin | Ahh... |
| 23:20.40 | kergoth | that why its one case per file in rtctest |
| 23:20.41 | CosmicPenguin | So I can make a test depend on the previous test then? |
| 23:20.48 | kergoth | good question |
| 23:20.56 | kergoth | i doubt it, but itd be nice |
| 23:21.00 | CosmicPenguin | Right |
| 23:21.09 | kergoth | otherwise a single problem that affects others will report as 8 failures or whatever |
| 23:21.12 | CosmicPenguin | Because I do need to test exactly what you said - write, read and compare |
| 23:21.32 | kergoth | that said, the one failure is a big enough problem to break 8 things, perhaps it should look that bad |
| 23:21.33 | CosmicPenguin | I guess we can always change it later |
| 23:21.35 | kergoth | heh |
| 23:22.11 | kergoth | i'd like to get a sort of a best practices check usage template repo |
| 23:22.18 | kergoth | checkexample/ or something |
| 23:22.35 | CosmicPenguin | Yeah |
| 23:22.43 | CosmicPenguin | We should propose that to the site owners |
| 23:23.03 | CosmicPenguin | I don't see any reason why we can't all share OSS testing, for an example |
| 23:23.13 | kergoth | yeah |
| 23:23.33 | kergoth | like the rtctest. thats a known interface used by everyone. same deal |
| 23:25.41 | CosmicPenguin | We're probably going to start writing unit tests for stuff like audio, and kfb |
| 23:25.48 | CosmicPenguin | so we'll offer those up for general usage |
| 23:26.12 | kergoth | thatd be useful |
| 23:26.29 | kergoth | perhaps we should create a new project on sf/berlios to collect check based linux kernel unit tests |
| 23:26.36 | kergoth | heh |
| 23:41.38 | CosmicPenguin | kergoth: check forks the tests right? So I don't have to worry about freeing memory if fail_unless is asserted? |
| 23:41.43 | kergoth | yeah |
| 23:41.48 | CosmicPenguin | nice |
| 23:41.57 | kergoth | thats how it can deal with signals and stuff |
| 23:42.06 | kergoth | i think so, anyway |
| 23:42.16 | kergoth | i know it runs them in its own address space |
| 23:42.43 | kergoth | heh |
| 23:42.47 | kergoth | it can deal with a segmentation fault |
| 23:42.49 | kergoth | it must be forking |