<<Prev Next>> Scroll to Bottom
Stuff goes here
L1[08:07:00] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L2[08:07:18] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L3[08:09:18] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L4[08:38:47] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L5[08:39:00] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L6[08:40:54] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L7[08:41:40] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L8[08:43:14] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L9[08:43:27] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L10[09:00:50] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L11[09:01:04] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L12[09:10:19] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L13[09:10:32] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L14[09:14:44] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L15[09:17:15] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L16[09:17:59] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L17[09:18:12] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L18[09:19:03] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L19[09:19:25] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L20[09:20:23] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L21[09:20:37] ⇨
Joins: MichiTest
(~MichiTest@50-38-30-225.csby.or.frontiernet.net)
L22[09:22:52] <PCL-Jenkins> Starting build
#962 for job LanteaBot (previous build: SUCCESS)
L24[09:23:25] <PCL-Jenkins>
michiyo.ravencroft: change subcommand prefix.
L25[09:25:33] ⇦
Quits: MichiBot (~MichiBot@ip160.ip-192-99-104.net) (Remote host
closed the connection)
L26[09:25:54] ⇨
Joins: MichiBot (~MichiBot@ip160.ip-192-99-104.net)
L27[09:25:54]
Spock sets mode: +o on MichiBot
L28[10:25:35] ⇦
Quits: MichiTest (~MichiTest@50-38-30-225.csby.or.frontiernet.net)
(Read error: Connection reset by peer)
L29[17:49:56] <Forecaster> I need to make a
unit test for these potion functions
L30[19:20:53] <Forecaster> except I can't
really do that due to all the random elements...
L31[19:52:34] <Forecaster> unless I move
all the random table stuff (600+ lines) out of the Helper class and
into it's own class, and add an init method that I can bypass in my
UnitTest main
L32[20:32:31] <Forecaster> hm, I'm gonna
have to use regex to test the outputs so I can account for the
random numbers
L33[20:49:08] <Forecaster> PASSED input
'{r:1-2}' expected output '' output '2'
L34[20:49:20] <Forecaster> I guess an empty
regex pattern matches anything?
L35[20:49:28] <Forecaster> which seems
strange
L36[20:59:54] <Forecaster> alright, got the
unittest system working, and now there is one failure, which is an
interesting one
L37[20:59:55] <Forecaster> Entry 29: FAILED
Drink effect discrepancy for input '{codeword2}' expected output
'CodeWordTest' output '{codewor1}'
L38[21:01:06] <Forecaster> it's treating
the d2 at the end as a dice, and rolls it (which is why it's
sometimes 2) before parsing the codeword tag...
L39[22:54:08] <Forecaster> weird, it parses
dice after replacing the placeholders, or it's supposed to...
L40[22:54:59] <Forecaster> or wait, no it
wasn't
L41[22:55:02] <Forecaster> but now it
does
L42[22:57:37] <Forecaster> there we go, 0
failures
L43[23:01:39] <Forecaster> so it seems this
part is mostly working as intended... so the issue has to be
somewhere else, possibly in how it's updating the array of stored
effects...