Mir

The following tests FAILED: 134 - unit-tests.UdevWrapperTest.* (OTHER_FAULT)

Bug #1253507 reported by Daniel van Vugt
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mir
Won't Fix
Undecided
Unassigned

Bug Description

In the past day or so a regression appeared when building on saucy:

The following tests FAILED:
 134 - unit-tests.UdevWrapperTest.* (OTHER_FAULT)
Errors while running CTest

...
[==========] 25 tests from 1 test case ran. (271 ms total)
[ PASSED ] 4 tests.
[ FAILED ] 21 tests, listed below:
[ FAILED ] UdevWrapperTest.IteratesOverCorrectNumberOfDevices
[ FAILED ] UdevWrapperTest.UdevDeviceHasCorrectDevType
[ FAILED ] UdevWrapperTest.UdevDeviceHasCorrectDevPath
[ FAILED ] UdevWrapperTest.UdevDeviceHasCorrectDevNode
[ FAILED ] UdevWrapperTest.UdevDeviceComparisonIsReflexive
[ FAILED ] UdevWrapperTest.UdevDeviceComparisonIsSymmetric
[ FAILED ] UdevWrapperTest.UdevDeviceDifferentDevicesCompareFalse
[ FAILED ] UdevWrapperTest.UdevDeviceDifferentDevicesAreNotEqual
[ FAILED ] UdevWrapperTest.UdevDeviceSameDeviceIsNotNotEqual
[ FAILED ] UdevWrapperTest.EnumeratorMatchParentMatchesOnlyChildren
[ FAILED ] UdevWrapperTest.EnumeratorEnumeratesEmptyList
[ FAILED ] UdevWrapperTest.EnumeratorAddMatchSysnameIncludesCorrectDevices
[ FAILED ] UdevWrapperTest.UdevMonitorTriggersAfterEnabling
[ FAILED ] UdevWrapperTest.UdevMonitorSendsRemoveEvent
[ FAILED ] UdevWrapperTest.UdevMonitorSendsChangedEvent
[ FAILED ] UdevWrapperTest.UdevMonitorEventHasCorrectDeviceDetails
[ FAILED ] UdevWrapperTest.UdevMonitorFdIsReadableWhenEventsAvailable
[ FAILED ] UdevWrapperTest.UdevMonitorFdIsUnreadableAfterProcessingEvents
[ FAILED ] UdevWrapperTest.UdevMonitorFiltersByPathAndType
[ FAILED ] UdevWrapperTest.UdevMonitorFiltersAreAdditive
[ FAILED ] UdevWrapperTest.UdevMonitorFiltersApplyAfterEnable

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Mostly the tests report:
C++ exception with description "Udev device does not exist" thrown in the test body.

Changed in mir:
milestone: none → 0.1.2
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Full test output

Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

I can reproduce this bug on trusty, too, when building locally.

Changed in mir:
assignee: nobody → Alexandros Frantzis (afrantzis)
Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

After a clean rebuild tests pass on trusty when running with ctest. Running unit-tests manually still fails, of course, unless I use umockdev-wrapper (or LD_PRELOAD). Daniel can you please try on saucy with a clean build to see if it makes a difference there?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I am always testing with a "clean build".

Confirmed the tests are now failing on both saucy and trusty. However on trusty I have to run them directly to get the failure:
    bin/unit-tests --gtest_filter="*Udev*"

Changed in mir:
importance: High → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also, bug 1253876 sounds related.

Daniel van Vugt (vanvugt)
Changed in mir:
milestone: 0.1.2 → 0.1.3
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Apparently the issue is that we recently added a new requirement that the unit tests can only be run under umockdev-run. However doing so results in bug 1259851.

Changed in mir:
importance: Critical → Undecided
Alexandros Frantzis (afrantzis)
Changed in mir:
assignee: Alexandros Frantzis (afrantzis) → nobody
Daniel van Vugt (vanvugt)
Changed in mir:
milestone: 0.1.3 → 0.1.4
Daniel van Vugt (vanvugt)
Changed in mir:
milestone: 0.1.4 → 0.1.5
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Won't fix. See comment #7.

Changed in mir:
milestone: 0.1.5 → none
status: Triaged → Won't Fix
tags: added: umockdev
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.