| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Make consistent with commit 144c23efbb4e9565debad03c13c5bcab833a8336.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this patch the allowed changes were:
1. USE
2. USE + ~arch + license
3. USE + ~arch + license + missing keywords + masks
With this patch:
1. USE
2. USE + ~arch + license
3. USE + ~arch + license + missing keywords
4. USE + ~arch + license + masks
5. USE + ~arch + license + missing keywords + masks
This avoids unmasking live versions, which are typically masked
and have missing keywords to be avoided if there is a regular
masked version available.
|
|
|
|
|
|
| |
Synchronous waiting for status is not supported, since it would be
vulnerable to hitting the recursion limit when a large number of tasks
need to be terminated simultaneously, like in bug #402335.
|
| |
|
|
|
|
|
|
| |
Since commit 4620d6aba1c5c10344e311585516ee43819b703c, the
SequentialTaskQueue.add() method starts the task immediately, so
initialize start_time before that happens.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes a regression since commit
10246cd535f909dda8bd05de617c32d2b8a56b4a which caused layout.conf
settings such as thin-manifests to be ignored for repositories that
had repos.conf settings that did not specify the repository location.
In order to trigger this case, ResolverPlayground has been modified to
omit the location of each repository in the repos.conf file that it
generates.
|
|
|
|
|
|
|
|
|
|
|
| |
If array.fromfile() is not used, then _test_pty_eof() is useless.
This function was for runtime detection of python issue 5380:
http://bugs.python.org/issue5380
However, array.fromfile() use has since been abandoned due to
bugs that exist in all known versions of Python (including Python
2.7 and Python 3.2). See PipeReaderArrayTestCase, for example.
|
|
|
|
| |
Also, generate appropriate SKIP message if pty is not acquired.
|
|
|
|
| |
Allows reliable triggering of the failure mode on fast computers.
|
| |
|
|
|
|
|
|
| |
We have abandoned array.fromfile() due to bugs that exist in all known
versions of Python (including Python 2.7 and Python 3.2). See
PipeReaderArrayTestCase, for example.
|
| |
|
|
|
|
|
| |
Since SpawnProcess no longer uses array, add conditional array support
to PipeReader and use that for tests.
|
|
|
|
| |
https://bugs.pypy.org/issue956
|
|
|
|
|
| |
This makes it unnecessary to explicitly call portage.data._init() in
runTests, and fixes some other cases that trigger the same issue.
|
| |
|
|
|
|
|
|
| |
When I extended test_poll to test SpawnProcess array.fromfile() usage,
it exposed bugs in array.fromfile() that I couldn't find a way to
handle. So, use os.read() instead.
|
| |
|
|
|
|
|
| |
This ensures that global __PORTAGE_TEST_HARDLINK_LOCKS overrides work
correctly for all tests.
|
|
|
|
|
|
| |
This updates the hardlink locking code to support the non-blocking,
lockfile(wantnewlockfile=False), and lockfile(file_object) behaviors
which are used by portage code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This fixes interference from FEATURES=force-prefix in the env.
|
|
|
|
| |
This reduces the amount of patching needed for prefix installs.
|
| |
|
|
|
|
|
| |
There's no need to do this anymore, because we don't restart since
commit d3f704a425a50b5cfa997a25866929b30f1b7d0f.
|
| |
|
| |
|
| |
|
|
|
|
| |
We have to set the EAPI for prefix code to work.
|
|
|
|
| |
This allows our prefix tests to use helpers like insinto, doins, and dosym.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It makes more sense to use EROOT instead of ROOT for keys in mappings
like portage.db, since it allows for multiple prefixes to exist
simultaneously within the same map without having a key collision.
This affects all portageq commands which take a <root> parameter, since
that parameter now corresponds to EROOT instead of ROOT. None of this
makes any difference for non-prefix users, since EROOT and ROOT are
identical when EPREFIX is empty.
|