Octave package tests - results from automated build

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

Octave package tests - results from automated build

octave-2
Hi all,

I have now updated my Jenkins build to better find, run and record the
results of function tests for packages. I discuss this in a bit more
detail here:

http://neilhopcroft.com/octave-package-test-results-revisited/

And the results (from build 147) can be found here:

http://neilhopcroft.com/octave/octave-packages_147.html

These results should also be automatically published for future builds.

This is still a work in progress, but let me know if you think the results
for your package are not what you expected to see.

Neil



Reply | Threaded
Open this post in threaded view
|

Re: Octave package tests - results from automated build

Andreas Weber-4
Am 06.06.2015 um 09:21 schrieb [hidden email]:

> Hi all,
>
> I have now updated my Jenkins build to better find, run and record the
> results of function tests for packages. I discuss this in a bit more
> detail here:
>
> http://neilhopcroft.com/octave-package-test-results-revisited/
>
> And the results (from build 147) can be found here:
>
> http://neilhopcroft.com/octave/octave-packages_147.html
>
> These results should also be automatically published for future builds.
>
> This is still a work in progress, but let me know if you think the results
> for your package are not what you expected to see.

Hi Neil, I'm sure this is wrong:
image-acquisition 0 0 0 0 8


"make check" returns
../src/__v4l2_handler__.cc........................ PASS 3/3
@videoinput/videoinput............................ PASS 1/1
@videoinput/get................................... PASS 4/4
@videoinput/set................................... PASS 7/7
@videoinput/getsnapshot........................... PASS 4/4
imaqhwinfo........................................ PASS 1/1

Summary:

  PASS  20
  FAIL   0

You should link to the detailed output the package tests generate.
-- Andy

Reply | Threaded
Open this post in threaded view
|

Re: Octave package tests - results from automated build

octave-2
Hi Andreas,

> Am 06.06.2015 um 09:21 schrieb [hidden email]:
>> Hi all,
>>
>> I have now updated my Jenkins build to better find, run and record the
>> results of function tests for packages. I discuss this in a bit more
>> detail here:
>>
>> http://neilhopcroft.com/octave-package-test-results-revisited/
>>
>> And the results (from build 147) can be found here:
>>
>> http://neilhopcroft.com/octave/octave-packages_147.html
>>
>> These results should also be automatically published for future builds.
>>
>> This is still a work in progress, but let me know if you think the
>> results
>> for your package are not what you expected to see.
>
> Hi Neil, I'm sure this is wrong:
> image-acquisition 0 0 0 0 8
>
>
> "make check" returns
> ../src/__v4l2_handler__.cc........................ PASS 3/3
> @videoinput/videoinput............................ PASS 1/1
> @videoinput/get................................... PASS 4/4
> @videoinput/set................................... PASS 7/7
> @videoinput/getsnapshot........................... PASS 4/4
> imaqhwinfo........................................ PASS 1/1
>
> Summary:
>
>   PASS  20
>   FAIL   0
>
> You should link to the detailed output the package tests generate.
> -- Andy

You are right that I had missed calling bootstrap for the
image-acquisition package, adding that makes it behave somewhat better:

Package image-acquisition
 list devices
  imaqhwinfo
 v4l2 input
  @videoinput/videoinput
warning: It appears that you have no v4l2 device installed. All tests may
fail. Please connect one or try
       $ modprobe v4l2loopback
       $ gst-launch videotestsrc ! v4l2sink device=/dev/video0
Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
  @videoinput/get
warning: It appears that you have no v4l2 device installed. All tests may
fail. Please connect one or try
       $ modprobe v4l2loopback
       $ gst-launch videotestsrc ! v4l2sink device=/dev/video0
Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
  @videoinput/set
warning: It appears that you have no v4l2 device installed. All tests may
fail. Please connect one or try
       $ modprobe v4l2loopback
       $ gst-launch videotestsrc ! v4l2sink device=/dev/video0
Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
  @videoinput/start
?????
/usr/share/tomcat7/octave/image-acquisition-0.2.1/@videoinput/start.m has
no tests available
  @videoinput/preview
?????
/usr/share/tomcat7/octave/image-acquisition-0.2.1/@videoinput/preview.m
has no tests available
  @videoinput/getsnapshot
warning: It appears that you have no v4l2 device installed. All tests may
fail. Please connect one or try
       $ modprobe v4l2loopback
       $ gst-launch videotestsrc ! v4l2sink device=/dev/video0
Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
  @videoinput/stop
????? /usr/share/tomcat7/octave/image-acquisition-0.2.1/@videoinput/stop.m
has no tests available

Sadly I'm running on a stock AWS kernel without video support, so for the
moment that is as far as I'm going to get. I'll have a bash at getting an
instance up with a custom kernel sometime, but that likely won't happen
soon...unless I can add all the support I need by building and installing
modules? Which modules do I need?

Neil