fresh-cat-90827
03/01/2022, 12:18 AM00: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-404
03/01/2022, 12:20 AM[GLOBAL].ignore_warnings
about inverted filters: ignore everything except for this pattern. Wdyt?fast-nail-55400
03/01/2022, 12:20 AMhundreds-father-404
03/01/2022, 12:21 AMbut I don’t know without further investigation if log messages map into work units.Not all. Adding a stray
logger.warning()
isn't associated w/ a particular workunit iiucfresh-cat-90827
03/01/2022, 12:25 AM./pants update-build-files --check
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 BUILD
file but using something that is going to be deprecated should pass. The ./pants validate
perhaps could be used as well.[WARN] Unmatched glob
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, imhohundreds-father-404
03/01/2022, 12:28 AMupdate-build-files
has the capability to do this in particular, and validate
is being merged into lint
Thoughts?fresh-cat-90827
03/01/2022, 12:37 AM[WARN]
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 ./pants test project::
, the warnings are shown, but if you re-run ./pants test --force 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 😕