New issue with toolset: CrystaX.NET-apilevel-19-armeabi

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

New issue with toolset: CrystaX.NET-apilevel-19-armeabi

Gennadiy Rozental-2
Not even sure how to interpret this output:

/home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:391:in `block in
adb_devices': undefined method `split' for nil:NilClass (NoMethodError)
?from /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:378:in `each'
?from /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:378:in `adb_devices'
?from /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:881:in `<main>'

Something is clearly wrong

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: New issue with toolset: CrystaX.NET-apilevel-19-armeabi

Dmitry Moskalchuk
On 23/07/15 05:03, Gennadiy Rozental wrote:

> Not even sure how to interpret this output:
>
> /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
> develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:391:in `block in
> adb_devices': undefined method `split' for nil:NilClass (NoMethodError)
> ?from /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
> develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:378:in `each'
> ?from /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
> develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:378:in `adb_devices'
> ?from /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-
> develop/tmp/crystax-ndk-10.2.1/tools/adbrunner:881:in `<main>'
>
> Something is clearly wrong
This is bug in our test launcher "adbrunner", which is aware of
uploading binaries to Android device, setup environment there and run
tests. This is already fixed:
https://github.com/crystax/android-platform-ndk/commit/32e33cb642c354b0851b6eb05065e5e5913d302a,
so Boost tests results will get back to the normal picture next time
when it will run (couple of days).

--
Dmitry Moskalchuk



_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

signature.asc (1K) Download Attachment