https://pantsbuild.org/ logo
Join Slack
Powered by
Slightly misleading error message (perhaps fixed o...
# development
c
Slightly misleading error message (perhaps fixed on main, haven’t checked)
Copy code
11:56:51.44 [ERROR] 1 Exception encountered:

  InvalidFieldException: Only fields which will be moved to generated targets may be parametrized, so target generator src/python/... (with type python_sources) cannot parametrize the {'foobar'} field.
as the field doesn’t exist, I think that error should take precedence here 😉 (in my case, I had a typo, which got me looking at this all wrong for a minute 😛 )
👍 1
h
feel free to open an issue if you don't have time to fix today
👍 1
c
I have an issue with a pex lockfile test in this PR, and I can’t really figure out why. Seems to be some kind of dependency on the surrounding tests, because if I single out this one test, it works fine (reproduces for me on main):
Copy code
╰─❯ ./pants test --debug src/python/pants/backend/python/util_rules/pex_test.py:tests -- -vv -k test_lockfiles
======================================================================= test session starts =======================================================================
collected 27 items / 26 deselected / 1 selected

src/python/pants/backend/python/util_rules/pex_test.py::test_lockfiles PASSED                                                                               [100%]

================================================================ 1 passed, 26 deselected in 3.21s =================================================================
Where as if I run all tests, it’s stuck on this particular test:
Copy code
╰─❯ ./pants test --debug src/python/pants/backend/python/util_rules/pex_test.py:tests -- -vv
======================================================================= test session starts =======================================================================
collected 27 items

src/python/pants/backend/python/util_rules/pex_test.py::test_pex_execution[True-Pex] PASSED                                                                 [  3%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_execution[True-VenvPex] PASSED                                                             [  7%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_execution[False-Pex] PASSED                                                                [ 11%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_execution[False-VenvPex] PASSED                                                            [ 14%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_environment[Pex] PASSED                                                                    [ 18%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_environment[VenvPex] PASSED                                                                [ 22%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_working_directory[Pex] PASSED                                                              [ 25%]
src/python/pants/backend/python/util_rules/pex_test.py::test_pex_working_directory[VenvPex] PASSED                                                          [ 29%]
src/python/pants/backend/python/util_rules/pex_test.py::test_resolves_dependencies PASSED                                                                   [ 33%]
src/python/pants/backend/python/util_rules/pex_test.py::test_requirement_constraints PASSED                                                                 [ 37%]
src/python/pants/backend/python/util_rules/pex_test.py::test_lockfiles ^CInterrupted by user.
b
FWIW there's another thread about a hang in pex_test on CI. Might be related?
c
Thx that's the same one. 👍
Open in Slack
PreviousNext
Powered by