| Summary: | MraaGpio test is failing on Common profile for Refkit | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] IoT Reference OS Kit | Reporter: | Monserrat <monserratx.sedeno.bustos> |
| Component: | intel-iot-refkit-default | Assignee: | Mikko Ylinen <mikko.ylinen> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Sonia Delgado <sonia.delgado> |
| Severity: | normal | ||
| Priority: | Low | CC: | matti-pekka.sivosuo, simo.kuusela |
| Version: | unspecified | ||
| Target Milestone: | 2.3 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
Probably just a glitch in running the tests. Let's wait for another master build and see if this reproduces or not. 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. Same resolution as bug #11113 |
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