00:51:15  * hferreiroquit (Quit: Connection closed for inactivity)
01:39:38  * plutoniixquit (Quit: Leaving)
04:12:16  * plutoniixjoined
04:29:33  * BobGneujoined
07:28:00  * plutoniixquit (Ping timeout: 246 seconds)
08:26:56  * hferreirojoined
09:24:23  <trungl-bot>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "Mjsunit" on http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/9920 "V8 Linux64 GC Stress - custom snapshot" from 7c79e23c34ea971947eedc6e42d8a882617c0e47: jshin@chromium.org (:jshin))
09:34:28  <trungl-bot>Tree opened by machenbach@chromium.org: open
09:44:09  * BobGneuquit (Ping timeout: 246 seconds)
09:44:32  <trungl-bot>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "compile" on http://build.chromium.org/p/client.v8.ports/builders/V8%20Mips%20-%20builder/builds/6129 "V8 Mips - builder" from 17318bbd393f8e1b60a00d1cb1fb57befdec0874: machenbach@chromium.org,mlippautz@chromium.org)
09:50:34  <trungl-bot>Tree opened by mlippautz@google.com: open; mips compile failure -> mlippautz
10:35:52  <trungl-bot>Tree opened by mlippautz@google.com: open
12:44:07  * thefourtheye_joined
12:44:09  * thefourtheye_changed nick to thefourtheye
14:37:27  * bradleymeckjoined
15:57:49  * bobmcwquit (Read error: No route to host)
15:58:18  * bobmcwjoined
15:59:10  * bobmcwquit (Read error: No route to host)
15:59:28  * bobmcwjoined
16:02:48  * bobmcw_joined
16:02:57  * bobmcwquit (Read error: Connection reset by peer)
16:03:40  * bobmcw_quit (Read error: Connection reset by peer)
16:03:48  * bobmcwjoined
16:26:25  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
17:26:27  <caitp->it would be really cool if we could make the CallRuntime bytecode tests not fail if the Runtime::FunctionId changes
17:26:33  <caitp->that would make me so happy
17:26:50  <caitp->I mean like, as happy as something like that could make a person
17:27:23  <caitp->like, what if it stringified the function id instead
17:30:28  <caitp->it looks like we can do that for free
17:58:04  * bradleymeckquit (Quit: bradleymeck)
18:14:21  * fairfieldtquit (Quit: ...)
18:46:31  <aklein>caitp-: I agree! and I see you plan to fix this :)
18:52:19  * bradleymeckjoined
18:56:03  <aklein>caitp-: did you ever send out a CL for padStart/padEnd?
19:21:37  * bradleymeckquit (Ping timeout: 260 seconds)
19:32:33  <aklein>caitp-: ah it landed and got reverted due to gcstress, sounds suspicious, will try again
20:08:47  * bradleymeckjoined
21:21:27  <trungl-bot>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "Mjsunit" on http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/9949 "V8 Linux64 GC Stress - custom snapshot" from 07277202cf136e70c147e2f000e48964332bb01c: adamk@chromium.org (:aklein))
21:25:24  * bradleymeckquit (Read error: Connection reset by peer)
21:32:46  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
21:35:19  * Guest59joined
21:40:37  <trungl-bot>Tree opened by adamk@chromium.org (:aklein): Tree is open
21:42:52  <caitp->I'll take a look at that gcstress failure
21:43:51  <aklein>caitp-: I've reduced it to v8_embed_script = "test/mjsunit/mjsunit.js" in gn args
21:43:56  <aklein>and --gc-interval=500
21:46:30  <aklein>it looks to me like this just shouldn't be a js test
21:47:05  <aklein>pretty sure the problem is that a GC occurs between the two calls to maker_function()
21:47:54  * bradleymeckjoined
21:53:04  <aklein>Reading jkummerow's https://codereview.chromium.org/2487943005 that seems like what's happening
21:53:16  <aklein>the array gets moved to old space and so the test doesn't do anything
21:55:40  <aklein>I think this test shouldn't be run under gcstress
21:56:31  <caitp->what is it that causes it to happen when this is shipped, newspace is just filling up faster?
21:57:09  <aklein>it doesn't even seem related to size...I need to understand more of what this gc-interval flag does
21:57:30  <caitp->well it has to be something if it doesn't happen without shipping that feature
21:58:30  <aklein>ah
21:58:35  <aklein>it's just number of allocations
21:58:47  <aklein> if (FLAG_gc_interval >= 0 && !always_allocate() &&
21:58:47  <aklein> Heap::allocation_timeout_-- <= 0) {
21:58:47  <aklein> return AllocationResult::Retry(space);
21:58:47  <aklein> }
21:59:08  <aklein>so this adds allocations, and voila
22:01:07  <caitp->so bootstrapper allocates the baseline code, shared function info, function instance, and nothing else?
22:01:20  <caitp->and that difference is enough to cause another gc
22:01:36  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:02:30  * Guest59joined
22:24:37  * bradleymeckquit (Ping timeout: 248 seconds)
22:33:00  * RT|Chatzillajoined
22:41:34  * bradleymeckjoined
22:51:16  <aklein>caitp-: looks like it
22:52:32  * bradleymeckquit (Quit: bradleymeck)
23:27:07  * Net147quit (Ping timeout: 265 seconds)
23:27:52  * Net147joined