updates on batched-`test` work :thread:
# development
s
updates on batched-
test
work 🧵
🙌 1
the uber-PR with the core plugin API changes has merged (thank you @bitter-ability-32190 and @hundreds-father-404!!!)
❤️ 2
I’ve started working on the actual batching impl for
pytest
. I am hopeful that I can get it done by end-of-week, but @witty-crayon-22786 if you don’t want to wait I think I have an idea for a work-around
❤️ 1
17360 above adds a
[pytest].skip
option. I think we can use that to experiment with batched pytest in Color’s repo by perma-skipping the “default” pytest subsystem and defining (copy-pasting) a parallel subsystem with different rules
the main benefit to waiting for
pantsbuild/pants
would be to have a real example of using the new APIs in the repo, and to flush out any rough edges in the API before release
I leave it up to you all to decide on the trade-offs - I’ll be plugging away at it either way 🙂
w
I’ve started working on the actual batching impl for
pytest
. I am hopeful that I can get it done by end-of-week, but @witty-crayon-22786 if you don’t want to wait I think I have an idea for a work-around
cutting
2.15.x
at end of week would be great, yea.
i’d feel better having the actual implementation landed, and then we can pick a few more things to
2.15.0a
releases if it’s horribly broken.
đź‘Ť 1
s
update: still on track to get the PR open for batched pytest today. the last pre-work PR just merged, and I have the (hopeful) implementation done locally. working on tests now
đź‘Ť 1
❤️ 1
h
feel free to put the PR up now if you want early feedback
s
đź‘Ť will do