Skip to content
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

[Feature request] Adding CI (e.g. Travis) to devlib #230

Open
valschneider opened this issue Jan 16, 2018 · 2 comments
Open

[Feature request] Adding CI (e.g. Travis) to devlib #230

valschneider opened this issue Jan 16, 2018 · 2 comments
Milestone

Comments

@valschneider
Copy link
Contributor

Hi,

The issue fixed in PR #229 was raised by LISA's Travis run of ARM-software/lisa#541. Since our Travis setup uses a LocalLinuxTarget to verify some of LISA's functionalities, the same could be done for devlib - after all, a devlib bug was found with this setup.

Is there any plan to add this kind of test to devlib ? I think even something as basic as creating a LocalLinuxTarget, pushing a basic script and executing it would be useful.

@valschneider valschneider changed the title Adding CI (e.g. Travis) to devlib [Feature request] Adding CI (e.g. Travis) to devlib Jan 16, 2018
@derkling
Copy link
Contributor

Maybe can be considered kind of overkilling, but a very simple and still working solution for the time being, could be to run the same LISA's Travis setup. Being LISA a devlib client, it already provides some tests which stress devlib APIs... and it will ensure you do not break one of main devlib's users. ;-)

@marcbonnici
Copy link
Collaborator

Hi,
Yes this would definitely be something we would be interested in implementing, and we have added it to our road map.

@marcbonnici marcbonnici added this to the Future milestone Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants