Mir

The following tests FAILED: 4 - acceptance-tests.ClientPidTestFixture.* (Failed)

Bug #1220493 reported by Huan Peng
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
High
Unassigned

Bug Description

i branch the code form launchpad and had all the dependency installed, while i run debuild i got the error as this:

142/145 Test #142: integration-tests.SwapIntervalSignalTest.* ............................. Passed 0.02 sec
        Start 143: integration-tests.SwapperSwappingStress.*
143/145 Test #143: integration-tests.SwapperSwappingStress.* .............................. Passed 0.01 sec
        Start 144: integration-tests.Synchronizer.*
144/145 Test #144: integration-tests.Synchronizer.* ....................................... Passed 0.01 sec
        Start 145: integration-tests.TestSessionManagerAndFocusSelectionStrategy.*
145/145 Test #145: integration-tests.TestSessionManagerAndFocusSelectionStrategy.* ........ Passed 0.01 sec

99% tests passed, 1 tests failed out of 145

Total Test time (real) = 73.62 sec

The following tests FAILED:
   4 - acceptance-tests.ClientPidTestFixture.* (Failed)
Errors while running CTest
make[2]: *** [test] 错误 8
make[2]:正在离开目录 `/home/ph/mir/obj-i686-linux-gnu'
dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2
make[1]: *** [override_dh_auto_test] 错误 2
make[1]:正在离开目录 `/home/ph/mir'
make: *** [binary] 错误 2
dpkg-buildpackage: 错误: fakeroot debian/rules binary 提供错误退出状态 2
debuild: fatal error at line 1361:
dpkg-buildpackage -rfakeroot -D -us -uc failed

i do this on ubuntu 13.10 beta1 i386

Tags: testsfail
Huan Peng (penghuanmail)
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think this happened to me yesterday. Not sure. Will have to reproduce it again before confirming.

summary: - debuild failed at test step
+ The following tests FAILED: 4 - acceptance-tests.ClientPidTestFixture.*
+ (Failed)
Changed in mir:
importance: Undecided → High
status: New → Triaged
tags: added: testsfail
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This is probably best described as bug 1201436 which just got reopened. So marking as a duplicate of that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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