00:01:01  <jwolfe>aklein: i've been meaning to continue setting up a chroot environment to get on the same page as official chromium developers. i should probably put more effort into that.
00:01:52  * joyeequit (Ping timeout: 260 seconds)
00:20:24  * plutoniixjoined
00:20:33  * plutoniixquit (Max SendQ exceeded)
00:21:07  * plutoniixjoined
00:24:17  * Net147quit (Read error: Connection reset by peer)
00:28:37  * Net147joined
00:35:16  <aklein>jwolfe: https://bugs.chromium.org/p/chromium/issues/detail?id=439320 sounds like an old bug that's in the area of the kind of badness you've been running into
00:35:33  <aklein>now that you found "use_debug_fission" I'm seeing it everywhere :)
00:44:19  * bradleymeckjoined
00:52:50  * bradleymeck_joined
00:52:57  * bradleymeckquit (Ping timeout: 260 seconds)
00:52:57  * bradleymeck_changed nick to bradleymeck
00:57:55  * bradleymeckquit (Read error: Connection reset by peer)
00:58:06  * bradleymeckjoined
00:58:14  * bradleymeckquit (Client Quit)
01:17:07  * ncthom91joined
01:33:54  * ilyaigpetrovquit (Quit: Connection closed for inactivity)
01:47:30  * ncthom91quit (Quit: Textual IRC Client: www.textualapp.com)
02:00:53  * joyeejoined
02:26:08  * joyeequit (Read error: Connection reset by peer)
02:26:23  * joyeejoined
02:39:38  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
02:54:10  * unixpicklejoined
03:02:37  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
03:06:44  * joyeequit (Read error: Connection reset by peer)
03:07:14  * joyeejoined
03:25:01  * joyeequit (Read error: Connection reset by peer)
03:25:25  * joyeejoined
03:29:53  * joyee_joined
03:29:53  * joyeequit (Read error: Connection reset by peer)
04:00:52  * joyeejoined
04:01:01  * joyee_quit (Read error: Connection reset by peer)
04:21:53  * joyee_joined
04:22:19  * joyeequit (Read error: Connection reset by peer)
05:25:04  * joyee_quit (Read error: Connection reset by peer)
05:25:30  * joyeejoined
05:33:53  * BobGneujoined
06:31:58  * mylesborinsquit (Ping timeout: 240 seconds)
07:05:59  * sparrpart ("WeeChat 1.4")
07:15:27  <trungl-bot>Tree closed by [email protected]: closed - launching (take 2)
07:17:42  * rosseauxquit (Read error: Connection reset by peer)
07:18:43  * rosseauxjoined
08:52:51  * BobGneuquit (Read error: Connection reset by peer)
09:42:11  * zvquit (Ping timeout: 256 seconds)
09:48:58  * rmcilroyjoined
09:53:58  * zvjoined
10:16:43  * plutoniixquit (Quit: Leaving)
10:16:43  * joyeequit (Read error: Connection reset by peer)
10:17:06  * joyeejoined
10:41:54  * joyeequit (Read error: Connection reset by peer)
10:42:19  * joyeejoined
10:44:10  * sxajoined
11:03:06  * joyeequit (Read error: Connection reset by peer)
11:05:44  * joyeejoined
11:16:49  * joyeequit (Read error: Connection reset by peer)
11:23:30  * joyeejoined
11:34:25  * joyeequit (Read error: Connection reset by peer)
12:25:24  <trungl-bot>Tree throttled by [email protected]: throttled - it's in! Still, no risky changes please!
12:29:53  * joyeejoined
12:32:27  <trungl-bot>Tree closed by [email protected]: closed - waiting - it's in! Still, no risky changes please!
12:35:40  * joyeequit (Read error: Connection reset by peer)
12:41:58  * joyeejoined
12:45:54  * joyeequit (Read error: Connection reset by peer)
12:46:22  * joyeejoined
13:38:54  <trungl-bot>Tree throttled by [email protected]: throttled - it's in! Still, no risky changes please!
14:36:28  * joyeequit (Read error: Connection reset by peer)
14:36:58  * joyeejoined
14:45:02  * unixpicklejoined
14:52:00  * bradleymeckjoined
15:08:33  * joyeequit (Remote host closed the connection)
16:27:26  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
16:41:13  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:51:44  * rwlbuis_joined
16:53:16  * bradleymeckquit (Quit: bradleymeck)
16:59:51  * unixpicklejoined
17:00:22  * bradleymeckjoined
17:27:29  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
17:31:44  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
17:33:06  * Guest59joined
18:16:22  * bradleymeckquit (Quit: bradleymeck)
18:27:09  * bradleymeckjoined
19:49:39  <jwolfe>aklein: that's similar, but not exactly the issue i was having.
19:50:29  <jwolfe>and here's the next link in the everything-is-broken chain: setting v8_use_snapshot=false appears to do nothing. it still makes a snapshot during the build step, and the snapshot initialization code i was trying to debug doesn't run at runtime.
19:51:02  <jwolfe>i can give up on trying to debug the snapshot code, but it seems like that option's existence implies that it's supposed to work.
19:54:52  <caitp>jwolfe: it looks like if v8_use_snapshot is false, and external startup data isn't configured, it generates an "empty" snapshot
19:55:09  <caitp>which could be the build steps you're seeing?
19:57:34  <jwolfe>caitp: i put a CHECK(false) in bootstrapper.cc Genesis::InitializeGlobal(), and it was hit during the build step: ACTION //:run_mksnapshot(//build/toolchain/linux:clang_x64)
19:59:14  <caitp>I think that should still be run each time you create a context in a nosnap build, though
19:59:18  <caitp>at least that's how it used to work
20:00:08  <jwolfe>caitp: when i set a breakpoint in that function, it did not trigger at runtime. so unless something is independently broken with breakpoints in certain places in the code at certain phases of running a program, i believe that function is not running at runtime.
20:00:18  <caitp>hmm
20:00:27  <caitp>might want to look at the gn args for some of the nosnap bots
20:00:33  <caitp>I think there are some in the config list
20:00:55  <jwolfe>what is the config list?
20:02:08  <jwolfe>build/config/** doesn't have any snapshot settings that i can find.
20:02:36  <caitp>'V8 Linux - nosnap builder' generates: is_component_build = false, is_debug = false, target_cpu = "x86", use_goma = true, v8_test_isolation_mode = "prepare", v8_use_snapshot = false
20:03:09  <caitp>and, the config list is in infra/mb/mb_config.pyl
20:05:07  <jwolfe>ok, maybe it's time i learn what a component build is
20:06:15  <caitp>it's what you'd expect, use of .so/dlls
20:06:31  <caitp>rather than static linkage
20:21:39  <jwolfe>caitp: after removing target_cpu="x68" and use_goma=true, i get the same behavior as i was getting before. (i removed those two options because i don't think i can use them at all on my machine.)
20:22:13  <caitp>yeah, I know
20:22:26  <caitp>the test isolation mode shouldn't matter for you
20:22:44  <caitp>I dunno what's going on with nosnap in gn if that's happening
20:22:57  <caitp>try doing a gyp build, maybe it will work properly? otherwise maybe yang knows
20:23:20  <caitp>but again, if you need to debug something in snapshot creation, you can always just debug mksnapshot
20:23:24  <caitp>rather than d8
20:24:12  <jwolfe>right. that would be the "giving up" option, which is realistically the right way forward at this point.
20:35:46  <caitp>give up or not, I think it's worth filing a bug about the nosnap gn build
20:36:12  <caitp>best case they will explain how it's not actually broken, worst case it will get fixed
22:10:35  * bradleymeckquit (Quit: bradleymeck)
22:15:51  * bradleymeckjoined
22:24:01  * unixpicklejoined
22:48:45  * RT|Chatzillajoined
22:51:06  * joyeejoined
22:53:03  * bradleymeckquit (Quit: bradleymeck)
22:55:36  * joyeequit (Ping timeout: 240 seconds)
23:16:24  * joyeejoined
23:18:43  * joyeequit (Read error: Connection reset by peer)
23:19:14  * joyeejoined
23:27:17  * joyeequit (Remote host closed the connection)
23:30:09  * joyeejoined
23:50:10  * joyeequit (Read error: Connection reset by peer)
23:50:39  * joyeejoined