| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
* PollScheduler and all subclasses now use the _terminated_tasks
variable to check whether or not _terminate_tasks() has been called,
and behave appropriately in that case.
* The _schedule_tasks() method now has documentation about the
relationship with _terminate_tasks() and _terminated_tasks.
|
|
|
|
|
| |
This prevents it from being called while the _schedule_tasks()
implementation is running, in order to avoid potential interference.
|
|
|
|
|
|
|
|
| |
If CTRL-C was received at certain times, it was possible for discarded
tasks to be erroneously left in Scheduler._running_tasks, which would
cause the main loop to run infinitely. Thanks to David James
<davidjames@google.com> for reporting this issue and helping to devise
a solution.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, when AbstractPollTask receives a POLLERR or POLLNVAL event,
it would silently cancel the task. Now it will generate a message like
this:
!!! SpawnProcess received strange poll event: 8
The message is displayed via a new _log_poll_exception method, which
is overridden by AbstractEbuildProcess to log the message via elog.
This might help diagnose reported cases of SIGTERM signals killing
ebuild processes for no apparent reason:
http://code.google.com/p/chromium-os/issues/detail?id=12968
|
|
|
|
| |
The dblink constructor is complex and best avoided.
|
| |
|
|
|
|
| |
This will fix bug #357093.
|
| |
|
|
|
|
| |
This will fix bug #356555.
|
|
|
|
| |
This will fix bug #356375 some more.
|
|
|
|
| |
This will fix bug #356375.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This will fix bug #355803.
|
|
|
|
| |
This is part of bug #354787.
|
|
|
|
|
| |
This makes it possible to do things like give special suggestions after
world updates.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This will fix bug #355447.
|
|
|
|
| |
This will fix bug #269534.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This happens if depstring evaluates to nothing.
|
|
|
|
| |
Broken since commit b4f98ec5a1eb2e010a455b19db5bef8d61def241.
|
| |
|
|
|
|
|
| |
This restores some desired logic that was left out of commit
5655b4dcfe5e9dae5e9d6352d791c3d04953baf7.
|
|
|
|
|
| |
Since commit 878f166c5a06b0ab6c5a34dd658c878cc7605fe7, empty implies
deep = True, so these checks are redundant.
|
| |
|
|
|
|
|
|
| |
Always prefer parents for which the parent atom is unsatisfied by the
child node. This seems to be the intention of the code, though it may
not have behaved correctly due to continuation of the parent loop.
|
|
|
|
| |
This will fix bug #354747.
|
|
|
|
|
|
| |
Now the masking display is disabled by the --quiet option if the
--verbose option is not enabled simultaneously. Also, docs are
updated as per bug 58416, comment #11 and #12.
|
| |
|
|
|
|
|
|
| |
Recursively traversed virtual dependencies, and their direct
dependencies, are considered to have the same depth as direct
dependencies.
|
|
|
|
|
| |
Control over recursion depth hasn't behaved properly since commit
6503980e0e3bcfce9fbaff85c33d87f616e955a9. Now it is fixed and tested.
|
|
|
|
|
|
|
| |
This won't change the existing depgraph behavior, but it will allow
logic to be simplified in some cases such that solely the deep param
needs to be consulted (rather than needing to consult both empty and
deep params).
|
|
|
|
|
|
|
|
| |
Atoms are stored in the graph as (atom, id(atom)) tuples since each
atom is considered to be a unique entity. For example, atoms that
appear identical may behave differently in USE matching, depending on
their unevaluated form. Also, specially generated virtual atoms may
appear identical while having different _orig_atom attributes.
|
| |
|
|
|
|
| |
This will fix bug #354437.
|
|
|
|
|
|
|
|
| |
In _add_pkg_dep_string(), _add_pkg() was called with generated
Dependency instances that created fake/distorted edges in the
graph for new-style virtuals (similar to those that were fixed
in commit 5b16e0d800f34dc90cdd8c505172ad16b97f0af4). Now there
won't be any such distorted edges.
|
|
|
|
|
|
|
|
| |
As mentioned in bug #353933, comment #4, special new-style virtual
atoms generated/distorted by _expand_new_virtuals() can prevent
extract_affecting_use() from working properly. This is fixed by
saving the original atoms so that the depgraph can map them back
into place at the appropriate step in dependency evaluation.
|