| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
...now that the ExtendedEventHandler can serve the same purpose.
--
PiperOrigin-RevId: 148640618
MOS_MIGRATED_REVID=148640618
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To give a better understanding of which packages are on the critical
path during loading and analysis, provide information in the same way
as during execution: show the earliest started, but not yet completed
package. As not all packages looked at during the analysis phase are
reported to the progress receiver, use a custom class to aggregate those
data.
--
Change-Id: I03c25efdecb4124e1bc06fce8be9175dc56b5500
Reviewed-on: https://bazel-review.googlesource.com/#/c/3700
MOS_MIGRATED_REVID=123408689
|
|
|
|
|
|
|
|
|
|
|
| |
Even during analysis, more packages will be loaded. However, those are
not tracked by the LoadingProgressReceiver. Therefore, provide a reference
to the AtomicInteger counting the total number of packages loaded already.
--
Change-Id: Ia546a2fec4afe6fd1bd69448b14ba889c68ae12c
Reviewed-on: https://bazel-review.googlesource.com/#/c/3644
MOS_MIGRATED_REVID=122722688
|
|
The main purpose of this event is to provide the LoadingProgressReceiver to
any interested listener. Note that this event will only be raised if the
option --experimental_skyframe_target_pattern_evaluator is given.
--
Change-Id: Ic675c9e1255b7d60de28bdad1ec1838655abd389
Reviewed-on: https://bazel-review.googlesource.com/#/c/3269
MOS_MIGRATED_REVID=119258070
|