-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make enforce-clang-format.cmd also run git diff
.
#255
Conversation
5b51fec
to
d58adaf
Compare
@BillyONeal, my intentionally failing run (original PR) looked great. When I force-pushed the change that's intended to succeed, clang-format appears to be hanging with "Waiting for console output...". Do you know why this is happening? I don't like sporadic failures. |
The Azure Pipelines run after I pushed the 5-minute timeout here succeeded, but now I observe #246 also hanging on enforce-clang-format. Something is wrong. |
I filed #257 for the sporadic clang-format hang. The hang is pre-existing and not caused by this PR. |
This is provided by azure-pipelines.yml. See: microsoft#114 (comment)
77b23e1
to
a178840
Compare
Make enforce-clang-format.cmd also run `git diff`. (microsoft#255)
Description
Make enforce-clang-format.cmd also run
git diff
.This will produce more informative output for clang-format failures.
Also add 5-minute timeouts to every task in
run_build.yml
except'Install MSVC Preview'
. This number was chosen semi-arbitrarily (successful runs appear to have sub-1-minute times for each task).Checklist
Be sure you've read README.md and understand the scope of this repo.
If you're unsure about a box, leave it unchecked. A maintainer will help you.
_Ugly
as perhttps://eel.is/c++draft/lex.name#3.1 or there are no product code changes.
verified by an STL maintainer before automated testing is enabled on GitHub,
leave this unchecked for initial submission).
members, adding virtual functions, changing whether a type is an aggregate
or trivially copyable, etc.).
the C++ Working Draft as a reference (and any other cited standards).
If they were derived from a project that's already listed in NOTICE.txt,
that's fine, but please mention it. If they were derived from any other
project (including Boost and libc++, which are not yet listed in
NOTICE.txt), you must mention it here, so we can determine whether the
license is compatible and what else needs to be done.