PDF::Class - Githubissues

AlexDaniel commented 5 years ago

Module PDF::Class cannot be installed (ZefFailure), perhaps it has some failing tests.

Tickets are opened/closed in this repo automatically (though not immediately).
If you can install the module without any problems, add works for me label, leave a comment saying that it works for you and mention any details that you feel are important.
If it needs a native library, put native dependency label, describe what you did to install it and ensure that same instructions are present in the README file of the module (otherwise submit a pull request). Also try to update this wiki page.
If the module is broken, try to fix it and send a PR. Add PR sent label.
If there is a problem in one of the dependencies, add failing dependency label and write a comment explaining the situation. Feel free to work on the corresponding ticket for the failing dependency.
It is a good idea to assign yourself to this ticket if you're working on it (to make sure two or more people are not working on the same ticket at the same time).
Once you are done, search for a next ticket.

If you can't self-assign yourself or attach a label, please let us know on #perl6 channel on freenode or just leave a comment here. We will try to give you privileges as fast as possible.

Output:

===> Searching for: PDF::Class
«timed out after 600 seconds»

Ping @p6-pdf

Previous ticket: #105

AlexDaniel commented 5 years ago

I think the problem here is that tests take a reaallly long time…

JJ commented 5 years ago

The problem was that the source URL didn't exist. I just fixed that. The tests take some time, that's true, but the main problem is that it's installing a whole lot of other modules.

AlexDaniel commented 5 years ago

But this:

«timed out after 600 seconds»

Indicates that the tests were actually running (dependencies were already installed at that point), but they just took a really long time. I don't know what should be done here, maybe it is unreasonable to have so many tests which users have to run when installing the module.

JJ commented 5 years ago

Well, it's PDF, it's got lots of things to test, they're testing PDF functions and capabilities. Can't you increase testing time?

JJ commented 5 years ago

It takes 24 minutes in Travis. So you should triple that time.

dwarring commented 5 years ago

Testing is not that intensive, just that there's a lot of that needs to be compiled and tested with around 110 source files.

Raku / ecosystem-unbitrot

PDF::Class #492