Tox returns ERROR: invocation failed (exit code 1)

[mlnprice]

@wsmorgan

command 'tox' (from https://github.com/msg-byu/getting-started/blob/master/instructions/first_code.md) returns error, despite using same tox file as in getting-started repository.

https://github.com/mlnprice/MSG-Introduction/blob/dev/tox.ini

[wsmorgan]

Few questions, what python version are you using?
What OS are you using?
Are you using the docker container?

[wsmorgan]

I ask because I can run tox on your code on my local machine with no problem which makes this start looking a lot like a system path problem, which the docker should prevent.

[mlnprice]

I’m new at this so I’ll try my best. Part of it was an issue that came from me not having input the command “pip install —upgrade setuptools” yet. Doing this and then running tox again yielded failures talking about there being “No module named demo.trial” I’m not super sure which python version I’m using for the tutorial, just one of the ones from "docker pull wsmorgan/python" I’m using OS 10.14.4 I am in the docker container, inside the repository with the tox.ini file. On May 13, 2019, at 7:14 PM, Wiley Morgan <notifications@github.com<mailto:notifications@github.com>> wrote: I ask because I can run tox on your code on my local machine with no problem which makes this start looking a lot like a system path problem, which the docker should prevent. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#14?email_source=notifications&email_token=ALOFCMBX5JV74N7ZQLAEXCDPVIG7FA5CNFSM4HMTX23KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJ7LLA#issuecomment-492041644>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALOFCMDS7AAA43TEKI6C55TPVIG7FANCNFSM4HMTX23A>.

[wsmorgan]

If you are getting the error no module called .. then tox is running correctly and your issue is with your unit testing code. When I looked at your code I didn't see any imports for demo.trial did you make more changes?

[mlnprice]

This error came up when I had directly cloned the getting-started repository into my docker container, rather than using my own repository. So, no changes. If it’s working just fine for you, then I will work through this more thoroughly tomorrow to see if I can figure out what is going wrong. Could it be because I am using "pip install --upgrade setuptools" rather than "pip install -e ."? On May 13, 2019, at 10:40 PM, Wiley Morgan <notifications@github.com<mailto:notifications@github.com>> wrote: If you are getting the error no module called .. then tox is running correctly and your issue is with your unit testing code. When I looked at your code I didn't see any imports for demo.trial did you make more changes? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#14?email_source=notifications&email_token=ALOFCMELMKSMT3IBK2O2Y5TPVI7ELA5CNFSM4HMTX23KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKHXXQ#issuecomment-492075998>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALOFCMGYLPYQVXRQOQWVQTDPVI7ELANCNFSM4HMTX23A>.

[wsmorgan]

No that shouldn't be it. To run pytest yourself you would need to do both. Last time I ran the code that's in the repository it worked but that was years ago and I'm not sure if anyone has renamed anything since. You are probably better off focusing on your own project rather than finding whatever typo exists in the demo repository. With pip install --upgrade setuptools you should be able to make progress on your code.

[mlnprice]

In that case, I’ll be sure to learn what principles I can from the guide without getting too caught up in getting it to work perfectly. Thank you for your help. On May 13, 2019, at 11:20 PM, Wiley Morgan <notifications@github.com<mailto:notifications@github.com>> wrote: No that shouldn't be it. To run pytest yourself you would need to do both. Last time I ran the code that's in the repository it worked but that was years ago and I'm not sure if anyone has renamed anything since. You are probably better off focusing on your own project rather than finding whatever typo exists in the demo repository. With pip install --upgrade setuptools you should be able to make progress on your code. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#14?email_source=notifications&email_token=ALOFCMCPWVEMHCYIW3WVNG3PVJDY7A5CNFSM4HMTX23KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKJLFQ#issuecomment-492082582>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALOFCMDYLRAG2SKL6ENTFXLPVJDY7ANCNFSM4HMTX23A>.