OK hopefully last question joy I run matrix tests for pants

Question

OK hopefully last question joy I run matrix tests for pants 14 15 16a0 However the generated testutil dependency is hard limited ``` pantsbuild pants testutil lt 2 16 gt =2 15 0a0 pantsbuild pants lt 2 16 gt =2 15 0a0 ``` I think the easiest is just to regenerate the lockfile before testing but it seems a tiny bit terrible I d prefer not to run three branches for all the variants I support slightly smiling face Any other options

bitter-ability-32190 · Answer

I think you d need multiple lockfiles + multiple resolves disappointed

gorgeous-winter-99296 · Answer

Regenerating the lock in each CI variant seems easier stuck out tongue

bitter-ability-32190 · Answer

Well its one and done

bitter-ability-32190 · Answer

But whatever you feel like is easier is defintely the right choice for you slightly smiling face

gorgeous-winter-99296 · Answer

I think because I need to run with different PANTS VERSION I d also need to triplicate the CI step etc

bitter-ability-32190 · Answer

Probably not I think each test would parametrize on resolve with each possible pants version as a resolve And those each have the lockfile with the pants version So Pants would run your tests in parallel across all pants versions each in its own process Does that make sense

gorgeous-winter-99296 · Answer

No But does run pants run a different pants than the one I m running the test from

gorgeous-winter-99296 · Answer

Otherwise I don t see how it d work stuck out tongue

bitter-ability-32190 · Answer

It uses the Pants referenced in the dependency I think I m like 84 sure

bitter-ability-32190 · Answer

And thats high enough to try it out stuck out tongue

gorgeous-winter-99296 · Answer

partying face It works I have to make every python source be parametrised over every variant of Pants which is eh maybe suboptimal ```pants plugins oci pants backend oci util rules layer py resolve=pants plugins pants plugins oci pants backend oci util rules layer py resolve=pants 214 pants plugins oci pants backend oci util rules layer py resolve=pants 215 pants plugins oci pants backend oci util rules layer py resolve=pants 216 pants plugins oci pants backend oci util rules oci sha py resolve=pants 216 pants plugins oci pants backend oci util rules oci sha py resolve=pants plugins pants plugins oci pants backend oci util rules oci sha py resolve=pants 214 pants plugins oci pants backend oci util rules oci sha py resolve=pants 215 pants plugins oci pants backend oci util rules pull image bundle py resolve=pants plugins pants plugins oci pants backend oci util rules pull image bundle py resolve=pants 214 pants plugins oci pants backend oci util rules pull image bundle py resolve=pants 215 pants plugins oci pants backend oci util rules pull image bundle py resolve=pants 216 pants plugins oci pants backend oci util rules unpack py resolve=pants plugins pants plugins oci pants backend oci util rules unpack py resolve=pants 214 pants plugins oci pants backend oci util rules unpack py resolve=pants 215 pants plugins oci pants backend oci util rules unpack py resolve=pants 216```

bitter-ability-32190 · Answer

Look up ` defaults ` slightly smiling face

bitter-ability-32190 · Answer

but also woohoo

gorgeous-winter-99296 · Answer

Oh for sure no way I d add the resolve in every single directory stuck out tongue Still quadruples the amount of targets

gorgeous-winter-99296 · Answer

Oh geez NOPE Parametrizing the sources with multiple pants variants breaks isort It starts thinking pants is a first party package

bitter-ability-32190 · Answer

`isort` is so wacky

bitter-ability-32190 · Answer

I d just adjust the config Don t throw out the baby with the bathwater

gorgeous-winter-99296 · Answer

Seems like the config discovery gets confused If I just set ``` isort config = pyproject toml ``` it fixes itself