| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Developers tend to blame the last printed line when a build takes too
long. Unfortunately, when building concurrently, the last printed line
may have actually finished a long time ago. Under the current system,
ninja does not update the status line to reflect what jobs are still
running. This change makes ninja always print the oldest still running job
instead. In other words, the likely build bottlenecks.
Patch from David Zarzycki, originally uploaded at #1320.
|
|\
| |
| | |
Track in Plan whether wanted edges have been scheduled
|
| |
| |
| |
| |
| |
| |
| |
| | |
Refactor the `want_` map to track for wanted edges whether they have
been scheduled or not. This gives `ScheduleWork` a direct place to keep
this information, making the logic more robust and easier to follow. It
also future-proofs `ScheduleWork` to avoid repeat scheduling if it is
called after an edge has been removed from `ready_` by `FindWork`.
|
| |
| |
| |
| |
| |
| | |
Ninja is supposed to be able to build as C++98 so it can run on old
systems, but it should also be possible to optionally build it with
newer dialects.
|
|\ \
| | |
| | | |
Flush changes into .ninja_log right away.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix disk_interface_test.cc on Windows for 64-bit timestamp
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make sure that stat on Windows, both with and without cache, returns
"missing file" when running stat on notadir/foo where notadir is a
file.
|
| |/ /
| | |
| | |
| | |
| | | |
subdir/subsubdir/.. seems to get the time of subdir/subsubdir on NTFS
(Windows 7), not the time of subdir.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This corrects an inconsistency where build targets were canonicalized
but clean targets were not. For example you could build ./foo but not
clean ./foo.
|
|\ \ \
| | | |
| | | | |
Don't clean up after ourselves when exiting.
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Destruction of NinjaMain can be an expensive operation when dealing
with stupidly large ninjafiles. exit directly instead of returning out
of real_main to avoid doing so.
|
|\ \ \
| | | |
| | | | |
Fix build on Solaris.
|
| |/ /
| | |
| | |
| | | |
Solaris also does not define struct stat's st_mtimensec field.
|
|\ \ \
| | | |
| | | | |
Update Usage to show "-k 0" behavior
|
| |/ /
| | |
| | | |
For "-k N", N==0 is interpreted as infinite. It's useful but not documented in the help, unfortunately.
|
|/ / |
|
|\ \
| | |
| | | |
Use high-resolution timestamps
|
| | | |
|
| | |
| | |
| | |
| | | |
This prevents overflow on Windows where 'long' is not 64-bit.
|
| | |
| | |
| | |
| | |
| | | |
Add parentheses so that constant does not overflow; include inttypes.h
when using MinGW to get the proper macros.
|
| | |
| | |
| | |
| | |
| | | |
This uses the macros as defined by the man page, which, as noted in the
comments, are defined correctly on as many libc's that I could check.
|
| | |
| | |
| | |
| | |
| | | |
Read and write the timestamp as two separate 32-bit integers in a fixed
order to prevent any issues with alignment or byte order.
|
| | |
| | |
| | |
| | |
| | | |
This is needed on older compilers/stdlibs such as on Ubuntu Precise
which is used on Travis.
|
| | |
| | |
| | |
| | |
| | | |
Not sure why the old way works in newer compilers; maybe they just
pre-define these types by defaulting to a newer standard.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This uses nanoseconds on POSIX (±~292 years) and 100-ns increments on
Windows (±~29247 years).
The fallbacks to different structure fields is the only thing grabbed
from #337, with a slight modification in implementation.
|
| |/
| |
| |
| | |
This prepares it for higher-resolution timestamps.
|
|\ \
| | |
| | | |
Fix potential buffer overrun
|
| |/
| |
| |
| |
| | |
This commit rearranges record size comparison and fread() to make sure
fread() only reads the data that can fit into the buffer.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit v1.8.0^2~3^2~1 (Teach RecomputeDirty to detect cycles in
the build graph, 2015-11-13) we correctly reject self-referencing phony
build statements like
build a: phony a
as cycles. Unfortunately this breaks support for CMake 2.8.12.x and
3.0.x because those versions incorrectly produce edges of this form
(that we used to tolerate). In order to preserve compatibility with
those CMake versions we need to restore tolerance of these edges.
Add a special case to the manifest parser to filter out self-referencing
inputs of phony edges of the form produced by those CMake versions.
Warn by default, but add a `-w phonycycle={err,warn}` option to make it
an error.
Fixes: #1322
|
|
|
|
|
|
| |
This will allow more options to be added without updating everywhere
that constructs a ManifestParser. Also extend the AssertParse function
to take the options so tests can control them.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Detect build graph cycles as early as possible
|
| |
| |
| |
| |
| | |
We now detect and reject cycles in DependencyScan::RecomputeDirty before
Plan::AddTarget is called so we can assume DAG input to the Plan.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RecomputeDirty is the earliest traversal of the build graph complete
with depfile-loaded dependencies. Teach it to detect cycles and fail
immediately. This avoids the need to tolerate cycles in RecomputeDirty
only to diagnose them later. It also enables future simplification of
Plan and Builder logic because they will be able to assume DAG input.
When RecomputeDirty detects a cycle, reject it with an error message
like that previously produced by Plan::CheckDependencyCycle.
Previously we used the stat state of each node to determine whether
we reached it earlier in the walk. Retain this approach for leaf
nodes, but add an explicit walk state mark for each Edge so that
we can have a temporary mark to aid cycle detection.
|
| |
| |
| |
| | |
Store a mark in each `Edge` to be updated as it is encountered by a walk.
|
| |
| |
| |
| |
| |
| | |
All call sites have a node on which they call `in_edge()` to call
RecomputeDirty. Simplify call sites by taking the node directly and
calling `in_edge()` internally.
|
| |
| |
| |
| |
| | |
Remove a dependency cycle from the test case, as cycles are covered by
other tests. Ensure this case covers stat failure on a valid graph.
|
|/ |
|
|
|
|
|
|
|
|
| |
PR #1281 added a deference of most_recent_input without checking
for NULL, which can occur if a build rule has no inputs.
Check it for null before dereferencing, and add a test.
Fixes #1290.
|
|\
| |
| | |
Write subprocess output to stdout in binary mode
|
| |
| |
| |
| |
| |
| |
| |
| | |
Set stdout to binary mode while writing subprocess output, so that the
CR in a CR LF sequence is not replaced with CR LF itself, which would
result in CR CR LF.
Based on patch posted by nico in issue #773 comment.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://groups.google.com/forum/#!msg/ninja-build/YQuGNrECI-4/ti-lAs9SPv8J
discusses a case where an rule updates its output file and then
fails. The next run of ninja considers the ouptut file clean
and doesn't rebuild it. Always stat output files after they are
built, and write the mtime into .ninja_log. Consider output files
dirty if the recorded mtime is older than the most recent input
file.
|
| |
| |
| |
| |
| |
| |
| |
| | |
https://groups.google.com/forum/#!msg/ninja-build/YQuGNrECI-4/ti-lAs9SPv8J
discusses a case where an rule updates its output file and then
fails. The next run of ninja considers the ouptut file clean
and doesn't rebuild it. Add a test for this case, which currently
fails.
|
| |
| |
| |
| |
| |
| |
| | |
Stat is not always used through Node::Stat, it is often used directly
through DiskInterface. THe next patches will cause it to be called
even more often through DiskInterface, so move the metrics to
DiskInterface.
|