hi, pants told me to report this :slightly_smiling...
# general
f
hi, pants told me to report this 🙂
Copy code
2025-05-28T17:02:01.5027959Z Running command: timeout --foreground 21600 pants --process-execution-local-parallelism=1 test :: --tag='IT' -- 
2025-05-28T17:02:01.5585360Z 17:02:01.55 [WARN] Found differences between the new native options parser and the legacy options parser in scope [GLOBAL]:
2025-05-28T17:02:01.5586162Z 
2025-05-28T17:02:01.5586354Z - Value mismatch for the option `tag`:
2025-05-28T17:02:01.5586933Z     Legacy value: ['IT'] of type <class 'list'>, from source FLAG
2025-05-28T17:02:01.5587606Z     Native value: [] of type <class 'list'>, from source HARDCODED
2025-05-28T17:02:01.5588005Z 
2025-05-28T17:02:01.5588699Z If you can't resolve this discrepancy, please reach out to the Pants development team: <https://www.pantsbuild.org//community/getting-help>.
2025-05-28T17:02:01.5589533Z 
2025-05-28T17:02:01.5590377Z The native parser will become the default in 2.23.x, and the legacy parser will be removed in 2.24.x. So it is imperative that we find out about any discrepancies during this transition period.
👀 1
f
cc @happy-kitchen-89482
h
Presumably related:
--tag
is a global flag, so it would need to come before
test
I guess in the old parser we incidentally supported global flags after any target specs (like
::
) but I don’t think that was ever intentional
hmm
What happens if you move that flag before
test
?
f
that did the trick, thanks!