Our first successful `python test` run via Docker ``` pants

Question

Our first successful `python test` run via Docker ``` pants test src python pants util strutil test py no python infer conftests 15 59 29 45 INFO Completed Building 1 requirement for requirements pex from the 3rdparty python user reqs lock resolve pytest lt 7 1 0 gt =6 2 4 15 59 36 38 INFO Completed Building pytest runner pex 15 59 38 55 INFO Completed Run Pytest src python pants util strutil test py tests succeeded src python pants util strutil test py tests succeeded in 2 15s ```

hundreds-father-404 · Answer

Apply this diff on `main` and make sure Docker is running ```diff git a src python pants util BUILD b src python pants util BUILD index 76d0a50a8a eb3d2c21cf 100644 a src python pants util BUILD +++ b src python pants util BUILD 3 4 +3 4 python sources python tests name= tests +python tests name= tests environment= docker ```

hundreds-father-404 · Answer

< bitter ability 32190> the ` no python infer conftests` is necessary because our `conftest py` uses `target py` which transitively uses `native engine` That is a `resource` that blindly gets copied into the Docker sandbox it s not platform aware So when run on Docker from macOS we end up with `invalid ELF header` To facilitate us working on this project thoughts on me rewriting the `conftest py` check for badly named Fields to instead be a Flake8 first party plugin Or any other suggestions

bitter-ability-32190 · Answer

I avoided flake8 because the facilities to do this are weak If you wanna tackle it be my guest stuck out tongue Otherwise I m confident we could find a way to adjust conftest

witty-crayon-22786 · Answer

Very exciting Nice work < fast nail 55400> < hundreds father 404> < ancient vegetable 10556>

hundreds-father-404 · Answer

and you too with the graph changes