You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
valschneider
changed the title
Adding CI (e.g. Travis) to devlib
[Feature request] Adding CI (e.g. Travis) to devlib
Jan 16, 2018
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. ;-)
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.
The text was updated successfully, but these errors were encountered: