#linuxcnc-devel Logs

Sep 08 2022

02:58 AM pere: Look like the missing armel and armhf binaries and the failing test will block linuxcnc from migration to testing. Sorry about that. A fix/workaround is in 40958f5769215a68f4f53f75d08be5306cb39fc4, after consulting with the debian CI maintainers who want the current behaviour to ensure packages building only arch:all package get tested on as many architectures as possible.
03:05 AM pere: I did manage to get the linuxcnc-test script working in ci.debian.org, but the rs274-test script seem to fail. I adjusted it to print the error messages on the next upload, and its failure will be ignored due to its 'flaky' flag, so it should not block propagation. the passing linuxcnc-test should bring propagation time down to two days.
03:54 AM pere: hi
04:41 AM Tom_L: hi
12:59 PM -!- #linuxcnc-devel mode set to +v by ChanServ
03:29 PM -!- #linuxcnc-devel mode set to +v by ChanServ
03:38 PM -!- #linuxcnc-devel mode set to +v by ChanServ
04:14 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:37 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:41 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:42 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:50 PM -!- #linuxcnc-devel mode set to +v by ChanServ
09:06 PM -!- #linuxcnc-devel mode set to +v by ChanServ