xdotool version 1:2.20110530.1-3 failed to build

Bug #823704 reported by Ricardo Salveti
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xdotool (Debian)
Fix Released
Unknown
xdotool (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned

Bug Description

xdotool version 1:2.20110530.1-3 failed to build on armel
Link to failed build: https://launchpad.net/ubuntu/+source/xdotool/1:2.20110530.1-3/+build/2644521

Direct link to the build log: https://launchpad.net/ubuntu/+source/xdotool/1:2.20110530.1-3/+build/2644521/+files/buildlog_ubuntu-oneiric-armel.xdotool_1%3A2.20110530.1-3_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1478 lines into the build log:

14 tests, 14 assertions, 2 failures, 0 errors
make[5]: *** [do-test] Error 1
make[5]: Leaving directory `/build/buildd/xdotool-2.20110530.1/t'
make[4]: *** [test-xvfb] Error 2
make[4]: Leaving directory `/build/buildd/xdotool-2.20110530.1/t'
make[3]: *** [test-xvfb-nowm] Error 2
make[3]: Leaving directory `/build/buildd/xdotool-2.20110530.1/t'
make[2]: *** [test] Error 2
make[2]: Leaving directory `/build/buildd/xdotool-2.20110530.1'
dh_auto_test: make -j1 test returned exit code 2
make[1]: *** [override_dh_auto_test] Error 29
make[1]: Leaving directory `/build/buildd/xdotool-2.20110530.1'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110725-1116
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/xdotool-2.20110530.1

Tags: ftbfs oneiric

Related branches

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Failing while running the test cases:
  1) Failure:
test_de_symbol_typing(XdotoolTypingTests)
    [test_typing.rb:58:in `_test_typing'
     test_typing.rb:118:in `test_de_symbol_typing']:
<"`12345678990-=~ !@\#$%^&*()_+[]{}|;:\",./<>?:\",./<>?"> expected but was
<"`12345678990-=~ !@\#$%&*()_+[]{}|;:\",./<>?:\",./<>?">.

  2) Failure:
test_se_symbol_typing(XdotoolTypingTests)
    [test_typing.rb:58:in `_test_typing'
     test_typing.rb:108:in `test_se_symbol_typing']:
<"`12345678990-=~ !@\#$%^&*()_+[]{}|;:\",./<>?:\",./<>?"> expected but was
<"`12345678990-=~ !@#%^&*()_+[]{}|;:\",./<>?:\",./<>?">.

14 tests, 14 assertions, 2 failures, 0 errors
make[5]: *** [do-test] Error 1

Seems a similar issue is also happening at Debian, but for ia64: https://buildd.debian.org/status/package.php?p=xdotool.

Maybe repo out of sync issue?

Revision history for this message
Julian Taylor (jtaylor) wrote :

debian had this failure on armel too:
http://thread.gmane.org/gmane.comp.tools.xdotool/456

but it is not clear to me what was changed to get it to work.

Revision history for this message
Matthias Klose (doko) wrote :

generic failure.

could be removed for oneiric, together with clipit and keynav (no rdepends)

tags: added: oneiric
removed: arm-porting-queue
Changed in xdotool (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Changed in xdotool (Debian):
status: Unknown → New
Matthias Klose (doko)
summary: - xdotool version 1:2.20110530.1-3 failed to build on armel
+ xdotool version 1:2.20110530.1-3 failed to build
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xdotool - 1:2.20110530.1-3ubuntu1

---------------
xdotool (1:2.20110530.1-3ubuntu1) oneiric; urgency=low

  * Ignore the test results. LP: #823704.
    See http://groups.google.com/group/xdotool-users/browse_thread/thread/795314d390f0b60
 -- Matthias Klose <email address hidden> Thu, 29 Sep 2011 18:41:42 +0200

Changed in xdotool (Ubuntu Oneiric):
status: Confirmed → Fix Released
Changed in xdotool (Debian):
status: New → Confirmed
Changed in xdotool (Debian):
status: Confirmed → Fix Released
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.