|
00:13
mtj_ joined
|
|||
| samcv | releasable6: status | 01:24 | |
| releasable6 | samcv, Next release in 4 days and ≈17 hours. Blockers: github.com/rakudo/rakudo/issues?q=...%9A%A0%22. Changelog for this release was not started yet | ||
| samcv, Details: gist.github.com/f921fe36733106bd17...a906b5f760 | |||
|
01:51
nativecallable6 joined
02:57
ilbot3 joined
06:13
releasable6 joined
07:05
brrt joined
|
|||
| brrt | good * #moarvm | 07:07 | |
| nwc10 | jnthn++ # cf523c89c06a0f480ec43a8adbc54d0ff453ebee | 07:34 | |
| samcv | good * br | 07:52 | |
|
08:15
brrt joined
08:51
zakharyas joined
09:36
reportable6 joined
10:39
zakharyas joined
11:03
brrt joined
11:05
brrt joined
11:23
zakharyas joined
11:33
brrt joined
11:49
zakharyas joined
12:05
zakharyas joined
12:24
notable6 joined
|
|||
| timotimo | i just checked and it looks like travis machines have 2 cores actually | 12:45 | |
| we should be running our travis jobs with at least -j2 on the makefile | |||
| Geth | MoarVM: c512dce8e9 | (Timo Paulssen)++ | .travis.yml travis: use 2 cores for compilation and tests it looks like travis virtual machines usually have 2 cores available. |
12:48 | |
| timotimo | let's see how that helps | ||
|
13:02
travis-ci joined
|
|||
| travis-ci | MoarVM build failed. Timo Paulssen 'travis: use 2 cores for compilation and tests | 13:02 | |
| travis-ci.org/MoarVM/MoarVM/builds/340930988 github.com/MoarVM/MoarVM/compare/a...12dce8e91c | |||
|
13:02
travis-ci left
13:28
lizmat joined
|
|||
| dogbert2 | jnthn: there's at least one GC related bug left in case you're interested: github.com/MoarVM/MoarVM/issues/620 | 13:39 | |
| timotimo | oh, haha | ||
| the semaphore test case doesn't work if there's not enough cores i guess | 13:40 | ||
| it doesn't even seem to save that much time | |||
| Geth | MoarVM: 1c79ca35d4 | (Timo Paulssen)++ | .travis.yml set test jobs back to 1 the semaphore test in nqp seems to flap if only two cores are available but one of the cores is busy running other test files |
13:42 | |
| jnthn | huh, that's odd | 13:44 | |
| dogbert2 | ? | ||
| jnthn | I'd expect the semaphore test to work reliably | 13:45 | |
| timotimo | then perhaps that failure is actually legitimate? | ||
| jnthn | Probably | 13:46 | |
|
13:51
AlexDaniel joined
13:57
travis-ci joined
|
|||
| travis-ci | MoarVM build passed. Timo Paulssen 'set test jobs back to 1 | 13:57 | |
| travis-ci.org/MoarVM/MoarVM/builds/340951714 github.com/MoarVM/MoarVM/compare/c...79ca35d448 | |||
|
13:57
travis-ci left
14:00
zakharyas joined
14:20
bloatable6 joined
14:26
evalable6 joined,
quotable6 joined,
coverable6 joined,
notable6 joined,
bloatable6 joined,
nativecallable6 joined,
releasable6 joined,
reportable6 joined,
committable6 joined,
bisectable6 joined,
shareable6 joined
14:27
benchable6 joined,
statisfiable6 joined
14:59
coverable6 joined,
notable6 joined,
reportable6 joined,
nativecallable6 joined,
committable6 joined,
quotable6 joined,
bisectable6 joined,
releasable6 joined,
bloatable6 joined,
shareable6 joined
15:04
benchable6 joined,
statisfiable6 joined
15:16
evalable6 joined
15:18
greppable6 joined
15:26
unicodable6 joined
|
|||
| brrt | i have ehm, debugged the bug a bit further | 15:27 | |
| the JIT appears to stuff a small number into where the GC thinks it should find an object | 15:28 | ||
| dogbert2 | that doesn't sound very good does it ? | 15:35 | |
| jnthn | Matches the stack traces pretty well | ||
| timotimo | that'd often be a frame, right? because they don't actually have their header? | 15:41 | |
| jnthn | More likely just some junk | 15:42 | |
|
15:44
zakharyas joined
|
|||
| dogbert2 | should Proc.kill return any file descriptors to the system or is that up to the GC? | 15:54 | |
|
15:56
brrt joined
|
|||
| dogbert2 | I meant Proc::Async.kill ofc | 15:57 | |
| brrt is back online | 15:58 | ||
| i wonder if there is a way in which a frame can be allocated, which does not respect the spesh_cand jitcodes' frame size | 16:00 | ||
| or, if i'm not computing that correctly | |||
| so this makes spilling quite suspicious | 16:04 | ||
| but, this frame, that's different from the one where the jit bisect script points us to | 16:10 | ||
| :-( | |||
|
16:25
zakharyas joined
16:28
zakharyas1 joined
16:50
zakharyas joined
17:13
Kaiepi joined
17:21
Kaiepi joined
17:45
Geth joined
18:25
bisectable6 joined,
lizmat joined
20:01
brrt joined
|
|||
| brrt | correction, after MVM_SPESH_BLOCKING it isn't | 20:04 | |
|
21:37
brrt joined
|
|||
| Kaiepi | thank you so much github.com/MoarVM/MoarVM/pull/801/files#diff-0 | 22:14 | |
| this has been driving me insuts for weeks | |||
| timotimo | oh whoops :) | 22:55 | |
| Kaiepi | stack overflows | 22:58 | |
| not... insut? what | |||
| oh nuts | 22:59 | ||
| geekosaur was trying to figure out what keyboard layout would lead to that keysmash | |||
| Kaiepi | casual qwerty | 23:00 | |
| unless you couunt tipsy as a keyboard | |||
| jnthn | .tell brrt Don't suppose a data breakpoint on the thing we're overwriting could help at al? | 23:09 | |
| yoleaux | jnthn: I'll pass your message to brrt. | ||
| MasterDuke | is this the sort of thing rr would be useful for? | 23:14 | |
| jnthn | Perhaps, yes | 23:18 | |
| Especially if it does reverse data breakpoints | 23:19 | ||
| (I suspect it does) | |||
|
23:23
lizmat joined
|
|||
| Kaiepi | ok | 23:26 | |
| the callbacks are happening after its been faced to the c part | 23:27 | ||
| *crashing | |||
| jnthn | Hm, it makes it back into MoarVM? | 23:33 | |
| Kaiepi | yep | 23:46 | |
| gimme a second i'll get some more detail out of it | 23:48 | ||
| shit i forgot to compile moar with telemetry | 23:49 | ||
|
23:59
greppable6 joined
|
|||