Bug 11114 - MraaGpio test is failing on Common profile for Refkit
Summary: MraaGpio test is failing on Common profile for Refkit
Status: RESOLVED WORKSFORME
Alias: None
Product: IoT Reference OS Kit
Classification: Yocto Project Subprojects
Component: intel-iot-refkit-default (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low normal
Target Milestone: 2.3 M3
Assignee: Mikko Ylinen
QA Contact: Sonia Delgado
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-02-28 23:40 UTC by Monserrat
Modified: 2017-03-06 13:29 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Monserrat 2017-02-28 23:40:15 UTC 
MraaGpio test is failing on Common profile for Refkit.

Failed
570x.refkit-image-common.oeqa.runtime.sanity.mraa_gpio.MraaGpioTest.test_gpio (from 570x.refkit-image-common.oeqa.runtime.sanity.mraa_gpio.MraaGpioTest-20000105032653)


Error Message
0 != 1 : GPIO pin output is not 1
Stacktrace
Traceback (most recent call last):
  File "/root/workspace/iotos-tester/workspace/intel-iot-refkit_master/iottest/oeqa/runtime/sanity/mraa_gpio.py", line 39, in test_gpio
    self.assertEqual(output, 1, msg="GPIO pin output is not 1")
AssertionError: 0 != 1 : GPIO pin output is not 1
Comment 1 Matti-Pekka Sivosuo 2017-03-01 10:16:51 UTC 
Probably just a glitch in running the tests. Let's wait for another master build and see if this reproduces or not.
Comment 2 Simo Kuusela 2017-03-01 11:53:46 UTC 
I ran this test manually 100 times with Joule 570x and it seemed to fail 2 times. I also ran the GPIO test with Minnowboard Turbot 200 times but the test didn't fail even once. When the test fails there is this kind of error message with mraa-gpio command: 
*** Error in `mraa-gpio': free(): invalid pointer: 0x00000000006193f5 ***
So the problem seems to be with mraa and specifically with Joule and seems to happen quite rarely. No idea if there is some fix to this.
Comment 3 Mikko Ylinen 2017-03-06 13:29:48 UTC 
Same resolution as bug #11113