fresh-cat-9082703/01/2022, 12:18 AM
00:15:35.08 [WARN] Unmatched glob from project/project:project's `sources` field: "project/project/othersrc/*.py" Do the file(s) exist? If so, check if the file(s) are in your `.gitignore` or the global `pants_ignore` option, which may result in Pants not being able to see the file(s) even though they exist on disk. Refer to <https://www.pantsbuild.org/v2.8/docs/troubleshooting#pants-cannot-find-a-file-in-your-project>.
hundreds-father-40403/01/2022, 12:20 AM
about inverted filters: ignore everything except for this pattern. Wdyt?
fast-nail-5540003/01/2022, 12:20 AM
hundreds-father-40403/01/2022, 12:21 AM
but I don’t know without further investigation if log messages map into work units.Not all. Adding a stray
isn't associated w/ a particular workunit iiuc
fresh-cat-9082703/01/2022, 12:25 AM
to report deprecations in some parsable form? 😕 The ambition is to fail a build in CI if someone has an unmatched glob pattern in their
./pants update-build-files --check
file but using something that is going to be deprecated should pass. The
perhaps could be used as well.
would of course work short-term, but I think being able to distinguish between warnings and allow programmatic iteration through them is ideal for long-term, imho
[WARN] Unmatched glob
hundreds-father-40403/01/2022, 12:28 AM
has the capability to do this in particular, and
is being merged into
fresh-cat-9082703/01/2022, 12:37 AM
is found in the output, then we can fail because it’s not deprecation (since it’s ignored as per config) but something of interest. However, it can be the case that there are multiple types of warnings so you still end parsing the warning to differentiate between them. FWIW, if you run
, the warnings are shown, but if you re-run
./pants test project::
, the warnings are gone. Is this intentional (hiding warnings if hitting the cache)? I am worried we may be missing some warnings due to cache hits 😕
./pants test --force project::