00:11:31  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
00:14:58  * jugglinmikequit (Ping timeout: 252 seconds)
00:22:35  * plutoniixjoined
00:24:07  * plutoniixquit (Client Quit)
00:30:29  * plutoniixjoined
02:02:45  * plutoniixquit (Quit: จรลี จรลา)
02:26:11  * unixpicklejoined
02:26:33  * unixpicklequit (Client Quit)
02:59:19  * unixpicklejoined
03:06:11  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
04:46:51  * plutoniixjoined
04:50:06  * plutoniixquit (Client Quit)
05:07:59  * plutoniixjoined
05:26:23  <trungl-bot>Tree closed by [email protected]: Tree is closed (Automatic: "compile" on http://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064%20-%20ignition/builds/777 "V8-Blink Linux 64 - ignition" from d5f2ac5e3326f281cbe7ba57464a4b17a9938e37: [email protected])
06:28:07  <trungl-bot>Tree opened by [email protected]: open
07:45:58  <trungl-bot>Tree closed by [email protected]: closed - maintenance
07:46:58  <trungl-bot>Tree closed by [email protected]: closed - fixing
07:56:06  * BobGneujoined
08:00:08  * bradleymeckjoined
08:29:19  * kenansulaymanquit (Read error: Connection reset by peer)
08:36:34  * saperquit (Ping timeout: 252 seconds)
08:37:07  * luite_quit (Ping timeout: 252 seconds)
08:37:07  * aperezdcquit (Ping timeout: 252 seconds)
08:44:16  <trungl-bot>Tree opened by [email protected]: open
08:44:17  * saper_joined
08:44:17  * clinthquit (Ping timeout: 244 seconds)
08:44:20  * aperezdc_joined
08:44:21  * AKPWDquit (Ping timeout: 244 seconds)
08:44:22  * luitejoined
08:44:22  * clinthjoined
08:44:27  * aperezdc_changed nick to aperezdc__
08:44:27  * gsathyaquit (Ping timeout: 272 seconds)
08:44:28  * BobGneuquit (Ping timeout: 276 seconds)
08:44:30  * Bob_Gneujoined
08:44:31  * Net147quit (Ping timeout: 244 seconds)
08:44:31  * AKPWDjoined
08:44:33  * aperezdc__changed nick to aperez
08:45:52  * aperezchanged nick to aperezdc
08:46:03  * Net147joined
08:46:47  * jochen__quit (Ping timeout: 258 seconds)
08:49:34  * jochen__joined
09:08:44  * gsathyajoined
09:30:05  <trungl-bot>Tree closed by [email protected]: Tree is closed (Automatic: "gclient runhooks" on http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20-%20internal%20snapshot/builds/5298 "V8 Linux64 - internal snapshot" from c534bd41a028d7dd8d79e932b619433ce9e82d10: [email protected])
09:51:21  * davijoined
10:16:38  <trungl-bot>Tree opened by [email protected]: open
10:27:31  * daviquit (Ping timeout: 250 seconds)
11:32:38  * kenansulaymanjoined
11:33:01  * kenansulaymanchanged nick to Guest34545
11:40:00  * Guest34545quit (Quit: ZNC - http://znc.in)
11:42:26  * bradleymeckquit (Quit: bradleymeck)
11:52:18  * plutoniixquit (Quit: จรลี จรลา)
12:17:07  * kenansulaymanjoined
12:17:30  * kenansulaymanchanged nick to Guest14030
12:19:06  * Guest14030quit (Changing host)
12:19:06  * Guest14030joined
13:00:11  * bobmcwjoined
13:22:01  * bradleymeckjoined
13:33:19  * bradleymeckquit (Quit: bradleymeck)
13:37:58  * bradleymeckjoined
13:44:12  * jugglinmikejoined
13:54:15  * seventhjoined
13:55:42  * ncthom91joined
14:04:23  * unixpicklejoined
14:06:03  * seventhquit (Ping timeout: 240 seconds)
14:12:43  * bradleymeckquit (Quit: bradleymeck)
14:16:30  * seventhjoined
14:44:30  * davijoined
15:56:39  * seventhquit (Ping timeout: 250 seconds)
15:59:46  * bradleymeckjoined
16:02:52  * ncthom91quit (Quit: Textual IRC Client: www.textualapp.com)
16:16:37  * bradleymeckquit (Quit: bradleymeck)
16:19:41  * RT|Chatzillaquit (Read error: Connection reset by peer)
16:25:37  <jwolfe>is anyone else frustrated by how bots can revert your CL after it gets landed and closed? i mean i get that we need more bots than just the pre-land checks, but can't we at least leave the CL open until all the bots with the power to revert the CL have given it their stamp of approval? that would save the pain of making re-land CL's.
16:26:51  <jwolfe>the background is that 2/2 of my CL's have been reverted by post-land bots, and neither issue was my fault, and both times, the CL was approved by a reviewer.
16:27:40  <jwolfe>it just seems that re-land CL's are a worse idea than leaving the original CL open or even re-opening the original CL and appending a new patches or whatever.
16:39:54  * daviquit (Ping timeout: 246 seconds)
17:25:18  <caitp>jwolfe: you've probably seen in bugmail that the land <revert> reland <revert> re-reland pattern is fairly common in the chromium projects
17:26:00  <caitp>really it's just stress testing for the bignum library used to parse CL ids
17:52:51  <jwolfe>caitp, lol. but is that a "no" then? is there some reason why CL's can't be reopened? or is there some reason a CL doesn't wait 24h after being landed to close? has this idea even been considered before?
17:53:56  <caitp>they can be reopneed
17:54:37  <caitp>you can just uncheck "closed" in the "edit issue" dialogue, and it will be opened again
17:55:12  <jwolfe>then why does anyone make re-land CLs?
17:56:29  <caitp>well for one thing, it makes the intent clear
17:56:48  <caitp>if they didn't, they might end up with 40 patchsets in the CL which gets hard to deal with
17:57:11  <caitp>so a reland CL might have the original landed CL, and then a second patchset with changes that were needed (if any)
17:57:33  <caitp>but just having "re-land" in the changeset is nice because it communicates what really happened
17:58:55  <jwolfe>so people use re-land CL's because they prefer to? not because there's a technical reason, like it makes reports and graphs nicer or something?
17:59:56  <caitp>I don't think there is a technical reason, just an aesthetic / functional reason
18:00:03  <caitp>easier on the eyes and brain
18:02:05  <jwolfe>well that sounds subjective :) . so does that mean i can reopen this CL? https://codereview.chromium.org/2048703002 i'm literally not going to change anything about the code before trying to re-land it.
18:03:16  <caitp>in a case like that, I'd personally be fine with not opening a new CL
18:03:56  <caitp>you could re-open it and ping people about relanding it, edit the description to reflect relanding if you want to
18:04:01  <caitp>if they suggest opening a new CL for it, then you should though
18:05:45  <jwolfe>it sounds like i should re-open it even if just to fish for people with an objective reason for creating re-land CL's. :)
18:19:25  * seventhjoined
19:25:59  * rhalffjoined
19:29:08  * seventhquit (Quit: ...)
19:44:49  * saper_changed nick to saper
20:02:28  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
20:04:34  * unixpicklejoined
20:17:07  * jwolfequit (Quit: Leaving)
20:18:03  * jwolfejoined
20:19:53  * jwolfequit (Client Quit)
20:20:13  * jwolfejoined
20:29:55  * bradleymeckjoined
20:54:39  * Bob_Gneuquit (Remote host closed the connection)
20:55:25  * BobGneujoined
20:59:53  * bobmcwquit (Remote host closed the connection)
21:33:22  <trungl-bot>Tree closed by [email protected]: Tree is closed (Automatic: "compile" on http://build.chromium.org/p/client.v8.fyi/builders/Chromium%20ASAN%20%28symbolized%29/builds/863 "Chromium ASAN (symbolized)" from c781e83194031b337f8eafb42588a2e3d7440782: [email protected] (:aklein),[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],machenb
22:34:07  * bradleymeckquit (Quit: bradleymeck)
22:44:15  * RT|Chatzillajoined
23:03:16  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:16:46  * unixpicklejoined