00:05:37  * evanlucasjoined
00:12:30  * evanlucasquit (Remote host closed the connection)
00:21:03  * evanlucasjoined
00:43:29  * stefanmbquit (Quit: Textual IRC Client: www.textualapp.com)
02:02:14  * node-ghjoined
02:02:15  * node-ghpart
03:34:09  <jbergstroem>this stuff looks pretty good! https://github.com/jenkins-contrib-themes/jenkins-neo-theme
03:34:27  <jbergstroem>someone (halp plez) should fork that and slap some nodejs green on top :)
04:10:55  <Trott>jbergstroem: Change @color-primary in less/variables.less from #0172BA to #026E00. (There may be a more standard way to override variables in less. Or maybe not.)
04:15:17  * rmgquit (Remote host closed the connection)
04:15:51  * rmgjoined
04:20:59  * rmgquit (Ping timeout: 276 seconds)
05:53:29  * node-ghjoined
05:53:30  * node-ghpart
06:26:24  <jbergstroem>joaocgreis/Trott: I'm going to add RUN_TIMES to the output of the stress tester. Bugging me not seeing it as part of console. Cool?
06:26:36  <jbergstroem>(If uncool I'll remove it I guess :)
07:57:39  * starefossen_joined
07:58:19  * orangemochaquit (Ping timeout: 276 seconds)
07:58:19  * starefossenquit (Ping timeout: 276 seconds)
07:58:19  * Trottquit (Ping timeout: 276 seconds)
07:58:44  * starefossen_changed nick to starefossen
08:06:46  * orangemochajoined
08:07:32  * Trottjoined
08:08:03  * node-ghjoined
08:08:04  * node-ghpart
09:02:16  <sgimeno>jbergstroem, I've been using https://github.com/jenkins-contrib-themes/jenkins-material-theme for and I like it
09:02:30  * node-ghjoined
09:02:30  * node-ghpart
09:02:35  <jbergstroem>sgimeno: yeah i saw that too. the one i linked is built on top and felt slighly more generic/customisable
09:02:58  <sgimeno>(y)
09:03:19  <sgimeno>will look into it then
09:08:26  * node-ghjoined
09:08:26  * node-ghpart
09:14:59  * targosjoined
10:30:58  * thealphanerdquit (Quit: farewell for now)
10:31:28  * thealphanerdjoined
11:18:26  * node-ghjoined
11:18:27  * node-ghpart
13:19:28  * rmgjoined
13:24:34  * rmgquit (Ping timeout: 260 seconds)
13:51:35  * chorrelljoined
14:04:31  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
14:05:42  * stefanmbjoined
14:10:45  * Fishrock123joined
14:24:48  * chorrelljoined
14:49:06  * node-ghjoined
14:49:07  * node-ghpart
15:04:56  * evanlucasquit (Remote host closed the connection)
15:30:01  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
15:43:31  <joaocgreis>jbergstroem: cool, looks good
16:00:59  * rmgjoined
16:47:22  * Fishrock123quit (Remote host closed the connection)
17:31:34  * chorrelljoined
17:34:14  * zkatquit (Ping timeout: 260 seconds)
17:35:24  * Trottquit (Ping timeout: 260 seconds)
17:35:24  * orangemochaquit (Ping timeout: 260 seconds)
17:35:25  * bretquit (Ping timeout: 260 seconds)
17:37:20  * othiym23quit (Read error: Connection reset by peer)
17:37:57  * Trottjoined
17:39:06  * zkatjoined
17:39:10  * bretjoined
17:39:59  * othiym23joined
17:41:01  * orangemochajoined
17:44:22  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
18:29:39  * Fishrock123joined
18:36:05  * node-ghjoined
18:36:06  * node-ghpart
19:00:15  * node-ghjoined
19:00:15  * node-ghpart
19:10:37  * stefanmbquit (Quit: My Mac has gone to sleep. ZZZzzz…)
19:21:01  * node-ghjoined
19:21:02  * node-ghpart
19:22:31  * node-ghjoined
19:22:32  * node-ghpart
19:39:08  * chorrelljoined
19:42:21  * thealphanerdquit (*.net *.split)
19:42:24  * rmgquit (*.net *.split)
19:45:07  * chorrellquit (Ping timeout: 251 seconds)
19:47:32  * stefanmbjoined
19:51:22  * thealphanerdjoined
19:51:24  * rmgjoined
19:54:20  * chorrelljoined
19:57:13  * chorrellquit (Client Quit)
19:59:05  * Fishrock123quit (Remote host closed the connection)
20:03:57  * Fishrock123joined
20:06:29  * Fishrock123quit (Remote host closed the connection)
21:01:27  * Fishrock123joined
21:28:42  * node-ghjoined
21:28:43  * node-ghpart
21:42:01  * evanlucasjoined
21:49:42  * node-ghjoined
21:49:42  * node-ghpart
21:55:26  * node-ghjoined
21:55:26  * node-ghpart
22:00:33  <Trott>orangemocha, joaocgreis, or anyone else who fully understands how the `parallel.status` files in the test directories work: For known_issues, I want to be able to mark tests as failing even if they pass, since known_issues test are expected to fail. Is that something the status files currently can do? Or would that be an enhancement to be written somewhere
22:00:33  <Trott>in the Python code?
22:46:57  * stefanmbquit (Quit: Textual IRC Client: www.textualapp.com)