lesshaste has quit [Read error: Connection reset by peer]
lesshaste has joined #pypy
jcea has quit [Ping timeout: 248 seconds]
dmalcolm_ has quit [Remote host closed the connection]
jinsun has joined #pypy
lesshaste has quit [Read error: No route to host]
lesshaste has joined #pypy
dmalcolm has joined #pypy
dmalcolm has quit [Read error: Connection reset by peer]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 246 seconds]
dmalcolm has joined #pypy
dmalcolm_ has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
dmalcolm_ has quit [Ping timeout: 255 seconds]
dmalcolm has joined #pypy
dmalcolm_ has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
lazka has quit [Remote host closed the connection]
lehmrob has joined #pypy
dmalcolm_ has quit [Ping timeout: 248 seconds]
marvin_ has quit [Remote host closed the connection]
marvin_ has joined #pypy
lazka has joined #pypy
marvin_ has quit [Remote host closed the connection]
lazka has quit [Quit: bye]
marvin has joined #pypy
lazka has joined #pypy
lehmrob has quit [Ping timeout: 252 seconds]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 268 seconds]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
dmalcolm has joined #pypy
dmalcolm has quit [Ping timeout: 248 seconds]
lesshaste has quit [Read error: Connection reset by peer]
leshaste has joined #pypy
dmalcolm has joined #pypy
dmalcolm_ has joined #pypy
dmalcolm has quit [Ping timeout: 252 seconds]
dmalcolm_ has quit [Ping timeout: 252 seconds]
dmalcolm_ has joined #pypy
dmalcolm_ has quit [Remote host closed the connection]
jcea has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Dejan has joined #pypy
<
Dejan>
How come there are so many applevel tests in 3.9 (compared to 3.10 and 3.8)
<
Dejan>
i mean failed tests :)
<
cfbolz>
Dejan: are there?
<
Dejan>
the difference is order of magnitude
leshaste has quit [Read error: Connection reset by peer]
lesshaste has joined #pypy
leshaste has joined #pypy
lesshaste has quit [Remote host closed the connection]
dmalcolm has joined #pypy
greedom has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
<
cfbolz>
Dejan: hm, that's a bit weird
<
cfbolz>
Dejan: it's a bit suspicious that 3.9 on 64bit linux has so much more failing tests according to this view than 32bit linux
<
cfbolz>
and then if I actually click on the huge number to go to the detailed view, I see a different lower number of failures:
leshaste has quit [Remote host closed the connection]
leshaste has joined #pypy
derpydoo has quit [Quit: derpydoo]
otisolsen70 has joined #pypy
otisolsen70 has quit [Remote host closed the connection]
greedom has quit [Remote host closed the connection]
<
mattip>
it seems the summary is off, and this started Jan 23
<
mattip>
which is just when I modified the buildbot code to handle junitxml output
<
mattip>
I think those summary numbers are "nice to have", but maybe it would be easier to just remove them
<
cfbolz>
mattip: I suspect it might be something shallow to fix them though, because most of them look accurate
<
mattip>
maybe, but that still requires time and effort
<
mattip>
the first step to fixing it would be to write a failing test in bot2/pypybuildbot/test/test_summary.py in the pypy/buildbot repo
derpydoo has joined #pypy