-
Notifications
You must be signed in to change notification settings - Fork 50
Test error Debian sid #1624
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
Comments
hello @avalentino ,
yes, sure
Looking at your attached logs, there are a lot of |
Thanks @sbrunato After applying the patch in PR #1631 the number of errors is drastically reduces:
For
the problem seems to be linked to an attempt to access the internet. For
the pronlem seems to be linked to an attempt to read/write to the HOME folder (which points to an unexisting path in the Debian tests). For
apparently, the issue seems to be linked to the impossibility to access the proper configuration file. For the last one it is not clear to me the reason of the failure
|
I'm trying to package eodag for debian.
Once done I would like to have the debian package for eodag published as part fo the official Debian archive.
I hope that this is OK for the eodag developers.
As part of the procedure to create debian package the SW is built and tested in and environment that does not have access to the interned.
In such environment I the execution of the unittest suite fails with a very large number of errors.
In particular, all tests in the following files fail:
Moreover the following additional tests fail:
Please find attached the full build log.
From what I cna say, some of the failures are clearly due to the impossibility to access the network.
In other case it seems more an issue with the management of plugins that could, maybe, be linked to the test environement.
I would like to kindly ask support to to identify tests that cannot be run in the debian build environemt and some help/hint to understand the reason of the errors in the remaining ones.
eodag-buildlog.txt
The text was updated successfully, but these errors were encountered: