-
Notifications
You must be signed in to change notification settings - Fork 308
fix travis #3025
Comments
It looks like it's not picking up the database configuration and it's using a default ( One idea I had is that the test deps update (#3017) updated honcho: we're using a fork. That doesn't pan out though. Other hypotheses? |
From the Travis log it looks like the problem is coming from this line: echo "DROP SCHEMA public CASCADE" | psql $DATABASE_URL So |
http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/ |
Not relevant. The new infrastructure is opt-in, and we haven't opted in. |
I'm going to push commits to #3011 to debug the problem. I'll force-push those off once I'm done. |
Hypothesis: |
Here's the env files: https://travis-ci.org/gratipay/gratipay.com/builds/44458444
|
Hypothesis: Nothing whatsoever from the env files make it into |
Hypothesis: The lack of quotes in |
Well, I effed up the tracer in |
None of the tracers are getting picked up. |
What he said. :-) |
Oops, didnt' see the above comment. |
Yoiks. We can see envvars from the base environment, just nothing from our env files. Makes it sound like a honcho problem, but we do seem to be using the same version locally and at Travis. What gives? |
We retried several previously passing commits, and they fail. @rohitpaulk is pinging Travis. IRC |
|
After upgrading to python 2.7.9 tests are failing for me:
|
It's clear that honcho is silently failing to inject the variables into the env. |
Travis is failing on #3011 and #3020 with this error:
What's up? IRC
The text was updated successfully, but these errors were encountered: