> It seems most of the errors relate to IO control
> relate to a version error
> iocontrol: machine: 'unknown'  version 'unknown'

this message is informational -- not an error that would
cause termination

>> Application initialization failed: no display name and no $DISPLAY
>> environment variable
>> Not starting new LinuxCNC

This misleading message is more likely caused by existence
of a 'leftover' LOCKFILE probably from an earlier failure
of the buildbot instance.

Note that the runtests scripts *unsets* the DISPLAY
environmental variable:
"# The linuxcnc starter script sometimes tries to display X windows if
 # DISPLAY is set.  We never want that while running tests, so unset it.
 unset DISPLAY"

Ref: https://github.com/LinuxCNC/linuxcnc/blob/2.8/scripts/runtests#L7

I made a test branch rebased to 2.8 at 69f7ce09b that
rm'd the LOCKFiLE as a workaround:

Ref:
https://github.com/LinuxCNC/linuxcnc/commits/dgarr/tst28
https://github.com/LinuxCNC/linuxcnc/commit/80b413852a1d3de2d837d28d855de8f730cd83df

This workaround lets a failing buildbot instance get a little further reporting:

"
!!! unexpected LOCKFILE at start of runtests
!!! removing /tmp/linuxcnc.lock
!!! Note: this debug does not solve problem of a leftover LOCKFILE
Running test: 
/home/buildslave/emc2-buildbot/wheezy-i386/rip-wheezy-i386/build/tests/abort/feed-rate
+ rm -f sim.var
+ linuxcnc -r test.ini
Machine configuration file is 'test.ini'
Starting LinuxCNC...
(time=1598926913.533681,pid=24099): Registering server on TCP port 5005.
libnml/cms/tcp_srv.cc 280: bind error: 98 -- Address already in use
libnml/cms/tcp_srv.cc 281: Server can not bind the connection socket on port 
5005.
libnml/rcs/rcs_exit.cc 96: 
 Errors Reported!!!
 Press ^C to exit.
"
Ref:
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/5354/steps/runtests/logs/stdio

The 'Address already in use' probably relates to an earlier problem and
likely needs manual intervention or a reboot of the reporting buildbot
instance(s).  A reboot will (conventionally) rm the LOCKFILE in /tmp
as well.
-- 
Dewey Garrett



_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to