Log file Viewer

[08:46:05] <pgadige__> hello! Hello! May I know how to access logs for this channel? Though I see an instruction asking "Use !logs for logs", I'm confused about where I should be executing this command-is it right here inside the channel? I connect to IRC chats using IRSSI.

[08:48:27] <pgadige__> !logs

[08:48:27] <pmxbot> http://kafka.dcpython.org/channel/pypa-dev

[08:49:27] <pgadige__> I figured it out! :)

[09:02:09] <pgadige__> sumanah:Hi! Happy Friday! Related to issue #3139(https://github.com/pypa/warehouse/issues/3139), I think the 'About' section is a good place to put details of 'How do I keep up?'. I'd like to know your thoughts on this.

[09:03:50] <pgadige__> and I'm happy that I learnt a good deal of Jinja2 templates while helping on this issue :)

[10:05:16] <pgadige__> As I run `make tests` on master branch in my local warehouse repo, the tests fail! I haven't made any changes to any file in my local repo. I updated my local repo as mentioned in the docs - on branch master I ran `git fetch upstream` followed by `git rebase upstream/master` and then `git push origin`. I'm sharing the link to the `make tests` results for your reference https://dpaste.de/Mgmp

[10:06:15] <pgadige__> I'll appreciate if you could help me diagnose why the tests are failing.

[10:11:56] <ronny> pgadige__: also note that there is pip list --format=json

[10:23:03] <pgadige__> ronny:`pip list --format=json` just returned the versions of `pip` and `setuptools` and also suggets me to consider upgrading to pip to a new version.

[10:23:53] <pgadige__> ronny: so would upgrading to a new version of pip help solve `make tests` problem that I'm experiencing?

[12:05:20] <tos9> dstufft: so! I am super late back to the party, but it does seem you're correct, and something was combining stderr

[12:05:31] <tos9> (fabric, which never ceases to cause me fun.)

[13:42:59] <di_codes> pgadige__: looks like you might be hitting <https://github.com/pypa/warehouse/issues/1536>, could you try running `docker-compose build static` and then try `make tests` again?

[15:29:22] <pgadige__> !logs

[15:29:22] <pmxbot> http://kafka.dcpython.org/channel/pypa-dev

[16:17:20] <dstufft> uhhh

[16:17:21] <dstufft> wat

[16:21:46] <di_codes> seems like a fluke

[16:24:19] <Wooble> why does that look like node's configure script is python? :/

[16:24:49] <Wooble> oh, it totally is. weird.

[16:29:24] <dstufft> yea

[16:29:27] <dstufft> it's python2 specifically

[16:29:29] <dstufft> and we use py3 lol

[16:30:00] <Wooble> from their github history, it looks like they fixed the syntax and *also* try really hard to make sure it only runs with py2.

[16:30:15] <thea> yeah looks like a fluke. restart the build and see if it works?

[16:32:26] <dstufft> yea it's fine now

[16:32:30] <dstufft> the prebuilt binary timed out

[16:32:34] <dstufft> so it fell back to compiling

[16:32:58] <dstufft> and compiling dind't work cuz `python` is py3

[16:35:20] <pgadige__> di_codes:thank you for suggesting `docker-compose build static` to solve the `make tests` problem that I was experiencing. I'm going to record this in my learning journal.

[16:36:24] <Wooble> dstufft: this sounds like a good argument for py3 virtualenvs not installing a "python" but it's probably a few years too late for that :)

[16:38:32] <di_codes> pgadige__: did that work? sorry about that… that issue is quite old but haven’t gotten around to fixing it yet

[16:53:17] <pgadige__> di_codes: absolutely yes! It worked! :) Thank you for sharing the link to the concerned issue.