You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prior to #5686 (I think) one could provide absolute paths to tmpdir_factory. I understand the security issues this brings. However, I had a conftest.py implementation which used tmpdir_factory.getbasetemp() and it self created full paths with the base being getbasetemp().
I think in such cases pytest should not fail since the directory is valid and could easily be checked against.
I.e. the directory/file passed should be resolved and if it is prefixed with getbasetemp then all is good, else fails.
I am only now encountering these problems in Travis, pytest version 5.4.1 (not on my local box, since I haven't updated pytest, I am still on 5.0.1).
Prior to #5686 (I think) one could provide absolute paths to
tmpdir_factory
. I understand the security issues this brings. However, I had aconftest.py
implementation which usedtmpdir_factory.getbasetemp()
and it self created full paths with the base beinggetbasetemp()
.I think in such cases
pytest
should not fail since the directory is valid and could easily be checked against.I.e. the directory/file passed should be resolved and if it is prefixed with
getbasetemp
then all is good, else fails.I am only now encountering these problems in Travis, pytest version 5.4.1 (not on my local box, since I haven't updated pytest, I am still on 5.0.1).
See here for the output which creates the fails.
See here for the implementation which itself collects the directories and files that are created.
If anymore information is required, feel free to contact me.
The text was updated successfully, but these errors were encountered: