Show enters and exits. Hide enters and exits.
| 00:31:33 | evan | found a tricky inlining "bug" |
| 00:31:44 | evan | not a crash bug, just a bug that caused things to be over inlined. |
| 01:33:49 | evan | le sigh lebron. |
| 02:09:11 | jeremyevans | Anyone know what the equivalent of rbx's ARG0 is in MRI? |
| 02:15:42 | evan | jeremyevans: there isn't one. |
| 02:15:50 | evan | dumb huh. |
| 02:15:53 | evan | thats why I added it. |
| 02:16:19 | evan | $0 can sort of do it. |
| 02:16:23 | evan | but it's inaccurate. |
| 02:18:48 | jeremyevans | evan: I tried $0 first, but it didn't work :) ruby -e 'p $0' => "-e" |
| 02:18:55 | evan | yeah |
| 02:19:01 | evan | thats why it's sort of there |
| 02:19:02 | evan | but not really. |
| 02:19:51 | jeremyevans | evan: I just tried compiling the MRI C extension I'm working on with rbx. No problems. Even caught a bug that MRI missed (typo in function name). |
| 02:20:00 | evan | nice! |
| 02:20:07 | evan | whats the extension? |
| 02:20:22 | jeremyevans | it's a replacement for date.rb |
| 02:20:37 | evan | cool. |
| 02:21:07 | jeremyevans | early stages now, but over 80 times faster for Date.civil |
| 02:21:28 | evan | 80x on MRI or rbx? :) |
| 02:21:47 | jeremyevans | evan: I only benched against MRI. Let me see on rbx |
| 02:24:32 | jeremyevans | on rbx, only 6 times faster, for 2 reasons |
| 02:24:46 | jeremyevans | rbx is twice as fast for stdlib date |
| 02:25:23 | jeremyevans | rbx is six times slower than MRI when using the C extension |
| 02:25:57 | evan | ha! |
| 02:26:07 | evan | half a dozen of one, 6 of another. |
| 02:26:10 | jeremyevans | Also, for some reason, rbx Date#inspect is crazy slow (27x slower than MRI) |
| 02:26:20 | evan | hm, i should check that out. |
| 02:26:30 | evan | oh |
| 02:26:34 | evan | String#% |
| 02:26:35 | evan | thats why. |
| 02:27:14 | jeremyevans | That's not yet optimized in rubinius I guess? |
| 02:27:46 | evan | nope |
| 02:27:56 | evan | should be optimized for 1.1 |
| 02:27:58 | jeremyevans | also, was the block splat bug fixed? I forgot to enter a ticket for it. |
| 02:27:59 | evan | it's on the short list |
| 02:28:02 | evan | right after pack/unpack |
| 02:28:11 | evan | the calling #to_ary one? |
| 02:29:30 | jeremyevans | evan: The bug might be related to to_ary, I'm not sure |
| 02:29:51 | evan | could you point out which you mean? |
| 02:29:58 | evan | there are couple i need to deal with. |
| 02:30:06 | jeremyevans | Let me see if I can find it. |
| 02:36:55 | jeremyevans | evan: I've located it, but let me put a simple example together. Be back in a bit |
| 02:37:10 | evan | k |
| 02:37:11 | evan | thanks. |
| 02:51:18 | brixen | <- silly |
| 02:51:26 | brixen | 1.5 hrs of aikido in 94 F |
| 02:51:36 | brixen | definition of silly |
| 02:51:48 | brixen | I should go drink manhattans on a patio somewhere |
| 02:53:58 | jeremyevans | evan: proc{|b, *a| p [b, a]}.call([2, 3]) => [2, [3]] |
| 02:54:19 | jeremyevans | evan: in MRI, it's [[2, 3], []] |
| 02:54:24 | evan | UG |
| 02:54:28 | evan | fuck |
| 02:54:29 | evan | that |
| 02:54:30 | evan | shit. |
| 02:54:31 | evan | yes. |
| 02:54:40 | evan | .call has entirely different semantics than yielding to it |
| 02:54:41 | jeremyevans | evan: My fault for not filing a bug report last time |
| 02:54:45 | evan | if you yield to |b, *a| |
| 02:54:53 | evan | it's something else entirely. |
| 02:55:19 | evan | ok, i need dinner. |
| 02:55:20 | evan | bbiab. |
| 02:55:23 | jeremyevans | evan: Should I post a bug on gihub? |
| 02:55:33 | parndt | evan: is the code for boyscout open source? |
| 02:56:48 | brixen | jeremyevans: yes, please file an issue |
| 03:01:49 | jeremyevans | brixen: evan: Issue filed: http://github.com/evanphx/rubinius/issues/issue/398 |
| 03:05:47 | brixen | jeremyevans: awesome, thanks |
| 03:21:39 | jc00ke | hello |
| 03:21:57 | brixen | sup jc00ke |
| 03:22:05 | brixen | missed you at pdx.rb |
| 03:22:20 | jc00ke | yeah, sounded like a good one. Had a graduation party to go to... |
| 03:22:25 | brixen | ahh fun |
| 03:22:48 | jc00ke | yeah, good times. I checked out Rein's enumeration slides today |
| 03:22:51 | jc00ke | fun also |
| 03:23:27 | jc00ke | so, I'm finally getting around to running some code I had written for a client on rbx... but I get a TypeError |
| 03:23:43 | brixen | ok, got a repro? |
| 03:23:53 | brixen | or backtrace |
| 03:24:13 | jc00ke | can't share code, but I think I can share backtrace |
| 03:24:17 | jc00ke | lemme grab some |
| 03:24:40 | jc00ke | any chance it could be Rspec? |
| 03:24:51 | jc00ke | same version runs fine in ree |
| 03:24:58 | brixen | well, if you want to try to extract a simpler case, that would be great |
| 03:25:02 | brixen | rspec should run ok |
| 03:25:14 | jc00ke | k, lemme see what I can get |
| 03:25:16 | brixen | but could be an issue, sure |
| 03:43:08 | jc00ke | debugger work? |
| 03:50:11 | evan | not atm. |
| 03:50:36 | jc00ke | k |
| 03:50:51 | jc00ke | brixen, how can I get you a private URL? |
| 03:52:29 | evan | jc00ke: you can send it to me |
| 04:05:28 | brixen | jeremyevans: do you use any RSTRING_PTR or RSTRING_LEN in your C ext? |
| 04:05:53 | jeremyevans | brixen: Nope, it's all numbers currently |
| 04:05:58 | brixen | ok |
| 04:06:02 | brixen | just curious |
| 04:06:20 | brixen | let us see the code when you can so we can look at the speed difference |
| 04:06:20 | jeremyevans | brixen: I'll be using it eventually. So far only Date.civil and Date#inspect have been implemented |
| 04:06:44 | brixen | jeremyevans: well, if you are using the string read_only, use rb_str_ptr_readonly in rbx |
| 04:07:11 | jeremyevans | brixen: Do you want to see the code now? |
| 04:07:16 | brixen | sure |
| 04:07:58 | brixen | jeremyevans: actually, I'll bbiab, but feel free to post a link |
| 04:08:14 | jeremyevans | brixen: http://www.pastie.org/1037018.txt |
| 04:09:14 | brixen | sweet, bbiab... |
| 05:53:41 | dbussink | evan: morning :) |
| 05:54:12 | dbussink | evan: the weird thing with those benchmarks is that sqlite3 is a lot slower than mysql, but the code in the extension is very similar |
| 05:54:12 | dbussink | does basically the same things, except calling mysql api methods instead of sqlite3 ones |
| 05:54:15 | dbussink | and on mri the performance is very similar |
| 16:24:27 | brixen | morning |
| 16:24:40 | brixen | evan: going to galois talk this morning |
| 16:24:56 | BrianRice-work | me, too |
| 16:25:02 | brixen | BrianRice-work: woot |
| 16:25:07 | brixen | are you feeling better? |
| 16:25:09 | BrianRice-work | this one ought to be interesting |
| 16:25:12 | BrianRice-work | yeah, more or less |
| 16:25:20 | brixen | looks like it will be interesting, yes |
| 16:25:42 | evan | ok |
| 16:26:01 | BrianRice-work | http://www.galois.com/blog/2010/07/02/tech-talk-requirements-and-performance-of-data-intensive-irr egular-applications/ |
| 16:26:16 | brixen | evan: I extracted #399 from jc00ke's code last night, but I didn't investigate yet |
| 16:27:29 | brixen | BrianRice-work: did you look at Rust? |
| 16:28:43 | BrianRice-work | I've looked at it, yes. not a bad idea. better than Go in principle |
| 16:28:55 | BrianRice-work | I mean, of course, that it appeals to me much more than Go |
| 16:29:11 | brixen | the author has much the same opinion :) |
| 16:29:29 | brixen | looks like charlie's got a new post on memory profiling |
| 16:29:57 | brixen | jhat looks just like gauge, unstyled and all |
| 16:30:36 | brixen | BrianRice-work: the syntax of both Go and Rust don't resonate with me |
| 16:30:45 | brixen | I like a lot of the concepts behind Rust |
| 16:31:01 | brixen | at least, the author's explanation of tradeoffs and why one was taken |
| 16:31:06 | BrianRice-work | it's hard to escape C-lexicalisms when you get close to it |
| 16:31:36 | brixen | yes, that is quite true |
| 16:31:58 | brixen | most languages actually look surprisingly similar, at least for short snippits |
| 16:32:09 | BrianRice-work | although the type/pointer declaration syntax... |
| 16:32:13 | brixen | er snippet |
| 16:38:11 | brixen | jvoorhis: come to the galois talk this morning |
| 16:38:24 | jvoorhis | dunno that i can, i have an appointment at 11:45 |
| 16:38:26 | jvoorhis | what's the talk? |
| 16:38:48 | brixen | http://www.galois.com/blog/2010/07/02/tech-talk-requirements-and-performance-of-data-intensive-irr egular-applications/ |
| 16:39:03 | brixen | could be quite relevant to y'all |
| 16:39:05 | jvoorhis | oh, that one sounded great |
| 16:39:12 | brixen | yeah, so reschedule :P |
| 16:39:30 | jvoorhis | ha |
| 16:39:34 | brixen | hehe |
| 16:39:44 | jvoorhis | no 24 notice |
| 16:39:51 | brixen | argh |
| 16:39:55 | jvoorhis | it starts at 1030? |
| 16:39:59 | brixen | yeah |
| 16:40:08 | jvoorhis | maybe i could leave early |
| 16:40:57 | brixen | sure |
| 16:41:39 | brixen | you know what would be cool: when I put a calendar item in my iphone, if I could link a pdxbus update so the reminder tells me how many min till the next arrival of the bus I'll take |
| 16:41:47 | brixen | any iphone hackers here? :) |
| 16:42:49 | jvoorhis | learning objc isn't so hard |
| 16:43:05 | BrianRice-work | brixen, been a while but yes |
| 16:43:32 | brixen | well, I don't know if there's an api for the calendar like that, but there should be |
| 16:43:33 | BrianRice-work | brixen, yeah you just have to form a custom URL that the application responds/launches-for |
| 16:43:52 | brixen | but I want it to display right in the reminder pop-up |
| 16:43:55 | brixen | is that possible? |
| 16:43:57 | BrianRice-work | iOS 4: http://stackoverflow.com/questions/246249/programmatically-add-custom-event-in-the-iphone-calendar |
| 16:44:06 | BrianRice-work | oh. not really. |
| 16:44:13 | brixen | :( |
| 16:44:43 | BrianRice-work | that would be a turing-complete hook into the notification system... not kosher from the security regime perspective |
| 17:05:51 | evan | dbussink: poke |
| 17:21:01 | boyscout | Introduce deoptimization on too many uncommon branches - 8969894 - Evan Phoenix |
| 17:47:31 | boyscout | CI: Commit 8969894 failed. http://github.com/evanphx/rubinius/commit/896989442781c131618d957f78b614623698479d |
| 18:54:25 | brixen | hrm |
| 18:54:39 | evan | ? |
| 18:54:55 | brixen | wondering about that spec failure |
| 18:55:04 | evan | i'm going to look at it shortly. |
| 18:55:05 | brixen | I actually get 5 on my ubuntu box |
| 18:55:11 | evan | ug. |
| 19:14:23 | evan | brixen: i'm going to get some lunch and a haircut |
| 19:14:24 | evan | i'll bbiab. |
| 19:16:39 | brixen | ok |
| 19:24:56 | dbussink | evan: auch |
| 19:28:45 | dbussink | hmm, guess 10 minutes for a lunch and haircut is a bit short :p |
| 19:30:40 | brixen | dbussink: are you getting excited for the game? |
| 19:31:01 | dbussink | brixen: now that it's weekend the tension buildup has started :P |
| 19:31:20 | brixen | heh |
| 19:31:21 | brixen | dbussink: http://www.statesmanjournal.com/article/20100709/SPORTS/7090351/1018 |
| 19:31:54 | dbussink | brixen: ah, cool :) |
| 19:32:07 | dbussink | already noticed in new york that it's a lot bigger in the usa than i expected it to be |
| 19:32:09 | brixen | we might catch it there |
| 19:32:28 | brixen | there are pockets of hard core fans :) |
| 19:32:29 | dbussink | probably going to watch it at a friends place |
| 19:32:46 | dbussink | with a bbq before, it's 30+ celcius here now |
| 19:33:12 | brixen | nice |
| 19:33:18 | brixen | it's about that here too |
| 19:33:29 | dbussink | bit too hot for me |
| 19:33:31 | brixen | should get up to about 34 C today |
| 19:33:46 | dbussink | we don't have airco's in each house here either :P |
| 19:33:52 | brixen | 25 C is nice for me |
| 19:33:52 | dbussink | so it can be pretty warm at night then |
| 19:34:00 | brixen | no aircon here either |
| 19:34:01 | dbussink | yeah, 25 is nice |
| 19:34:26 | BrianRice-work | houses in the northwest aren't built to shed heat |
| 19:34:46 | dbussink | well, if they are properly insulated, they can keep heat out too |
| 19:35:21 | BrianRice-work | as long as the albedo is low :) |
| 19:35:34 | brixen | BrianRice-work: our apt is in the cross-section of an H shaped building, so it gets great cross ventilation if we keep the door open :) |
| 19:36:16 | BrianRice-work | nice. I have two doors I can open. the only downside is that the upper floor's doors have no bug screening |
| 19:36:30 | brixen | ah yeah, that sucks |
| 19:38:51 | dbussink | i've grown up with country side levels of bugs, so it's a lot better in the city :P |
| 20:40:43 | pcapriotti | any particular reason rb_throw is not implemented in the C API? |
| 20:43:31 | dbussink | pcapriotti: not that i know of, does it have any special semantics? |
| 20:47:03 | pcapriotti | dbussink: I don't know, actually, I just noticed that it's missing while trying to compile QtRuby |
| 20:51:57 | dbussink | pcapriotti: from what i can see it should be pretty simple to add |
| 20:53:43 | pcapriotti | dbussink: I'm pretty new to rubinius, but I'd like to try. Can you give me some pointers? |
| 20:54:27 | dbussink | pcapriotti: well, you probably want to call into the ruby throw parts |
| 20:54:42 | dbussink | pcapriotti: there are a bunch of other things in vm/capi that do that too |
| 20:55:07 | dbussink | pcapriotti: best is to start of with adding a spec for this under spec/ruby/optional/capi |
| 20:55:37 | dbussink | since throw is on Kernel you should probably add it to kernel_spec |
| 20:55:43 | pcapriotti | ok, thanks |
| 21:06:50 | evan | you must call back into ruby to implement rb_throw |
| 21:07:50 | dbussink | pcapriotti: look at other stuff that usually uses rb_funcall in vm/capi to call into ruby |
| 21:07:54 | dbussink | evan: you rang sir? |
| 21:08:00 | evan | yeah |
| 21:08:04 | evan | with your benchmark |
| 21:08:08 | evan | on my machine |
| 21:08:20 | evan | the benchmark that fills a table with rows |
| 21:08:25 | dbussink | yeah |
| 21:08:26 | evan | seems to end up being entirely an IO benchmark |
| 21:08:37 | evan | MRI takes 26s wall clock |
| 21:08:39 | evan | and 7s user |
| 21:08:48 | dbussink | ah ok, well, what i find weird is the big discrepancies between the different drivers |
| 21:08:55 | evan | thats the drivers |
| 21:09:00 | evan | not rbx vs mri |
| 21:09:02 | evan | yes? |
| 21:09:21 | dbussink | well, i don't see that discrepancy running with mri, but if the benchmark numbers are wrong that could be it then yeah |
| 21:09:32 | evan | here |
| 21:09:40 | evan | rbx is about the same as MRI for sqlite |
| 21:09:44 | dbussink | let me wrap it with a time call |
| 21:10:22 | dbussink | looks like the numbers it prints are pretty off with mri |
| 21:10:41 | evan | thats because of the IO |
| 21:10:47 | evan | I believe |
| 21:10:54 | evan | I need to fix rbx's Process.times |
| 21:11:05 | evan | to actually report the same times as MRI |
| 21:11:11 | evan | ie, seperate user, etc. |
| 21:12:55 | dbussink | evan: these are my numbers if i wrap them with a time |
| 21:12:57 | dbussink | https://gist.github.com/688db0ac6eb42dbc0b93 |
| 21:13:02 | dbussink | so the different isn't that big there |
| 21:15:11 | evan | it's the numbers in the real column that you want to look at |
| 21:15:28 | pcapriotti | I wrote a simple spec for rb_throw, and was expecting it to fail compiling, instead it gives a linker error "undefined symbol rb_throw". Is it picking up the MRI ruby.h, maybe? |
| 21:15:30 | evan | time is useless for this |
| 21:15:34 | evan | because you're seeing code loading too. |
| 21:15:51 | evan | pcapriotti: thats C. |
| 21:16:06 | evan | you can call a function that has no definition |
| 21:16:19 | pcapriotti | evan: ah, right, makes sense |
| 21:16:20 | evan | you don't get a compile error because it's linked as a dynamic library |
| 21:16:30 | dbussink | evan: true yeah, but the numbers are less skewed than what benchmark reports |
| 21:16:51 | dbussink | pcapriotti: you want to start of with running the specs against mri |
| 21:17:07 | dbussink | pcapriotti: you can do ./bin/mspec -tr spec/ruby/optional/kernel_spec.rb |
| 21:17:14 | dbussink | -t selects the ruby to run against |
| 21:17:23 | dbussink | mspec in the rbx repo uses rbx by default |
| 21:17:27 | dbussink | r selects mri |
| 21:17:58 | pcapriotti | dbussink: ok, cool, it works |
| 21:18:20 | dbussink | pcapriotti: ok, then is a good step to add it to rbx too :) |
| 21:18:57 | pcapriotti | dbussink: having a failing spec is ok? |
| 21:19:08 | dbussink | pcapriotti: it shouldn't fail on mri :) |
| 21:19:14 | dbussink | because it should follow how mri behaves |
| 21:19:54 | pcapriotti | dbussink: yeah, but it fails on rubinius |
| 21:20:11 | dbussink | pcapriotti: even after you add it to capi? |
| 21:20:28 | dbussink | pcapriotti: because if you haven't added it yet, it should fail because it isn't there yet :) |
| 21:21:38 | pcapriotti | dbussink: yeah, I'm just wondering if you want the failing spec to be committed before the thing being tested is implemented |
| 21:21:54 | dbussink | pcapriotti: well, we prefer separete spec commits and implementation commits |
| 21:21:57 | pcapriotti | this particular one might be trivial, but I was wondering in general, if that's how you roll :) |
| 21:22:05 | dbussink | that makes merging specs back to rubyspec way easier |
| 21:22:13 | dbussink | so always as separate commits |
| 21:22:13 | brixen | pcapriotti: please read doc/specs.txt |
| 21:22:25 | pcapriotti | ok, will do |
| 21:41:00 | dbussink | pcapriotti: thing is that we don't require each commit in itself to always maintain a clean ci run, other things are more important |
| 21:41:38 | brixen | yes, just the tip of what you push must run without errors in CI |
| 21:41:45 | pcapriotti | ok |
| 21:42:05 | evan | brixen: i'm working on the CI failure |
| 21:42:06 | brixen | so you can commit the specs, then commit the impl, then create a patch/push |
| 21:42:10 | brixen | evan: ok |
| 21:42:18 | evan | 1006 means that the subprocess exited because of a signal |
| 21:42:26 | evan | in this case, signal 6 which is abort |
| 21:42:28 | evan | which means it crashed |
| 21:42:31 | evan | i'm on it. |
| 21:42:33 | brixen | ok |
| 21:42:49 | evan | the > 1000 status is an rbx specific feature |
| 21:42:55 | evan | to detect things exactly like this. |
| 21:43:05 | brixen | ah nice, didn't realize that |
| 21:43:55 | dbussink | evan: i have a reproduceable crash here too, it segfaults in syck_mark_parser |
| 21:44:09 | evan | ok |
| 21:44:12 | evan | please gist the steps. |
| 21:44:25 | evan | probably my capi changes yesterday |
| 21:44:25 | dbussink | evan: will do |
| 21:44:25 | evan | ug. |
| 21:50:11 | dbussink | evan: this is what i run to get it: https://gist.github.com/7010094f6267ba278d37 |
| 21:50:51 | evan | um |
| 21:50:58 | evan | wtf is that warning about cross compiling for jruby? |
| 21:51:03 | evan | you sure it's not compiling wrong? |
| 21:51:18 | dbussink | that's rake-compiler |
| 21:51:22 | pcapriotti | should I create a ticket to submit the patch? |
| 21:51:31 | dbussink | evan: i know it's compiling it right |
| 21:51:41 | evan | can you minimize this? |
| 21:51:51 | evan | do I need to be recompiling all this everytime? |
| 21:52:15 | dbussink | evan: the weird thing is, that if i just run that last command listed there, it doesn's segfault :S |
| 21:52:42 | evan | :/ |
| 21:53:12 | brixen | pcapriotti: yes, please |
| 22:07:41 | evan | brixen: ok, the crash is cleaning up some FFI memory |
| 22:07:45 | evan | i'm working on it now. |
| 22:09:38 | brixen | cool |
| 22:16:17 | pcapriotti | when building an extension for rubinius, is there an equivalent of libruby.so I can link to, or should I leave ruby symbols undefined? |
| 22:16:27 | evan | no, there is not. |
| 22:16:33 | evan | you leave them hanging |
| 22:16:45 | evan | why are you doing it by hand? |
| 22:16:57 | pcapriotti | I'm using the existing build system of QtRuby |
| 22:17:04 | evan | ah |
| 22:17:10 | evan | no, no -lruby |
| 22:17:32 | pcapriotti | ok, I have to remove the no-undefined flag, then |
| 22:21:29 | brixen | pcapriotti: was rb_throw the only C-API function missing for QtRuby? |
| 22:21:59 | pcapriotti | brixen: no, there's rb_during_gc |
| 22:22:08 | brixen | :/ |
| 22:22:17 | pcapriotti | brixen: I'm trying to figure out why they need that, it seems a dirty hack |
| 22:23:01 | brixen | anything /rb.*gc/ is a dirty hack :) |
| 22:23:32 | pcapriotti | it seems it avoids to call an overriden method during GC and calls the original C++ method instead... looks like a potential source of crazy heisenbugs |
| 22:23:50 | pcapriotti | I'll just take it off for now :) |
| 22:23:59 | brixen | heh |
| 22:24:16 | evan | during_gc? |
| 22:24:23 | evan | is that a flag? |
| 22:24:25 | evan | must be. |
| 22:34:33 | pcapriotti | it works! :D |
| 22:35:15 | brixen | pcapriotti: woot! |
| 22:35:26 | brixen | pcapriotti: what platform are you on? |
| 22:35:31 | pcapriotti | linux |
| 22:35:35 | brixen | which? |
| 22:35:39 | pcapriotti | kubuntu |
| 22:35:43 | brixen | sweet |
| 22:35:52 | pcapriotti | ok, let me try my app now :) |
| 22:36:25 | brixen | pcapriotti: you'll go down in the pages of history as the first Qt app running on rbx |
| 22:36:41 | pcapriotti | eheh |
| 22:56:34 | pcapriotti | ok, I stumbled upon another difference: it seems rb_class2name in MRI works for Modules, too, while in rbx it expects a Class |
| 22:57:06 | brixen | pcapriotti: could you add a c-api spec for it? |
| 22:57:12 | pcapriotti | brixen: sure |
| 22:57:16 | brixen | sweet, thanks |
| 23:00:13 | pcapriotti | brixen: should I keep the one for Class? |
| 23:00:49 | brixen | ? |
| 23:01:02 | brixen | you mean the existing spec? |
| 23:01:05 | pcapriotti | there is already a spec in class_spec.rb for class2name |
| 23:01:12 | brixen | yeah |
| 23:01:14 | pcapriotti | should I move it to module_spec or keep both? |
| 23:01:22 | brixen | add one for passing a module |
| 23:01:26 | pcapriotti | ok |
| 23:22:28 | evan | brixen: it's a bug in libffi! |
| 23:22:31 | evan | *eyeroll* |
| 23:23:25 | brixen | ahhhh :( |
| 23:24:32 | evan | this line |
| 23:24:32 | evan | if (strncmp (p + 1, "selinuxfs ", 10) != 0) |
| 23:24:34 | evan | should be |
| 23:24:45 | evan | if (strncmp (p + 1, "selinuxfs ", 10) == 0) |
| 23:24:54 | evan | clearly whoever wrote this never ran it. |
| 23:25:06 | brixen | the value of tests |
| 23:25:44 | evan | i'd at least take "I ran the code once" |
| 23:25:50 | evan | the bug is masked |
| 23:25:59 | evan | because the selinux code sort of works |
| 23:26:02 | evan | but it's not fork friendly. |
| 23:30:50 | boyscout | Cleanup and improve NativeMethod a bit - a2fe4b0 - Evan Phoenix |
| 23:30:50 | boyscout | Fix classic strncmp bug in libffi - 74c1dce - Evan Phoenix |
| 23:45:31 | pcapriotti | uhm... there are some nasty crashes in qtruby |
| 23:45:40 | pcapriotti | it's going to be fun to track them down :) |
| 23:46:11 | brixen | gdb is your friend :) |
| 23:47:08 | pcapriotti | yep, but now it's too late here for debugging :) |
| 23:47:19 | pcapriotti | I'm happy to have hello world running for now |
| 23:47:55 | brixen | well, thanks for working on it! |
| 23:49:31 | pcapriotti | np, hope to see my patches integrated, so I can commit the changes in qtruby and have it running on rbx for the next release |
| 23:49:48 | brixen | yep, we'll get them in shortly |
| 23:55:46 | toulmean | brixen, evan : vanity now conforms with 1.8.7 if you want to do some perf work, it looks like a good target. |
| 23:56:10 | evan | ah cool! |
| 23:56:39 | boyscout | CI: rubinius: 74c1dce successful: 3458 files, 13692 examples, 41271 expectations, 0 failures, 0 errors |
| 23:56:42 | toulmean | I'll do a new pass with -Xprofile and will paste results for you |
| 23:57:10 | toulmean | is there a way with rvm to install the master branch of rubinius ? |
| 23:57:19 | brixen | rvm install rbx-head |
| 23:57:28 | toulmean | thanks. That's very useful. |
| 23:57:32 | brixen | n/p |
| 23:57:40 | toulmean | I'll use rvm with head and will run a profiling for you guys. |
| 23:57:47 | brixen | sweet, thanks |
| 23:58:44 | evan | yay CI is fixed. |
| 23:58:52 | evan | i sent a patch to libffi also. |
| 23:59:02 | brixen | excellent |