did something change between 1.5 and 1.7 1.3 and 1...
# general
f
did something change between 1.5 and 1.7 1.3 and 1.5 that prevents multiple versions of a python library from existing in the same repo? when trying to run all tests in the repo, I’m now getting pex resolve errors for different packages needing incompatible versions of the same library, even though (AFAICT, and given that this used to be working) this is not the case for any single pex file
a
what stage of the build is it failing at? is it possible to provide an example of what used to work? i'm unfortunately not personally familiar with any changes that may have caused this issue but am looking through changelogs now
(couldn't see anything obvious, sorry)
if you file an issue with some more info we can take a look
i'm sorry you're having issues upgrading!
f
hm, didn’t realize how new 1.7 was; will probably just go for 1.6 for now
actually, I was wrong, this seems broken for me in 1.5 as well; 1.3 was the last time this was definitely working
failing at pyprep -> requirements
only seems to be an issue when you build all tests at once w/ a single invocation of pants
a
ok, this may be related to the test caching changes, some of which are described in https://www.pantsbuild.org/notes-1.4.x.html -- could you let me know what the output of
./pants options | grep -iP 'fast|chroot'
is? and which version have you settled on now? and are you just running
./pants test ::
?
(i'm not very familiar with the test caching features, but i have seen users experience difficulty when upgrading for similar ish reasons i think)
(the caching isn't broken, but i think the interface might be nonintuitive or require some changes to pants options -- i could be way off base here)
(and generally we try really hard to not make breaking changes for exactly this reason, so i wouldn't call this an expected difficulty)
(also, i said test "caching" -- likely not at all related to caching whatsoever, just meant general pytest changes)