{"action":"created","issue":{"url":"https://api.github.com/repos/IEEERobotics/bot/issues/376","labels_url":"https://api.github.com/repos/IEEERobotics/bot/issues/376/labels{/name}","comments_url":"https://api.github.com/repos/IEEERobotics/bot/issues/376/comments","events_url":"https://api.github.com/repos/IEEERobotics/bot/issues/376/events","html_url":"https://github.com/IEEERobotics/bot/issues/376","id":98560456,"number":376,"title":"Fixing travis builds","user":{"login":"kvijay1995","id":8673519,"avatar_url":"https://avatars.githubusercontent.com/u/8673519?v=3","gravatar_id":"","url":"https://api.github.com/users/kvijay1995","html_url":"https://github.com/kvijay1995","followers_url":"https://api.github.com/users/kvijay1995/followers","following_url":"https://api.github.com/users/kvijay1995/following{/other_user}","gists_url":"https://api.github.com/users/kvijay1995/gists{/gist_id}","starred_url":"https://api.github.com/users/kvijay1995/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kvijay1995/subscriptions","organizations_url":"https://api.github.com/users/kvijay1995/orgs","repos_url":"https://api.github.com/users/kvijay1995/repos","events_url":"https://api.github.com/users/kvijay1995/events{/privacy}","received_events_url":"https://api.github.com/users/kvijay1995/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/IEEERobotics/bot/labels/field:CS","name":"field:CS","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-08-01T20:42:46Z","updated_at":"2015-08-11T16:16:02Z","closed_at":null,"body":"I noticed that there exists a branch named \"fixing_travis_errors\" and that each travis build has three different jobs namely \"docs\", \"pep8\" and \"py27\". \r\n\r\nI also noticed that we have a different issue where we're actively trying to convert the code base to python 3 #295. If this is the case is it better to not try and fix \"py27\" job since the conversion will effectively replace that with a \"py30\" job or something along those lines @AhmedSamara @dfarrell07 ? Does the same thing apply for fixing pep8 errors, since the formatting will change when we migrate to python 3?"},"comment":{"url":"https://api.github.com/repos/IEEERobotics/bot/issues/comments/129952214","html_url":"https://github.com/IEEERobotics/bot/issues/376#issuecomment-129952214","issue_url":"https://api.github.com/repos/IEEERobotics/bot/issues/376","id":129952214,"user":{"login":"dfarrell07","id":880273,"avatar_url":"https://avatars.githubusercontent.com/u/880273?v=3","gravatar_id":"","url":"https://api.github.com/users/dfarrell07","html_url":"https://github.com/dfarrell07","followers_url":"https://api.github.com/users/dfarrell07/followers","following_url":"https://api.github.com/users/dfarrell07/following{/other_user}","gists_url":"https://api.github.com/users/dfarrell07/gists{/gist_id}","starred_url":"https://api.github.com/users/dfarrell07/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dfarrell07/subscriptions","organizations_url":"https://api.github.com/users/dfarrell07/orgs","repos_url":"https://api.github.com/users/dfarrell07/repos","events_url":"https://api.github.com/users/dfarrell07/events{/privacy}","received_events_url":"https://api.github.com/users/dfarrell07/received_events","type":"User","site_admin":false},"created_at":"2015-08-11T16:16:02Z","updated_at":"2015-08-11T16:16:02Z","body":"> Method 1:\r\n\r\nYou can use `docker run -ti tox -epy27`, FYI.\r\n\r\nI'm seeing 8 unexpected failures, all of which are the same bug. I need to revisit it or dig up some old Issues, but basically the simulated pins we use to fake hardware are files, and we need to make sure they are created in the test setup before we try to use them in the test. That should be handled by [this part](https://github.com/IEEERobotics/bot/blob/master/tests/test_bot.py#L18-L33) of the `TestBot.setUp` method (`TestBot` should be the parent class of all our tests, which makes `TestBot.setUp` run before every test).\r\n\r\n> Method 2:\r\n\r\n> (navigate to bot directory)\r\n> python setup.py test (OR) tox -epy27\r\n\r\nThere are a few reasons this would fail. One, you need all the dependencies setup on your dev system (that's why we use the Vagrant box and Docker image, to package up those deps for you to share). You'd also need to fix the conditional test vs real hardware logic described correctly above.\r\n\r\n> However it's not as simple as just adding this field back in\r\n\r\nAll you should need to do is convert everything to the new fine-grain simulation method (fixing Ahmed's hack, basically).\r\n\r\nI suggest trying the test in the Vagrant env too, idk what the status is there but good to figure out and fix. :)"}}