Google Git
Sign in
bazel / bazel / fc66ead4d499e2933885747452e6af908196a059 / src / main / java / com / google / devtools / build / lib / runtime / CriticalPathComponent.java
  1. f0ff3c0 Remove the preconditions check that an action is not running when accessing its aggregated elapsed time. by jhorvitz · 3 years, 8 months ago
  2. 1e3fe98 Move NanosToEpochConverter to BlazeClock. by twerth · 4 years ago
  3. b26b808 Add runner details to SpawnResult. by Googler · 4 years, 6 months ago
  4. e5759a7 Simplify CriticalPathComponent by Googler · 4 years, 10 months ago
  5. 2b7e71a Require explicit ExecKind in SpawnMetrics.Builder and remove SpawnMetrics.EMPTY by Googler · 4 years, 10 months ago
  6. 0b31794 Introduce AggregatedSpawnMetrics by Googler · 4 years, 10 months ago
  7. ae9bfd4 Move the addition of SpawnMetrics to its Builder by Googler · 4 years, 10 months ago
  8. 4e12ba6 Default CriticalPathComponent duration time to 0 if there is a negative duration. by Googler · 4 years, 11 months ago
  9. 7aa7498 Populate SpawnMetrics and improve CP output by George Gensure · 5 years ago
  10. db32f86 A build's or test's critical path run time was surpassing the execution run time, which is impossible. The root cause was that within the same critical path, multiple actions were run in parallel. Therefore the total run time is the union of all those actions instead of the aggregate (which was the original implementation). by Googler · 5 years ago
  11. ab9d6ad Automated rollback of commit 83d7e1d27a84f2db0d6197af50955e26a9db04fb. by twerth · 5 years ago
  12. 83d7e1d A build's or test's critical path run time was surpassing the execution run time, which is impossible. The root cause was that within the same critical path, multiple actions were run in parallel. Therefore the total run time is the union of all those actions instead of the aggregate (which was the original implementation). by Googler · 5 years ago
  13. c5e3bfe Implemented a new event called DiscoveredInputsEvent that gets posted if the action has discoveredInputs in the ActionExecutionFunction. The discovered inputs event was added to tell the CriticalPathComputer that it took n amount of time to go through the discover input phase and to categorize it at parse time. by Googler · 5 years ago
  14. 1f773ba Automated rollback of commit cfe70bbee566836538c0dff70d26376100657abf. by Googler · 5 years ago
  15. cfe70bb A CriticalPathComponent's input discovery step is not categorized so there is a discrepancy in runtime and metrics provided. Now input discovery will be categorized as parse time. by Googler · 5 years ago
  16. 1ed689c CriticalPathComponents aggregate duration values for actions that have multiple spawns run in parallel. by Googler · 5 years ago
  17. 70d0c3e Add the name of the spawn runner to CriticalPathComponent. by ajurkowski · 6 years ago
  18. ba84986 Don't crash on missing action complete events by ulfjack · 6 years ago
  19. 89b25c3 Handle interrupts (&etc.) before a rewound action re-evaluates by mschaller · 6 years ago
  20. 2343441 Clean up CriticalPath things since action is not nullable by mschaller · 6 years ago
  21. 2485ce0 Dedupe actions for top-k worst action selection by ulfjack · 6 years ago
  22. 79d5ac3 Remove online computation of slowest components by ulfjack · 6 years ago
  23. 3b0d72a Merge SimpleCriticalPathComputer into CriticalPathComputer by ulfjack · 7 years ago
  24. 8b7aad4 Remove generics use from critical path classes by ulfjack · 7 years ago[Renamed (76%) from src/main/java/com/google/devtools/build/lib/runtime/AbstractCriticalPathComponent.java]
  25. 1af71e5 Use an interface to convert from nanos to millis since epoch by ulfjack · 7 years ago
  26. af79eb4 Accept Durations in the CriticalPathComponent and Profiler. by ccalvarin · 7 years ago
  27. a155b53 Replace all usages of Blaze's Preconditions class with guava. by tomlu · 7 years ago
  28. 3bcb9f6 More BUILD file refactorings. by philwo · 8 years ago
  29. 520bbbc Make isRunning protected. by janakr · 8 years ago
  30. 4679739 Avoid Preconditions failures when formatting messages for Preconditions failures. by janakr · 8 years ago
  31. 95d4280 When tracking the critical path, if not keeping incremental state, don't keep references to actions indefinitely. Instead, once an action is finished executing, keep just some metadata about it. This allows actions to be unconditionally dropped when running with --batch, --discard_analysis_cache, and --keep_going, even if profiling is enabled. by janakr · 8 years ago
  32. 536d9cb Make "profile --html --html_details" work again. by Lukacs Berki · 8 years ago
  33. 68e5551 Tolerate the rare state where a dependent of a previously cached shared action sees a different shared action that is in the midst of being an action cache hit. by Janak Ramakrishnan · 9 years ago
  34. 6df8179 Use Bazel Preconditions variant which avoids varargs array creation by Mark Schaller · 9 years ago
  35. f88f4d8 Rationalize copyright headers by Damien Martin-Guillerez · 10 years ago
  36. 4a2b1b3 Use a single critical path component in case of shared actions that run concurrently. We update the timing with the maximum elapsed time. This could prevent us from getting the critical path (because another smaller path could mask the critical path), but in practice we do not expect this to happen. by Miguel Alcon Pinto · 10 years ago
  37. c5102fc Compute action start time in critical path using Clock.currentTimeMillis instead of nanoTime. As nanoTime should only be used to compute time differences. To avoid having to pass two long values representing time (And calling twice to Clock.xxx methods per action executed) we compute the wall time by passing a clock and computing the difference from the start nano time. by Miguel Alcon Pinto · 10 years ago
  38. d08b27f Update from Google. by Han-Wen Nienhuys · 10 years ago