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
Add a network pytest mark for tests that use the network #982
Comments
This seems like a good idea. I see you have two tests marked as requiring a network connection. I think that only test_path_installed_plugin_is_none is failing because of missing internet connectivity. (It tries to install the The second test you marked, test_markdown_links appears to be failing for you due to improper encoding of From your
I think this might be due to your use of mistune 2.0.1. (Lektor currently pins As a quick test, I just unplugged my ethernet cable and ran the tests. |
I use #944 and it seems to work (except of this test apparently). Do you know where the problem is? |
https://build.opensuse.org/request/show/944195 by user mcepl + dimstar_suse - Upgrade to 3.3.0: - This release drops support for versions of Python before 3.6. In particular, Python 2.7 is no longer supported. - Quite a few bugs have been fixed since the previous release. - The Admin UI has seen a major refactor and various performance optimisations. It has been rewritten in Typescript, and updated to use v5 of the Bootstrap CSS framework. - Remove unnecessary patches: - more_recent_werkzeug.patch - werkzeug_rename.patch - Added patches making things working: - new_version_of_mistune.patch (gh#lektor/lektor#944) make the package work with mistune 2.* - skip-network-tests.patch (gh#lektor/lektor#982) we build in the network isolated environment, we need to make tests which need it
@mcepl I believe the problem is with I've just filed PR lepture/mistune#295 which, I think, fixes the issue. |
Yes, that fixes it. Thank you. |
Sometimes it's useful to have the tests that use the network marked so they can be skipped easily when we know the network is not available.
This is useful for example on SUSE and openSUSE's build servers. When building our packages the network is disabled so we can assure reproducible builds (among other benefits). With this mark, it's easier to skip tests that can not succeed.
Patch suggesting the solution.
Complete build logs with all packages used and steps taken to reproduce.
The text was updated successfully, but these errors were encountered: