<fangerer>
Btw. you can dump the generated test sources using `python3 -m pytest --dump-dir=<some_dir> test/test_something.py` (you may need to rebase; the dump feature is pretty new)
jboi has quit [Quit: Bridge terminating on SIGTERM]
ronny has quit [Quit: Bridge terminating on SIGTERM]
jevinskie[m] has quit [Quit: Bridge terminating on SIGTERM]
antocuni[m] has quit [Quit: Bridge terminating on SIGTERM]
jboi has joined #hpy
jevinskie[m] has joined #hpy
ronny has joined #hpy
antocuni[m] has joined #hpy
jboi has quit [Ping timeout: 246 seconds]
jboi has joined #hpy
<fangerer>
PurityLake: I've seen you've updated your PR. Just tell me when you think it's time for the next CI run.
FFY00 has quit [*.net *.split]
FFY00 has joined #hpy
PurityLake__ has joined #hpy
<PurityLake__>
Hey all, finally able to get back on the IRC. I believe I have fixed the failing test on the PR. Apologies for the fact they failed in the first place
<fangerer>
Is it ready for triggering the CI ?
<PurityLake__>
Yes it should be
<PurityLake__>
I have no failing tests my end
<PurityLake__>
I copied the testing methods from the .yml for testing these things, should be all good
<fangerer>
👍
<PurityLake__>
docs failed? I literally just check that
<PurityLake__>
Should be the only fail though
dalley has quit [Ping timeout: 264 seconds]
<PurityLake__>
Does it cost anything to run these CI runs?
dalley has joined #hpy
mattip has quit [Ping timeout: 268 seconds]
mattip has joined #hpy
mattip has quit [Ping timeout: 268 seconds]
mattip has joined #hpy
dalley has quit [Ping timeout: 268 seconds]
mattip has quit [Ping timeout: 252 seconds]
mattip has joined #hpy
dalley has joined #hpy
PurityLake__ has quit [Quit: Ping timeout (120 seconds)]