-
Notifications
You must be signed in to change notification settings - Fork 159
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
allow using assets from global path instead of relative path in tests #167
Comments
pravi
changed the title
allow using assets from global path instead of relative path
allow using assets from global path instead of relative path in tests
Mar 2, 2019
A crude method is like this, let me try to make it more generic.
|
This change makes all tests except one to pass
|
Actually this patch also failed the same way in autopkgtest (the earlier test run was during build). For now I have disabled autopkgtest, but it'd be nice to be able to run it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the globally installed handlebars,
all tests fails to find the assets.
https://ci.debian.net/data/packages/unstable/amd64/r/ruby-handlebars-assets/latest-autopkgtest/log.gz
This works when assets are present locally, but we'd like to test the installed package also in debian. If there is a way to make this look for assets relative the the installed path instead of relative to test file path, that would help.
The text was updated successfully, but these errors were encountered: