The log files have moved to a new location, you can see them now at:
http://koji.fedoraproject.org/koji/buildinfo?buildID=619820
https://kojipkgs.fedoraproject.org//packages/pyproj/1.9.4/1.fc23/data/logs/armv7hl/
https://kojipkgs.fedoraproject.org//packages/pyproj/1.9.4/1.fc23/data/logs/i686/
https://kojipkgs.fedoraproject.org//packages/pyproj/1.9.4/1.fc23/data/logs/x86_64/

The tests that are failing are the ones that require epsg, which are a commonly used as a shorthand for long projection string. I would say that this is problematic.

thanks for your comment. Meanwhile I moved to release 2.0.0 for pyproj, and the test results for this one seem much better. All tests pass for python2 and only 5 out of 103 tests fail for python3. See:
https://kojipkgs.fedoraproject.org//packages/pygrib/2.0.0/5.fc24/data/logs/x86_64/build.log
I'll try to find out what went wrong for python3 as soon as I find some time to work on it.

whoops, sorry, mixing two projects here. Version 2.0.0 refers to pygrib. Ofcourse pyproj is still at 1.9.4

pyproj still is at 54 passed and 19 failed, both for python2 and python3, see:
https://kojipkgs.fedoraproject.org//packages/pyproj/1.9.4/4.fc24/data/logs/x86_64/build.log
Next I'll check what happens with the latest version on github.

OK, latest github version looks good. All 73 tests pass both for python2 and python3. Closing this issues.

just for reference, the few failures reported by mistake above on pygrib v2.0.0, are also solved for the latest github version. Here both python2 and python3 versions give me 105 passed tests.

Hmm.. If the lastest github version passes all the test. Perhaps there needs to be a new release. Version 1.9.5?

yes, that would be nice. I noticed there are more reasons to go for a new release, see the discussion in issue #33 on Travis, so if that one is resolved it seems a good idea to me.

A final note on this issue. Afteral it seems the large number of fails was due to my own mistake in the building of the rpm package for pyproj. In Fedora pyproj depends on proj but also on proj-nad and proj-epsg, and I had included these as requirements. However, they are also needed when running the unit tests during the rpm build process, and in this case they should be added as BuildRequires in the spec file as well. After adding this the majority of tests run fine. I'll mention the remaining failures (related to the hammer projection) in another issue.