00:42
Dejan_ has joined #pypy
00:45
Dejan has quit [Ping timeout: 246 seconds]
00:46
andi- has quit [Ping timeout: 248 seconds]
01:01
andi- has joined #pypy
01:45
jcea has quit [Ping timeout: 250 seconds]
03:04
tos9 has quit [Quit: leaving]
03:06
tos9 has joined #pypy
03:37
tos9 has quit [Quit: leaving]
03:46
tos9 has joined #pypy
07:55
bbot2_ has quit [Quit: buildmaster reconfigured: bot disconnecting]
07:57
bbot2 has joined #pypy
07:59
oberstet has joined #pypy
08:03
bbot2 has quit [Quit: buildmaster reconfigured: bot disconnecting]
08:04
bbot2 has joined #pypy
08:06
lritter has joined #pypy
08:36
sknebel_ is now known as sknebel
08:58
Dejan has joined #pypy
08:58
Dejan has joined #pypy
09:01
Dejan_ has quit [Ping timeout: 268 seconds]
09:30
krono has joined #pypy
11:53
jcea has joined #pypy
14:23
<
tos9 >
this is an unhelpful question but did anything change about the warnings system in pypy3 nightly recently
14:24
<
tos9 >
I have done 0 diagnosing, so if there's not something obvious I should be aware of do ignore that question until I do diagnose :)
14:35
otisolsen70 has joined #pypy
14:47
<
mattip >
and I did touch warnings in 5cab38ca5bce but then backed that out in 472813ba4604
14:48
<
mattip >
that would be around March 8-9
15:10
lritter has quit [Quit: Leaving]
15:15
commandoline has quit [Ping timeout: 248 seconds]
15:16
commandoline has joined #pypy
15:25
<
tos9 >
mattip: it looks like the first day it failed was...
15:25
<
tos9 >
and has failed every night since
15:29
<
tos9 >
(will check hg log in a sec)
15:30
<
mattip >
tos9: the failing test is emitting a DeprecationWarning. What is the expected behaviour?
15:31
<
mattip >
No warning? An error? A different warning?
15:31
<
tos9 >
mattip: it should succeed
15:31
<
tos9 >
that test basically checks some warnings were emitted
15:34
<
tos9 >
(on a call now hooray... will diagnose in a bit)
15:35
<
tos9 >
and a notable piece is that trial fails tests that don't catch their warnings
15:37
<
mattip >
so the warning filter is not catching the warnings?
15:37
<
tos9 >
yeah, that's my guess
15:37
<
tos9 >
is flushWarnings isn't catching that
15:37
<
tos9 >
but only on pypy
15:37
<
tos9 >
and only on nightly
15:38
<
mattip >
ahh, we did change the repl code, so maybe something with stdout/stderr is not right
15:39
<
mattip >
s/not right/different/
16:19
danchr_ is now known as danchr
17:03
lritter has joined #pypy
17:10
larstiq has joined #pypy
17:35
lritter has quit [Ping timeout: 240 seconds]
18:38
<
tos9 >
whaaaaaaaaaaaaaat
18:38
<
tos9 >
mattip: if my brain is on right (which is always a stretch), this bug is quite bad, and has nothing to do with warnings
18:39
<
tos9 >
⊙ ~/Desktop/pypy-c-jit-101940-633376bc07a7-osx64/bin/pypy -c 's = [1, 2, 3]; s[:] = []; print(s)' julian@Airm
18:39
<
tos9 >
list[:] = [] appears to not work
18:39
<
tos9 >
list[:] = () on the other hand does
18:43
<
nulano >
tos9, I think that was fixed yesterday
18:47
<
tos9 >
aha! nice looks like it's on default but not py3.7 which is why my hg log perusing didn't see it
18:47
<
tos9 >
nulano: thanks, that definitely looks like it
18:47
<
tos9 >
(so, I guess nothing to do here but wait till tomorrow's nightly)
20:40
redj has joined #pypy
23:13
oberstet has quit [Remote host closed the connection]