Skip to content

Tests fail when run inside pbuilder #15

@mark0n

Description

@mark0n

PCI tests fail when run inside pbuilder:

23:57:32 make[2]: Entering directory '/tmp/buildd/devlib2-2.9/testApp'
23:57:32 make -C O.linux-x86_64 -f ../Makefile TOP=../.. \
23:57:32     T_A=linux-x86_64 runtests
23:57:32 make[3]: Entering directory '/tmp/buildd/devlib2-2.9/testApp/O.linux-x86_64'
23:57:32 perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' pcitest.t epicsMMIOTest.t
23:57:32 Could not open /sys/bus/pci/devices!
23:57:32 pcitest.t ........ 
23:57:32 Failed 19/24 subtests 
23:57:32 epicsMMIOTest.t .. ok
23:57:32 
23:57:32 Test Summary Report
23:57:32 -------------------
23:57:32 pcitest.t      (Wstat: 0 Tests: 9 Failed: 4)
23:57:32   Failed tests:  6-9
23:57:32   Parse errors: Bad plan.  You planned 24 tests but ran 9.
23:57:32 Files=2, Tests=23,  0 wallclock secs ( 0.03 usr  0.01 sys +  0.02 cusr  0.00 csys =  0.06 CPU)
23:57:32 Result: FAIL
23:57:32 Failed 1/2 test programs. 4/23 subtests failed.
23:57:32 /etc/epics/configure/RULES_BUILD:322: recipe for target 'runtests' failed
23:57:32 make[3]: [runtests] Error 255 (ignored)
23:57:32 make[3]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp/O.linux-x86_64'
23:57:32 make -C O.linux-x86_64-debug -f ../Makefile TOP=../.. \
23:57:32     T_A=linux-x86_64-debug runtests
23:57:32 make[3]: Entering directory '/tmp/buildd/devlib2-2.9/testApp/O.linux-x86_64-debug'
23:57:33 perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' pcitest.t epicsMMIOTest.t
23:57:33 Could not open /sys/bus/pci/devices!
23:57:33 pcitest.t ........ 
23:57:33 Failed 19/24 subtests 
23:57:33 epicsMMIOTest.t .. ok
23:57:33 
23:57:33 Test Summary Report
23:57:33 -------------------
23:57:33 pcitest.t      (Wstat: 0 Tests: 9 Failed: 4)
23:57:33   Failed tests:  6-9
23:57:33   Parse errors: Bad plan.  You planned 24 tests but ran 9.
23:57:33 Files=2, Tests=23,  0 wallclock secs ( 0.03 usr  0.01 sys +  0.02 cusr  0.00 csys =  0.06 CPU)
23:57:33 Result: FAIL
23:57:33 Failed 1/2 test programs. 4/23 subtests failed.
23:57:33 /etc/epics/configure/RULES_BUILD:322: recipe for target 'runtests' failed
23:57:33 make[3]: [runtests] Error 255 (ignored)
23:57:33 make[3]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp/O.linux-x86_64-debug'
23:57:33 make -C O.RTEMS-mvme2100 -f ../Makefile TOP=../.. \
23:57:33     T_A=RTEMS-mvme2100 runtests
23:57:33 make[3]: Entering directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme2100'
23:57:33 perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' 
23:57:33 make[3]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme2100'
23:57:33 make -C O.RTEMS-mvme2307 -f ../Makefile TOP=../.. \
23:57:33     T_A=RTEMS-mvme2307 runtests
23:57:33 make[3]: Entering directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme2307'
23:57:33 perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' 
23:57:33 make[3]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme2307'
23:57:33 make -C O.RTEMS-mvme3100 -f ../Makefile TOP=../.. \
23:57:33     T_A=RTEMS-mvme3100 runtests
23:57:33 make[3]: Entering directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme3100'
23:57:33 perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' 
23:57:33 make[3]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme3100'
23:57:33 make -C O.RTEMS-mvme5500 -f ../Makefile TOP=../.. \
23:57:33     T_A=RTEMS-mvme5500 runtests
23:57:33 make[3]: Entering directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme5500'
23:57:33 perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' 
23:57:33 make[3]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp/O.RTEMS-mvme5500'
23:57:33 make[2]: Leaving directory '/tmp/buildd/devlib2-2.9/testApp'

I'm wondering if these tests should be disabled by default. Or maybe we should disable them only when building the Debian package by adding an appropriate patch to the patch queue? Or maybe we can make the build smart enough to skip these tests if this is run inside a chroot environment?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions