Kinsey Moore commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/15#note_113937 I found a recommendation that when calling proc.kill(), you should follow it with proc.communicate() to ensure that all I/O is finalized and culled. This seems to keep the pipe count to almost exactly 3x jobs, but exposes other problems on my server. The 28c56t machine is not under any load but gitlab, but seems to be less performant than my server is. AArch64 toolchain build times are: - 8c16t(personal server): 13.75m - 28c56t: 22m - 8c16t VM(virtualbox on a laptop): 16m Something is definitely going on on that machine. Once I fixed the proc.communicate() issue, other issues start popping up on my server when the tester is coerced to run at 52 jobs: ``` [232/675] p:152 f:4 u:3 e:21 I:0 B:3 t:0 L:0 i:0 W:0 | powerpc/psim: psxcancel01.exe error: gdb.cfg:54: macro '%{rtems_version}' not found error: gdb.cfg:54: macro '%{rtems_version}' not found warning: switched to dry run due to errors error: gdb.cfg:54: macro '%{rtems_version}' not found error: gdb.cfg:54: macro '%{rtems_version}' not found error: gdb.cfg:54: macro '%{rtems_version}' not found error: gdb.cfg:54: macro '%{rtems_version}' not found error: gdb.cfg:60: macro '%{rtems_version}' not found error: gdb.cfg:60: macro '%{rtems_version}' not found error: gdb.cfg:60: macro '%{rtems_version}' not found error: gdb.cfg:60: macro '%{rtems_version}' not found [233/675] p:153 f:4 u:3 e:21 I:0 B:3 t:0 L:0 i:0 W:0 | powerpc/psim: psxchroot01.exe ... [249/675] p:170 f:4 u:4 e:21 I:0 B:3 t:0 L:0 i:1 W:0 | powerpc/psim: psxfatal01.exe error: config error: gdb.cfg:36: No 'target' defined [253/675] p:170 f:4 u:4 e:21 I:0 B:3 t:0 L:0 i:1 W:0 | powerpc/psim: psxfile01.exe [251/675] p:170 f:4 u:4 e:21 I:0 B:3 t:0 L:0 i:1 W:0 | powerpc/psim: psxfchx01.exe ``` -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/15#note_113937 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
