On Tue, 1 Sep 2020 at 13:01, Phill Carter wrote:
> So it is OK to push changes to 2.8?
You might as well.
I have no idea what to do about the release now
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils
> On 1 Sep 2020, at 6:27 pm, andy pugh wrote:
>
> On Tue, 1 Sep 2020 at 00:52, Phill Carter wrote:
>
>> Thanks, I forgot to change the install instructions in the PlasmaC manual to
>> reflect the change to 2.8
>
> The online docs are always the latest, so the only thing that will
> miss
On Tue, 1 Sep 2020 at 00:52, Phill Carter wrote:
> Thanks, I forgot to change the install instructions in the PlasmaC manual to
> reflect the change to 2.8
The online docs are always the latest, so the only thing that will
miss your next commit is the distributed PDF files that are in the
On Tue, 1 Sep 2020 at 03:41, Dewey Garrett wrote:
> 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.
This is getting
> 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
On Mon, 31 Aug 2020 at 17:56, andy pugh wrote:
>
> I think that there are problems with the buildbot, but I know not what.
I think I might have found the problem.
On the builders that fail the tests we see 59 instances of this sequence:
Running test:
> On 1 Sep 2020, at 9:48 am, andy pugh wrote:
>
> On Tue, 1 Sep 2020 at 00:20, Phill Carter wrote:
>
>> Is it too lateyet to add anything to 2.8?
>
> Yes.
> But I don't think that 2.8.1 will be that long in coming. There is a
> lot more Spanish translation due, for one thing.
Thanks, I
On Tue, 1 Sep 2020 at 00:20, Phill Carter wrote:
> Is it too lateyet to add anything to 2.8?
Yes.
But I don't think that 2.8.1 will be that long in coming. There is a
lot more Spanish translation due, for one thing.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
> On 1 Sep 2020, at 8:38 am, andy pugh wrote:
>
> On Mon, 31 Aug 2020 at 17:56, andy pugh wrote:
>
>> Four of the builders are failing runtests, but it isn't so much the
>> tests that are failing as LinuxCNC itself.
>
> I have just realised that the three failed builds after my failed
>
On Mon, 31 Aug 2020 at 17:56, andy pugh wrote:
> Four of the builders are failing runtests, but it isn't so much the
> tests that are failing as LinuxCNC itself.
I have just realised that the three failed builds after my failed
(2.8) build were master. I don't know if Master is building cleanly
On Mon, 31 Aug 2020 at 23:18, andy pugh wrote:
> http://buildbot.linuxcnc.org/buildbot/builders/1610.rip-stretch-rtpreempt-i386/builds/2207/steps/get-dmesg/logs/stdio
>
> It looks like motion-logger is segfaulting.
Though I guess that might be effect rather than cause. Perhaps it is
trying to
On Mon, 31 Aug 2020 at 17:56, andy pugh wrote:
>
> I think that there are problems with the buildbot, but I know not what.
I have just noticed that one of the 4 sometimes dumps a dmesg:
On Monday 31 August 2020 12:56:10 andy pugh wrote:
> I think that there are problems with the buildbot, but I know not
> what.
>
> Four of the builders are failing runtests, but it isn't so much the
> tests that are failing as LinuxCNC itself.
>
>
Andy,
It seems most of the errors relate to IO control relate to a version error
iocontrol: machine: 'unknown' version 'unknown'
So do we need to change another version in the code?
This seems to be where the error comes from on a cursory glance.
I think that there are problems with the buildbot, but I know not what.
Four of the builders are failing runtests, but it isn't so much the
tests that are failing as LinuxCNC itself.
15 matches
Mail list logo
