-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node_icon.diag
assumes a network connection and Debian system
#20
Comments
I'm not even sure that this file is used in the test suite. Could you please provide which command is failing while creating the Nix package? |
Sure, here’s the failure from the log:
|
Thanks! I guess we want to make sure that BlockDiag can resolve an icon from an absolute path and/or from an URL. I will take a deeper look in order to make the tests more portable. |
Thanks for considering this! Those all sound like reasonable solutions to me. Note that downstream packages like |
If the HTTP server is started as part of the test suite (in a dedicated thread) it should work right? In other words, the test suite won't assume that a HTTP server is running. We could use something like: https://pytest-httpserver.readthedocs.io/en/latest/ |
Right, I just mean that downstream projects use the blockdiag test generators that work with these fixtures, e.g. |
blockdiag/src/blockdiag/tests/diagrams/node_icon.diag
Lines 1 to 6 in ce37f0c
These cause problems for us in Nixpkgs, as we of course don’t have a Debian logo lying around on the filesystem and our build and testing environment cannot access external network resources.
I see that the Debian logo is already present in‐tree, so hopefully that could be changed to a local reference. I’m not sure if the URL is critical to the functionality being tested here, but I thought I’d raise it anyway.
(Copied from blockdiag#184.)
The text was updated successfully, but these errors were encountered: