You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Jules Villard 741e527826 [console] print progress-like messages on stderr ... Summary: Try and enforce the following rules: - stderr is for updating the user about progress or errors - Introduce Logging.progress that outputs to stderr, but honours --quiet - Logging.stderr is as before - Logging.out now prints to stderr (or to log files as before if set up) and not stdout. If some information should go on stdout then the user should be able to rely on it (ie, it's not just some progress message). For now only the summary of the errors is printed on stdout by default. - Logging.err* functions are gone. If the error is user-visible, it should be Logging.stderr, or `failwith`. If not, go to the same log file as other output, which personally I find much more convenient than having to dig through 2 log files every time I'm looking for some output. Reviewed By: jberdine Differential Revision: D5095720 fbshipit-source-id: 68999c9		8 years ago
..
__init__.py	move python code to infer package	9 years ago
ant.py	[infer][toplevel] remove dead code from the python bucklib.py scripts	8 years ago
buck.py	[clang] Collect captured folders in buck-out when keep-going is passed	8 years ago
gradle.py	[infer][toplevel] remove dead code from the python bucklib.py scripts	8 years ago
ndk-build.py	[driver] Add warning about nothing captured	8 years ago
util.py	[console] print progress-like messages on stderr	8 years ago
xcodebuild.py	[CLI] switch to infer-<command> (symlinks) executables	8 years ago