#linuxcnc-devel Logs

Oct 04 2023

12:56 AM pere: andypugh: anything more I can do to help with the release?
01:11 AM linuxcnc-build2: Build [#1586](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1586) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
01:11 AM linuxcnc-build2: Build [#1590](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1590) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 4failed.
01:11 AM linuxcnc-build2: Build [#1664](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1664) of `00-checkin` 4failed.
01:39 AM linuxcnc-build2: Build [#1586](http://buildbot2.highlab.com/buildbot/#builders/14/builds/1586) of `10-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
01:40 AM linuxcnc-build2: Build [#1587](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1587) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
02:07 AM linuxcnc-build2: Build [#1591](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1591) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 8completed with warnings.
02:23 AM linuxcnc-build2: Build [#1665](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1665) of `00-checkin` 3completed successfully.
02:29 AM linuxcnc-build: build #3481 of 1660.rip-buster-python3 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3481 blamelist: CMorley <chrisinnanaimo@hotmail.com>, andypugh <andypugh@Boookworm.bodgesoc>, andypugh <andy@bodgesoc.org>
03:25 AM linuxcnc-build: build #3883 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3883 blamelist: CMorley <chrisinnanaimo@hotmail.com>, andypugh <andypugh@Boookworm.bodgesoc>, andypugh <andy@bodgesoc.org>
03:38 AM linuxcnc-build2: Build [#1587](http://buildbot2.highlab.com/buildbot/#builders/14/builds/1587) of `10-rip.debian-10-buster-rtpreempt-amd64` 4failed.
03:58 AM linuxcnc-build2: Build [#1588](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1588) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
03:58 AM linuxcnc-build2: Build [#1666](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1666) of `00-checkin` 4failed.
04:21 AM linuxcnc-build: build #10301 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10301 blamelist: CMorley <chrisinnanaimo@hotmail.com>, andypugh <andypugh@Boookworm.bodgesoc>, andypugh <andy@bodgesoc.org>
04:24 AM linuxcnc-build: build #7406 of 1903.clang-wheezy-amd64 is complete: Failure [4failed garbage-collect git repo] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1903.clang-wheezy-amd64/builds/7406 blamelist: CMorley <chrisinnanaimo@hotmail.com>
04:31 AM linuxcnc-build2: Build [#1588](http://buildbot2.highlab.com/buildbot/#builders/14/builds/1588) of `10-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
04:32 AM linuxcnc-build2: Build [#1589](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1589) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
04:53 AM linuxcnc-build2: Build [#1667](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1667) of `00-checkin` 3completed successfully.
05:46 AM linuxcnc-build2: Build [#1594](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1594) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 4failed.
05:51 AM linuxcnc-build: build #10302 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10302 blamelist: CMorley <chrisinnanaimo@hotmail.com>
06:12 AM linuxcnc-build2: Build [#1590](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1590) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
06:18 AM linuxcnc-build2: Build [#1589](http://buildbot2.highlab.com/buildbot/#builders/14/builds/1589) of `10-rip.debian-10-buster-rtpreempt-amd64` 4failed.
06:18 AM linuxcnc-build2: Build [#1668](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1668) of `00-checkin` 4failed.
06:27 AM -!- #linuxcnc-devel mode set to +v by ChanServ
08:01 AM travis-farmer is now known as travis_farmer
08:07 AM andypugh: pere: How’s your C++?
08:16 AM andypugh: Anyone else got some time, who knows C++ (I barely do)
08:16 AM andypugh: https://github.com/LinuxCNC/linuxcnc/issues/707
08:16 AM andypugh: I am going to move onto a different bug for an hour or so, in my own familiar C code.
08:20 AM rmu: andypugh: what do you mean with "complex numbers"?
08:20 AM rmu: *looking*
08:21 AM rmu: really complex numbers.
08:21 AM andypugh: He uses std::complex to represent coordinates. So we are machining in the Argand diagram
08:26 AM rmu: so if i understand correctly, the problem is that z40 and z39.999 yields different result and the 39.999 is very wrong?
08:28 AM -!- #linuxcnc-devel mode set to +v by ChanServ
08:33 AM andypugh: No, 39.9999 is right and 40 is very wrong
08:33 AM rmu: ok
08:33 AM andypugh: G72 is a lathe roughing cycle.
08:33 AM andypugh: (It’s possibly a bit unclear as I am plotting in a lmill config)
08:34 AM rmu: i have no idea about cnc lathe operation. but i do know that you are not supposed to inherit std::list, WHY THE HELL
08:34 AM rmu: sometime in the not so far future, the whole codebase has to be fed through clang-format and blacken
08:34 AM andypugh: Leaving that aside…. How would you go about working out whether the p that is passed in is different in the two cases?
08:35 AM rmu: it is a pointer to a segment, so perhaps print contents of the segment
08:35 AM rmu: whatever that is. line 61
08:36 AM andypugh: I barely know how to print in C++ I only speak “printf”
08:37 AM rmu: printf is fine
08:37 AM andypugh: I think that p is a pointer to a list, and don’t know how to find the size of the list.
08:37 AM rmu: g7x is the list itself
08:38 AM rmu: p points to somewhere hopefully in that list
08:39 AM rmu: size() should get the size of the list, but there is no easy way to tell the index of p into the list
08:39 AM rmu: IIRC
08:40 AM andypugh: Are you in a position to do any testing?
08:48 AM pere: andypugh: my C++ is ok. :)
08:50 AM rmu: andypugh: not now maybe in 3-4 hours
08:50 AM rmu: but thas is really some strange code, even recursive
08:51 AM andypugh: OK. Though I _really_ need to get 2.9 pushed out today, and there is a long, long process to get the files in the right places.
08:52 AM andypugh: G72 is a pretty interesting puzzle. It leads to interesting code. I did it in Python and that was recursive and fun too.
08:54 AM rmu: so what direction are the axis pointing to?
08:54 AM rmu: imaginary is from center?
08:58 AM rmu: do i understand correctly that 40 skips all roughing passes?
08:58 AM rmu: except the last?
09:05 AM rmu: andypugh: maybe that is the problem? https://github.com/LinuxCNC/linuxcnc/commit/e39f078b65c8801568419e0ff36526d062363d77#diff-64771623f87e913e9f863b1120a7f942237fe386a043865952bcb921c2d931f3L667
09:05 AM andypugh: rmu: Yes
09:06 AM andypugh: Typically, yes.
09:07 AM andypugh: That change is in 2.9. I recognise the code
09:07 AM rmu: it adds tolerance to the comparison whereas the rest of the change just replaces a fixed constant
09:08 AM andypugh: I can try it…
09:09 AM pere: andypugh: why do 2.9 have to be pushed out today?
09:12 AM pere: andypugh: is there a tests/ script to trigger the problem at hand?
09:13 AM andypugh: pere: Well, I want to get a bugfix into the version that is in Debian stable, and to do that I think that I need to have the fix in the version in unstable, and I want the version in unstable to be numbered with a real number.
09:13 AM pere: right.
09:13 AM andypugh: pere: Just load sim-axs-lathe and run the sample code in the issue report
09:14 AM pere: I guess I will start writing a tests/ script, then.
09:14 AM andypugh: And tomorrow night I am flying to Stuttgart without my main dev PCs…..
09:16 AM andypugh: rmu: I tried without the tolerance, and with the sign of the tolerance changed, and it was the same result.
09:18 AM rene-dev5: andypugh Did you manage to book a hotel?
09:18 AM rene-dev5: looking at the issue now, maybe I can help.
09:21 AM rmu: hmm
09:25 AM andypugh: rene-dev5: Yes, I have a hotel.
09:25 AM andypugh: Arrive late thirsday night, I might, or might not, pop into the workshop on the way to the hotel.
09:25 AM pere: "rs274 -g test.ngc" reproduce the problem.
09:27 AM andypugh: pere: I am slightly surprised by that, I wasn’t aware that the SAI understood G72
09:27 AM pere: Do "rs274 -g tests/interp/g71-endless-loop/g71-endless-loop.ngc" still give an endless loop for you?
09:29 AM andypugh: No, that test passes
09:33 AM pere: good. I guess it got fixed since I built my debs.
09:36 AM pere: andypugh: if the test passes, the xfail and skip files should be removed.
09:37 AM andypugh: pere: Yes, the command-line test does roduce very different output
09:37 AM andypugh: ah, wait, I didn’t know it had a skip
09:38 AM pere: <URL: https://github.com/LinuxCNC/linuxcnc/pull/2673 > is a new test to trigger this problem. xfail for now.
09:43 AM pere: note, I used the output from the 39.999 file as the expected output. I guess it might be slightly wrong.
09:44 AM andypugh: g71-endless-loop fails too, without the skip / xfail
09:46 AM pere: right. still unsolved, then.
09:49 AM -!- #linuxcnc-devel mode set to +v by ChanServ
09:51 AM Roguish: Andypugh: go for the freeze. well done.
09:51 AM pere: running ./debian/configure no-docs; debuild on bookworm failed for me.
09:51 AM andypugh: Roguish: Two serious bugs. Well, three it turns out, remain. Two with the G71 / G72 cycles.
09:52 AM andypugh: pere: I have a feeling that Chris Morley might have broken it, despite my warnings on the mailing list
09:53 AM pere: look like halcompile do not understand s64. not quite sure what is going on here. might be my dirty git repo.
09:53 AM andypugh: yeah, need to make clean to build 2.9
09:54 AM andypugh: The buildbot fails: http://buildbot.linuxcnc.org/buildbot/grid
09:56 AM Roguish: andypugh. I am starting some contracting/consulting work with this company: https://verdagy.com/
09:58 AM andypugh: Got to beat making it from petrochemicals
09:59 AM pere: andypugh: is the endless loop also a release critical bug?
10:00 AM andypugh: Well, it would have been at 9am this morning...
10:00 AM pere: hehe
10:00 AM andypugh: I am tempted to document a known fragility…
10:01 AM pere: debuild after a proper clean worked better. :)
10:06 AM linuxcnc-build2: Build [#1590](http://buildbot2.highlab.com/buildbot/#builders/14/builds/1590) of `10-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
10:07 AM linuxcnc-build2: Build [#1591](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1591) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
10:33 AM linuxcnc-build2: Build [#1595](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1595) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 8completed with warnings.
10:34 AM andypugh: I only have the G71 / G72 bugs left.
10:45 AM linuxcnc-build: build #3885 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3885
10:46 AM pere: I have had a look at the g7x code, and I lack too much knowledge about the code base to get anywhere before your deadline.
10:50 AM andypugh: TBH it barely touches the rest of the codebase, that’s partly what is confusing me ;-)
10:51 AM linuxcnc-build2: Build [#1669](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1669) of `00-checkin` 3completed successfully.
11:06 AM linuxcnc-build: build #10303 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10303
11:34 AM andypugh: Well, I have something to go on. The “dive” function is being fed a +40 value, but there are only -40 numbers in the G-code. I suspect a missing abs in a denominator.
11:48 AM rmu: hmm. looks like it behaves that way if z of second move is <= z of first move
11:49 AM rmu: e.g. going from z-40 to z-50. that suggests it doesn't have to do with tolerances
12:18 PM rmu: andypugh: in the failing case, imag(back->ep()) is positive here https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/rs274ngc/interp_g7x.cc#L730 vs. in the working case it is negative
12:19 PM andypugh: Yes, very puzzling.
12:19 PM rmu: (40 vs. -39.999)
12:19 PM rmu: so where does that come from
12:21 PM andypugh: I tracked imag(back) all the way through oid g7x::pocket( and found that in both cases the initial sign is wrong, but in the Pass” case the sign is flipped in the “swap” routine
12:21 PM andypugh: Are you running 2.9 or 2.10?
12:21 PM rmu: 2.9
12:22 PM rmu: convert_g7x calls do_g71 and there it seems to be already wrong
12:23 PM andypugh: Change the condition in line 603 from > to >= and then it works
12:23 PM rmu: i should really run that in the debugger
12:23 PM andypugh: But….. if you then try to use 40.0001 instead of 39.9999 _that_ breaks.
12:24 PM rmu: this line? https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/rs274ngc/interp_g7x.cc#L602
12:24 PM rmu: somewhere a sign is lost...
12:24 PM andypugh: yes
01:16 PM pere: g7x::swap() will flip both x and z in the successful case, but only flip z in the unsuccessful case. Perhaps this is the source of the sign flip?
01:43 PM rmu: what about this https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/rs274ngc/interp_g7x.cc#L194
01:43 PM rmu: i think it should look if in "swapped"
01:43 PM rmu: in non-working case the return 1 is taken
01:46 PM rmu: did this code ever work?
01:51 PM linuxcnc-build2: Build [#1597](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1597) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 4failed.
01:55 PM linuxcnc-build: build #3485 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3485 blamelist: andypugh <andy@bodgesoc.org>
02:00 PM pere: hard to tell when there were no tests written for it in the code.
02:03 PM rmu: this code is way too clever
02:11 PM linuxcnc-build2: Build [#1671](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1671) of `00-checkin` 4failed.
02:13 PM rmu: i suspect that this never worked
02:26 PM rmu: the code is from dec 2019, the bug from april 2020
02:27 PM linuxcnc-build2: Build [#1593](http://buildbot2.highlab.com/buildbot/#builders/14/builds/1593) of `10-rip.debian-10-buster-rtpreempt-amd64` 4failed.
02:27 PM linuxcnc-build2: Build [#1594](http://buildbot2.highlab.com/buildbot/#builders/7/builds/1594) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
02:52 PM linuxcnc-build2: Build [#1598](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1598) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 8completed with warnings.
03:02 PM linuxcnc-build: build #3887 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3887 blamelist: andypugh <andy@bodgesoc.org>
03:16 PM pere: rmu: could be. does not really matter, it should work. :)
03:19 PM andypugh: rmu: The code largely works.
03:19 PM andypugh: But fails with certain inputs.
03:24 PM pere: perhaps we can make tests with the working cases and the failing inputs, to ensure it keep working for the working ones while we fix the broken ones?
03:29 PM linuxcnc-build2: Build [#1599](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1599) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 4failed.
03:33 PM rmu: andypugh: to me it seems the code is failing for g72 if your end-Z is larger than your start-Z
03:33 PM rmu: larger or equal
03:34 PM andypugh: There is a bit of a hint about that in the G71 issue, in that he made it work by reversing the direction
03:35 PM andypugh: I don’t reallu know enough about the cycle to work out if that is reasonable.
03:35 PM pere: look like it is the same pocket() code that cause the endless loop for g71.
03:36 PM rmu: i don't know anything :)
03:48 PM pere: adding cout lines, I suspect the endless loop is a floating point rounding issue.
03:48 PM pere: pocket(3, (-14.04,-3.06472), 1, 0x55df3b4a0a50)
03:48 PM pere: 40 N..... STRAIGHT_FEED(3.0647, 0.0000, -14.0400, 0.0000, 0.0000, 0.0000)
03:48 PM pere: 41 N..... STRAIGHT_FEED(3.0647, 0.0000, -14.0400, 0.0000, 0.0000, 0.0000)
03:48 PM rmu: issue number?
03:49 PM pere: #1146
03:49 PM rmu: found it
03:49 PM pere: tests/interp/g71-endless-loop/
03:49 PM rmu: i managed to provoke endless loops with my experiments re issue 707
03:49 PM pere: I suspect the .00002 difference is the wanted movement, but it is too small for the code to try to do anything.
03:53 PM rmu: pere: try G01 X9 Z0 followed by G01 X10 Z-14 works, if you change X9->X10 and X10->X9 endless loop
03:53 PM rmu: doesn't look like rounding issue, smells like same issue like G72
03:54 PM pere: aha
03:59 PM rmu: i like the code. really. throw(std::string("How did we get here?"));
04:00 PM rmu: andypugh: is "climb" and "dive" usual CNC lathe lingo?
04:01 PM andypugh: No. Not as far as I know.
04:01 PM andypugh: But it’s clear enoug
04:02 PM linuxcnc-build: build #3647 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3647 blamelist: andypugh <andy@bodgesoc.org>
04:02 PM linuxcnc-build: build #10305 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10305 blamelist: andypugh <andy@bodgesoc.org>
04:13 PM rmu: it seems it really only depends on start/endpoint and not on path in between
04:14 PM rmu: i'm not sure why this "swapping" has to happen
04:19 PM andypugh: I think that it is related to using the same code for G71 and G72. But I could be wrong.
04:19 PM andypugh: Ideally such a canned cycle would be cooedinate agnostoc,and could run in the AW plane…
04:20 PM rmu: it uses complex numbers with Z real and X imag and a bit-field that records mirrored and rotated coordinates. no idea why.
04:21 PM andypugh: I am just about ready to push the new tag and start the release builds. You have about 30 minutes while my test docs build runs :-)
04:21 PM rmu: why the mirroring is there. that seems to be involved in these problems
04:21 PM rmu: no i give up :)
04:22 PM andypugh: I think that the first qeuastion is why the initial coordinate comes in with the wrong sign.
04:23 PM pere: rmu: I guess it uses complex to save code and space.
04:24 PM linuxcnc-build: build #3486 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3486 blamelist: Petter Reinholdtsen <pere@hungry.com>, andypugh <andy@bodgesoc.org>
04:24 PM rmu: pere: it doesn't really use complex math, so a struct with proper names would have sufficed
04:24 PM pere: I agree. but why make a struct when complex will do. :)
04:24 PM pere: (perhaps to avoid confusing co-developers. :)
04:24 PM rmu: to make people think about what minus complex conjugate means
04:33 PM linuxcnc-build: build #3888 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3888 blamelist: Petter Reinholdtsen <pere@hungry.com>, andypugh <andy@bodgesoc.org>
04:51 PM linuxcnc-build: build #3648 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3648 blamelist: Petter Reinholdtsen <pere@hungry.com>, andypugh <andy@bodgesoc.org>
04:51 PM linuxcnc-build: build #10306 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10306 blamelist: Petter Reinholdtsen <pere@hungry.com>, andypugh <andy@bodgesoc.org>
05:02 PM andypugh: My own build seems to be getting stuck at (32610 entries)
05:02 PM andypugh: Updating po/cs.po: 2 translated messages, 1 fuzzy translation, 32607 untranslated messages.
05:02 PM andypugh: Updating po/da.po: 1 translated message, 32609 untranslated messages.
05:02 PM andypugh: Updating po/de.po: 21719 translated messages, 4943 fuzzy translations, 5948 untranslated messages.
05:10 PM linuxcnc-build: build #3487 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3487 blamelist: andypugh <andy@bodgesoc.org>
05:14 PM rigid: can anyone reproduce in axis, that the "program will exceed upper boundary of Z-axis" warning will repeat until the file is manually reloaded, even if all values have been corrected before?
05:14 PM rigid: i guess that's a bug
05:16 PM andypugh: rigid: Have you seen https://github.com/LinuxCNC/linuxcnc/commit/5c9a79d186ea5e8b64772c71694debaddb0005bb ?
05:16 PM rigid: andypugh: ah no. gotta pull. thank you
05:48 PM linuxcnc-build: build #3889 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3889 blamelist: andypugh <andy@bodgesoc.org>
06:07 PM linuxcnc-build: build #3649 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3649 blamelist: andypugh <andy@bodgesoc.org>
06:07 PM linuxcnc-build: build #10307 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10307 blamelist: andypugh <andy@bodgesoc.org>
06:08 PM andypugh: Yes but, _my_ buld says that all links are good!
06:15 PM Unterhaus_ is now known as Unterhausen
06:25 PM linuxcnc-build: build #3488 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3488 blamelist: andypugh <andy@bodgesoc.org>
06:36 PM linuxcnc-build: build #3890 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3890 blamelist: andypugh <andy@bodgesoc.org>
06:54 PM linuxcnc-build: build #3650 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3650 blamelist: andypugh <andy@bodgesoc.org>
06:54 PM linuxcnc-build: build #10308 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10308 blamelist: andypugh <andy@bodgesoc.org>
07:11 PM linuxcnc-build: build #3489 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3489 blamelist: andypugh <andy@bodgesoc.org>
07:51 PM linuxcnc-build: build #3891 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3891 blamelist: andypugh <andy@bodgesoc.org>
08:10 PM linuxcnc-build: build #3651 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3651 blamelist: andypugh <andy@bodgesoc.org>
08:10 PM linuxcnc-build: build #10309 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10309 blamelist: andypugh <andy@bodgesoc.org>
08:28 PM linuxcnc-build: build #3490 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/3490 blamelist: andypugh <andy@bodgesoc.org>
08:39 PM linuxcnc-build: build #3892 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3892 blamelist: andypugh <andy@bodgesoc.org>
08:56 PM linuxcnc-build: build #3652 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/3652 blamelist: andypugh <andy@bodgesoc.org>
08:56 PM linuxcnc-build: build #10310 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/10310 blamelist: andypugh <andy@bodgesoc.org>