upstart version 0.9.7-3 failed to build on armel

Bug #791294 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

upstart version 0.9.7-3 failed to build on armel
Link to failed build: https://launchpad.net/ubuntu/+source/upstart/0.9.7-3/+build/2527035

Direct link to the build log: https://launchpad.net/ubuntu/+source/upstart/0.9.7-3/+build/2527035/+files/buildlog_ubuntu-oneiric-armel.upstart_0.9.7-3_FAILEDTOBUILD.txt.gz

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

===============================================
2 of 4 tests failed
Please report to <email address hidden>
===============================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/build/buildd/upstart-0.9.7/util'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/build/buildd/upstart-0.9.7/util'
make[2]: *** [check] Error 2
make[2]: Leaving directory `/build/buildd/upstart-0.9.7/util'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/build/buildd/upstart-0.9.7'
dh_auto_test: make -j1 check returned exit code 2
make: *** [build] Error 29
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110525-2009
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/upstart-0.9.7

Revision history for this message
Dr. David Alan Gilbert (davidgil-uk) wrote :

From log:

PASS: test_initctl
/bin/bash: line 5: 17756 Segmentation fault ${dir}$tst
FAIL: test_utmp
/bin/bash: line 5: 17761 Segmentation fault ${dir}$tst
FAIL: test_sysv
Testing env_option()
...with first argument
...with further argument
PASS: test_telinit
===============================================
2 of 4 tests failed
Please report to <email address hidden>
===============================================

Revision history for this message
Dr. David Alan Gilbert (davidgil-uk) wrote :

Fails in a different test in my test environment (oneiric chroot on panda):

Testing conf_source_reload() with job directory
...with new job directory
...with new file in directory (direct write)
...with modified job (direct write)
...with modified job (atomic rename)
...with deleted job
...with modification to running job
...with modification to replacement for running job
...with deletion of replacement for running job
...with deletion of running job
...with error after modification of job
BAD: wrong value for file, expected (nil) got 0x404ccf78
        at tests/test_conf.c:752 (test_source_reload_job_dir).
/bin/bash: line 5: 3855 Aborted ${dir}$tst

Revision history for this message
Dr. David Alan Gilbert (davidgil-uk) wrote :

Looking at test_conf.c:752 we see:

        nih_io_select_fds (&nfds, &readfds, &writefds, &exceptfds);
        nih_io_handle_fds (&readfds, &writefds, &exceptfds);

        file = (ConfFile *)nih_hash_lookup (source->files, filename);
>>> TEST_EQ_P (file, NULL);

        TEST_FREE (old_job);

The use of nih_ makes me suspicious (without proof) that what we have here is an instance of bug 791315 which is libnih failing it's tests.

Dave

Changed in upstart (Ubuntu):
status: New → 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.