| 19:45.05 | *** join/#brlcad ibot (~ibot@rikers.org) |
| 19:45.05 | *** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || logs: http://ibot.rikers.org/%23brlcad/ || Congratulations to our 11 accepted GSoC students!! |
| 19:57.34 | CIA-23 | BRL-CAD: 03carlmoore * r51770 10/brlcad/trunk/src/conv/bot_shell-vtk.1: correct spelling of what was 'ancountered','outout' |
| 20:22.01 | CIA-23 | BRL-CAD: 03crdueck * r51771 10/brlcad/trunk/include/vmath.h: update HEQUAL and V2EQUAL to use the HNEAR_EQUAL and V2NEAR_EQUAL macros respectively |
| 20:29.34 | CIA-23 | BRL-CAD: 03crdueck * r51772 10/brlcad/trunk/src/libged/analyze.c: revert r51767, HEQUAL now uses the HNEAR_EQUAL macro |
| 20:58.46 | CIA-23 | BRL-CAD: 03Ksuzee 07http://brlcad.org * r4283 10/wiki/User:Ksuzee/Reports: |
| 21:25.38 | brlcad | waves back to DarkCalf |
| 21:26.46 | brlcad | andrei_: ask those questions, very interested in those unit tests |
| 21:27.08 | brlcad | hopefully as many distinct and comprehensive tests.. :) |
| 21:29.27 | brlcad | andrei_: you wouldn't be writing unit tests correctly if you didn't uncover SEVERAL ways to produce a segfault |
| 21:30.41 | brlcad | when you find a segfault case, I suggest trying to debug the issue to see if you can make a minimal patch that prevents the crash |
| 21:30.54 | brlcad | the test itself (crashing or not) is good to go |
| 21:35.44 | andrei_ | hello brlcad |
| 21:35.44 | andrei_ | so |
| 21:35.48 | andrei_ | if I have in a tes |
| 21:35.50 | andrei_ | t |
| 21:36.38 | andrei_ | let s say, two cases of segfault and the second one is never reached by the first one, should I submmit it like that ? Or should I fix the " minimal patch" and submit it after? |
| 21:37.08 | andrei_ | what I meant is that a program exists when it encounters a segfault. It never reaches the other case |
| 21:41.40 | CIA-23 | BRL-CAD: 03Elf11 07http://brlcad.org * r4284 10/wiki/User:Elf11: |
| 21:43.26 | CIA-23 | BRL-CAD: 03Elf11 07http://brlcad.org * r4285 10/wiki/User:Elf11: |
| 21:45.01 | andrei_ | another question : pkg_conn has a rather large number of fields. There are several functions that receive only pkg_conn type parameter. Should I test every field from pkg_conn ? |
| 21:45.35 | CIA-23 | BRL-CAD: 03Elf11 07http://brlcad.org * r4286 10/wiki/User:Elf11: |
| 21:48.20 | CIA-23 | BRL-CAD: 03Elf11 07http://brlcad.org * r4287 10/wiki/User:Elf11: |
| 21:57.55 | DarkCalf | brlcad, are you guys in san diego? |
| 22:12.32 | ``Erik | some of 'em are in la for siggraph |
| 22:14.54 | ``Erik | andrei_: leave it so both cases are in there, when the code the first one exercises gets fixed, the next will be ready to go |
| 22:16.56 | ``Erik | for the pkg_conn fields, it's better to test too much than too little.. fill in as much as you can :) |
| 22:17.34 | ``Erik | if you can figure out how to get 100% coverage (every line of code exercised, every branch tried), that'd be awesome |
| 22:18.34 | andrei_ | right, thanks :) |
| 22:30.01 | *** join/#brlcad cristina (~quassel@188.24.45.30) |
| 22:31.11 | *** join/#brlcad stas (~stas@188.24.45.30) |
| 22:35.19 | *** part/#brlcad elf_ (~elf@p22.eregie.pub.ro) |
| 22:36.15 | *** join/#brlcad elf_ (~elf@p22.eregie.pub.ro) |
| 22:40.00 | elf_ | I updated the schedule that I thought about for SOCIS, the proposed schedule for the first month can be found http://brlcad.org/wiki/User:Elf11#Proposed_Schedule as tasks will get done the project plan will get revised, the schedule will get also revised if any of the mentors have any additions |
| 23:02.33 | *** join/#brlcad cristina (~quassel@188.24.45.30) |
| 23:14.33 | *** join/#brlcad IriX64 (~kvirc@70.49.139.62) |