Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

followup fix to pull #619 #620

Merged
merged 2 commits into from
Jul 30, 2012
Merged

followup fix to pull #619 #620

merged 2 commits into from
Jul 30, 2012

Conversation

qwcode
Copy link
Contributor

@qwcode qwcode commented Jul 30, 2012

this corrects the site-packages path for pypy in response to my lib_path fix.

this got the pypy failures down to 2 for me.

@pnasrat
Copy link
Contributor

pnasrat commented Jul 30, 2012

Great - after this goes through the build queue I'll merge.

@pnasrat
Copy link
Contributor

pnasrat commented Jul 30, 2012

Travis pypy run http://travis-ci.org/#!/pypa/pip/jobs/1987701

@travisbot
Copy link

This pull request fails (merged aa20274 into fa8c738).

@pnasrat
Copy link
Contributor

pnasrat commented Jul 30, 2012

So pypy FAILED (SKIP=12, failures=12) the other failure was network issue.

@qwcode
Copy link
Contributor Author

qwcode commented Jul 30, 2012

hmm.... I checked again.. I only have 2 locally.
the extra ones travis are reporting are the ones where there's an expected dir like
created: .virtualenv/site-packages/initools
looking...

@travisbot
Copy link

This pull request passes (merged b7cca4e into fa8c738).

@qwcode
Copy link
Contributor Author

qwcode commented Jul 30, 2012

still left with 12.
I think none of these are new failures

compared to where we were before: http://travis-ci.org/#!/pypa/pip/jobs/1982085

we've gone from
FAILED (SKIP=3, errors=8, failures=17)
to
FAILED (SKIP=12, failures=12)

pnasrat added a commit that referenced this pull request Jul 30, 2012
@pnasrat pnasrat merged commit 6e10adf into pypa:develop Jul 30, 2012
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants