Hi All,

We had a hanging qemu process:


https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/1748

This is on ubuntu1804-arm-1.yocto.io.

I was able to ssh into the image on the worker with ssh root@192.168.7.2
and it looks to be hung during fs ltp tests. I've dumped some 
output below, I'm not too familiar with ltp so struggling to understand
where it is at.

The processes are still around so we may be able to save data from
them but the servers will be rebooted tomorrow during maint at which
point we'd lose this unless we ask Michael to defer.

It looks like the proc01 -m 128 is hanging.

Cheers,

Richard

root@qemuarm64:~# ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 1:45 init [5]
2 ? S 0:00 [kthreadd]
3 ? I< 0:00 [rcu_gp]
4 ? I< 0:00 [rcu_par_gp]
6 ? I< 0:00 [kworker/0:0H-events_highpri]
8 ? I< 0:00 [mm_percpu_wq]
9 ? S 0:00 [rcu_tasks_kthre]
10 ? S 0:00 [rcu_tasks_rude_]
11 ? S 0:00 [rcu_tasks_trace]
12 ? S 0:42 [ksoftirqd/0]
13 ? I 0:08 [rcu_preempt]
14 ? S 0:00 [migration/0]
15 ? S 0:00 [cpuhp/0]
16 ? S 0:00 [kdevtmpfs]
17 ? I< 0:00 [netns]
19 ? S 0:00 [oom_reaper]
20 ? I< 0:00 [writeback]
21 ? S 0:04 [kcompactd0]
54 ? I< 0:00 [kblockd]
55 ? I< 0:00 [blkcg_punt_bio]
56 ? I< 0:00 [md]
57 ? I< 0:06 [kworker/0:1H-kblockd]
58 ? I< 0:00 [rpciod]
59 ? I< 0:00 [kworker/u3:0]
60 ? I< 0:00 [xprtiod]
61 ? S 0:01 [kswapd0]
62 ? I< 0:00 [nfsiod]
63 ? I< 0:00 [cifsiod]
64 ? I< 0:00 [smb3decryptd]
65 ? I< 0:00 [cifsfileinfoput]
66 ? I< 0:00 [cifsoplockd]
68 ? S 0:05 [hwrng]
69 ? I< 0:00 [ttm_swap]
71 ? S 0:00 [khvcd]
73 ? I< 0:00 [raid5wq]
74 ? I< 0:00 [dm_bufio_cache]
75 ? I< 0:00 [ipv6_addrconf]
80 ? S 0:24 [jbd2/vda-8]
81 ? I< 0:00 [ext4-rsv-conver]
116 ? Ss 0:00 /sbin/udevd -d
445 ? Ss 0:00 /usr/bin/dbus-daemon --system
453 ? Ss 3:47 /usr/sbin/connmand
460 ? S 0:00 xinit /etc/X11/Xsession -- /usr/bin/Xorg :0 -br -pn
463 ? S 0:58 /usr/sbin/wpa_supplicant -u
467 ? S<sl 1:07 /usr/bin/Xorg :0 -br -pn
471 ? Ss 0:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
476 ? Ss 0:25 /usr/sbin/rpcbind
491 ? S 0:00 matchbox-window-manager -theme Sato -use_cursor yes
496 ? S 0:00 dbus-launch --sh-syntax --exit-with-session
497 ? Ss 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
514 ? Sl 0:00 /usr/libexec/at-spi-bus-launcher --launch-immediately
518 ? S 0:00 connman-applet
534 ? S 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
553 ? S 0:00 matchbox-desktop
554 ? S 10:50 matchbox-panel --start-applets showdesktop,windowselector --end-applets clock,,systray,startup-notify,notify
557 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon
621 ? S 1:41 /usr/libexec/gconfd-2
623 ? S 0:00 /usr/bin/settings-daemon
638 ? S 0:00 avahi-daemon: running [qemuarm64.local]
639 ? S 0:00 avahi-daemon: chroot helper
643 ? Ss 0:00 /usr/sbin/ofonod
648 ? Sl 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
650 ? Ss 1:22 /usr/sbin/crond
660 ? Ss 0:00 /bin/sh /bin/start_getty 115200 ttyAMA0 vt102
661 ? Ss 0:00 /bin/sh /bin/start_getty 115200 hvc0 vt102
662 tty1 Ss+ 0:00 /sbin/getty 38400 tty1
665 hvc0 Ss+ 0:00 /sbin/getty -L 115200 hvc0 vt102
666 ttyAMA0 Ss+ 0:00 -sh
7112 ? S 0:02 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
7113 ? S 0:00 /bin/sh /opt/ltp/runltp -f fs -p -q -r /opt/ltp -l /opt/ltp/results/fs -I 1 -d /opt/ltp
7155 ? S 0:00 /opt/ltp/bin/ltp-pan -q -e -S -a 7113 -n 7113 -p -f /opt/ltp/ltp-HZxaOUahq7/alltests -l /opt/ltp/results/fs -C /opt/ltp/output/LTP_RUN_ON-fs.failed -T /opt/ltp/output/LTP_RUN_ON-fs.tconf
9361 ? S 0:00 /sbin/syslogd -n -O /var/log/messages
9364 ? S 0:01 /sbin/klogd -n
11412 ? I 0:00 [kworker/u2:0-ext4-rsv-conversion]
11413 ? I 0:00 [kworker/u2:3-events_unbound]
11578 ? S 0:00 proc01 -m 128
11580 ? S 0:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
11581 pts/0 Ss 0:00 -sh
11585 pts/0 R+ 0:00 ps ax
27489 ? I 0:00 [kworker/0:1-cgroup_pidlist_destroy]
27490 ? I 0:55 [kworker/0:4-events]

root@qemuarm64:~# tail /opt/ltp/results/fs
ftest02 PASS 0
ftest03 PASS 0
ftest04 PASS 0
ftest05 PASS 0
ftest06 PASS 0
ftest07 PASS 0
ftest08 PASS 0
lftest01 PASS 0
writetest01 PASS 0
fs_di PASS 0
root@qemuarm64:~# tail /opt/ltp/output/LTP_RUN_ON-fs.failed

Lots in dmesg but the last bit shows handy timestamp:

[10052.451191] cgroup: fork rejected by pids controller in /ltp_pids_9/child2
[10052.500603] new mount options do not match the existing superblock, will be ignored
[10052.543519] cgroup: fork rejected by pids controller in /ltp_pids_9/child2
[10052.619108] new mount options do not match the existing superblock, will be ignored
[10052.733366] cgroup: fork rejected by pids controller in /ltp_pids_9/child2
[10052.942680] new mount options do not match the existing superblock, will be ignored
[10053.146175] cgroup: fork rejected by pids controller in /ltp_pids_9/child2
[10092.243267] input: virtual-device-ltp as /devices/virtual/input/input2
[10092.327062] input: virtual-device-ltp as /devices/virtual/input/input3
[10092.422283] input: virtual-device-ltp as /devices/virtual/input/input4
[10092.436818] input: virtual-device-ltp as /devices/virtual/input/input5
[10092.517318] input: virtual-device-ltp as /devices/virtual/input/input6
[10092.596125] input: virtual-device-ltp as /devices/virtual/input/input7
[11205.107302] ICMPv6: process `proc01' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead

Hi All,

We had a hanging qemu process:

https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1898

This is on debian10-ty-2.yocto.io.

I was able to ssh into the image on the worker with ssh root@192.168.7.2
and it looks to be hung during controller ltp tests. I've dumped some 
output below, I'm not too familiar with ltp so struggling to understand
where it is at.

The processes are still around so we may be able to save data from
them but the servers will be rebooted tomorrow during maint at which
point we'd lose this unless we ask Michael to defer.

Cheers,

Richard


root@qemux86-64:/opt/ltp/results# ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:03 init [5]
2 ? S 0:00 [kthreadd]
3 ? I< 0:00 [rcu_gp]
4 ? I< 0:00 [rcu_par_gp]
6 ? I< 0:00 [kworker/0:0H-events_highpri]
8 ? I< 0:00 [mm_percpu_wq]
9 ? S 0:00 [rcu_tasks_kthre]
10 ? S 0:00 [rcu_tasks_rude_]
11 ? S 0:00 [rcu_tasks_trace]
12 ? S 0:00 [ksoftirqd/0]
13 ? I 0:06 [rcu_preempt]
14 ? S 0:00 [migration/0]
15 ? S 0:00 [cpuhp/0]
16 ? S 0:00 [cpuhp/1]
17 ? S 0:00 [migration/1]
18 ? S 0:00 [ksoftirqd/1]
20 ? I< 0:00 [kworker/1:0H-events_highpri]
21 ? S 0:00 [cpuhp/2]
22 ? S 0:00 [migration/2]
23 ? S 0:00 [ksoftirqd/2]
25 ? I< 0:00 [kworker/2:0H-kblockd]
26 ? S 0:00 [cpuhp/3]
27 ? S 0:00 [migration/3]
28 ? S 0:00 [ksoftirqd/3]
30 ? I< 0:00 [kworker/3:0H-kblockd]
31 ? S 0:00 [kdevtmpfs]
32 ? I< 0:00 [netns]
34 ? S 0:00 [oom_reaper]
35 ? I< 0:00 [writeback]
36 ? S 0:07 [kcompactd0]
73 ? I< 0:00 [kblockd]
74 ? I< 0:00 [blkcg_punt_bio]
75 ? I< 0:00 [ata_sff]
76 ? I< 0:00 [md]
78 ? I< 0:00 [kworker/0:1H-kblockd]
79 ? I< 0:00 [rpciod]
80 ? I< 0:00 [kworker/u9:0]
81 ? I< 0:00 [xprtiod]
82 ? S 0:00 [kswapd0]
83 ? I< 0:00 [nfsiod]
84 ? I< 0:00 [cifsiod]
85 ? I< 0:00 [smb3decryptd]
86 ? I< 0:00 [cifsfileinfoput]
87 ? I< 0:00 [cifsoplockd]
89 ? I< 0:00 [acpi_thermal_pm]
91 ? S 0:00 [hwrng]
92 ? I< 0:00 [ttm_swap]
93 ? I< 0:00 [nvme-wq]
94 ? I< 0:00 [nvme-reset-wq]
95 ? I< 0:00 [nvme-delete-wq]
96 ? S 0:00 [scsi_eh_0]
97 ? I< 0:00 [scsi_tmf_0]
98 ? S 0:00 [scsi_eh_1]
99 ? I< 0:00 [scsi_tmf_1]
100 ? S 0:00 [scsi_eh_2]
101 ? I< 0:00 [scsi_tmf_2]
102 ? S 0:00 [scsi_eh_3]
103 ? I< 0:00 [scsi_tmf_3]
104 ? S 0:00 [scsi_eh_4]
105 ? I< 0:00 [scsi_tmf_4]
106 ? S 0:00 [scsi_eh_5]
107 ? I< 0:00 [scsi_tmf_5]
114 ? I< 0:00 [raid5wq]
115 ? I< 0:00 [dm_bufio_cache]
116 ? I< 0:00 [ipv6_addrconf]
124 ? S 0:03 [jbd2/vda-8]
125 ? I< 0:00 [ext4-rsv-conver]
160 ? Ss 0:00 /sbin/udevd -d
358 ? I< 0:00 [kworker/2:1H-kblockd]
525 ? Ss 0:00 /usr/bin/dbus-daemon --system
533 ? Ss 0:05 /usr/sbin/connmand
539 ? S 0:00 xinit /etc/X11/Xsession -- /usr/bin/Xorg :0 -br -pn
545 ? S 0:01 /usr/sbin/wpa_supplicant -u
548 ? S<sl 0:12 /usr/bin/Xorg :0 -br -pn
551 ? S 0:00 matchbox-window-manager -theme Sato -use_cursor no
556 ? S 0:00 dbus-launch --sh-syntax --exit-with-sessionsh-keygen -f "/home/pokybuild/.ssh/known_hosts" -R "192.168.7.2"
557 ? Ss 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
576 ? Sl 0:00 /usr/libexec/at-spi-bus-launcher --launch-immediately
580 ? Sl 0:00 connman-applet
602 ? S 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
612 ? Sl 0:00 matchbox-desktop
613 ? Sl 0:06 matchbox-panel --start-applets showdesktop,windowselector --end-applets clock,,systray,startup-notify,notify
616 ? S 0:00 /usr/libexec/gconfd-2
620 ? Ss 0:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
621 ? S 0:00 /usr/bin/settings-daemon
628 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon
629 ? Ss 0:00 /usr/sbin/rpcbind
700 ? S 0:00 /usr/libexec/bluetooth/bluetoothd
712 ? Sl 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
732 ? S 0:00 avahi-daemon: running [qemux86-64.local]
733 ? S 0:00 avahi-daemon: chroot helper
737 ? Ss 0:00 /usr/sbin/ofonod
741 ? Ss 0:00 /usr/sbin/crond
750 ? Ss 0:00 /bin/sh /bin/start_getty 115200 ttyS0 vt102
751 ? Ss 0:00 /bin/sh /bin/start_getty 115200 ttyS1 vt102
752 tty1 Ss+ 0:00 /sbin/getty 38400 tty1
755 ttyS0 Ss+ 0:00 /sbin/getty -L 115200 ttyS0 vt102
756 ttyS1 Ss+ 0:00 -sh
760 ? I< 0:00 [kworker/1:1H-kblockd]
1087 ? I< 0:00 [kworker/3:1H-kblockd]
3886 ? D 0:00 cgroup_xattr
3887 ? R 0:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
3888 pts/0 Ss 0:00 -sh
3892 ? I 0:00 [kworker/u8:2-events_unbound]
3906 ? I 0:00 [kworker/u8:0-events_unbound]
3911 ? S 0:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
3912 pts/1 Ss+ 0:00 -sh
3918 pts/0 R+ 0:00 ps ax
4451 ? I 0:00 [kworker/2:1-mm_percpu_wq]
4454 ? I 0:00 [kworker/1:0-rcu_gp]
4569 ? I 0:00 [kworker/2:4-rcu_gp]
4620 ? I 0:00 [kworker/0:2-rcu_gp]
5157 ? S 0:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 -B
5158 ? S 0:00 /bin/sh /opt/ltp/runltp -f controllers -p -q -r /opt/ltp -l /opt/ltp/results/controllers -I 1 -d /opt/ltp
5200 ? S 0:00 /opt/ltp/bin/ltp-pan -q -e -S -a 5158 -n 5158 -p -f /opt/ltp/ltp-qYESo05pbN/alltests -l /opt/ltp/results/controllers -C /opt/ltp/output/LTP_RUN_ON-controllers.failed -T /opt/ltp/output/LTP_RUN_ON-controllers.tconf
12503 ? I 0:00 [kworker/u8:1-events_unbound]
12921 ? I 0:00 [kworker/1:2-mm_percpu_wq]
12961 ? I 0:00 [kworker/0:0-events]
13462 ? I 0:00 [kworker/3:3-rcu_gp]
14966 ? S 0:00 /sbin/syslogd -n -O /var/log/messages
14969 ? S 0:01 /sbin/klogd -n
21420 ? I 0:00 [kworker/3:0-mm_percpu_wq]

root@qemux86-64:/opt/ltp/results# ls -la
total 172
drwxr-xr-x 2 root root 4096 May 11 10:55 .
drwxr-xr-x 13 root root 4096 May 11 10:55 ..
-rw-r--r-- 1 root root 6207 May 11 10:55 containers
-rw-r--r-- 1 root root 20494 May 11 10:58 controllers
-rw-r--r-- 1 root root 2466 May 11 10:46 dio
-rw-r--r-- 1 root root 561 May 11 10:46 io
-rw-r--r-- 1 root root 969 May 11 10:53 ipc
-rw-r--r-- 1 root root 1106 May 11 10:22 math
-rw-r--r-- 1 root root 5255 May 11 10:53 mm
-rw-r--r-- 1 root root 493 May 11 10:55 nptl
-rw-r--r-- 1 root root 901 May 11 10:55 pty
-rw-r--r-- 1 root root 1106 May 11 10:55 sched
-rw-r--r-- 1 root root 91210 May 11 10:40 syscalls

root@qemux86-64:/opt/ltp/results# tail controllers
cpuset_exclusive CONF 32
cpuset_hierarchy CONF 32
cpuset_syscall CONF 32
cpuset_sched_domains CONF 32
cpuset_load_balance CONF 32
cpuset_hotplug CONF 32
cpuset_memory CONF 32
cpuset_memory_pressure CONF 32
cpuset_memory_spread CONF 32
cpuset_regression_test FAIL 6


root@qemux86-64:/opt/ltp/results# tail ../output/LTP_RUN_ON-controllers.failed
cgroup_fj_stress_net_prio_10_3_each cgroup_fj_stress.sh net_prio 10 3 each
cgroup_fj_stress_net_prio_1_200_each cgroup_fj_stress.sh net_prio 1 200 each
cgroup_fj_stress_net_prio_200_1_each cgroup_fj_stress.sh net_prio 200 1 each
cpuacct_1_1 cpuacct.sh 1 1
cpuacct_1_10 cpuacct.sh 1 10
cpuacct_10_10 cpuacct.sh 10 10
cpuacct_1_100 cpuacct.sh 1 100
cpuacct_100_1 cpuacct.sh 100 1
cpuacct_100_100 cpuacct.sh 100 100
cpuset_regression_test cpuset_regression_test.sh

Noted. Let me know when swatbot account is ready.

BTW, is there a timetable for the SWAT rotation?
So we can check the schedule and inform ahead if there is any needs for reschedule


Chee Yang

Hello Lee Chee,

SWAT duty will rotate from me to you at the end of this Friday.

Please reply to let me know whether you will be able to work on this
task next week.

I'll be available to walk you through the swatbot process on Monday,
don't hesitate to contact me by email or on IRC.
I'll create your swatbot account soon.

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hello,

On 03/05/2021 19:34:55+0000, Larson, Chris wrote:

Apolzogies, I'm swamped this week and am dealing with an injured kid, I'll need to shift my position to a future week again.

That's OK, I didn't do a great job last week and I'll handle SWAT this
week.


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Apologies, I'm swamped this week and am dealing with an injured kid, I'll need to shift my position to a future week again.

-Chris

Hello Christopher,

SWAT duty will rotate from me to you at the end of this Friday.

Please reply to let me know whether you will be able to work on this
task next week.

I'll be available to walk you through the swatbot process on Monday,
don't hesitate to contact me by email or on IRC.
I'll create your swatbot account soon.

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hello,

Here are the statistics for last week. Naveen was on SWAT duty.

168 failures were triaged:

* 168 by Naveen
- 73 for an issue in opkg-utils-native
- 22 for check-layer-nightly issues Richard was working on
- 13 for go-runtime source fetching issues
- 8 for an issue in epiphany
- 7 for issues already solved at the time of triage
- 7 for individual issues reported on the mailing list
- 6 for space issues on the tmpfs
- 5 for kernel config warnings
- 4 for a build started for ebugging purposes
- 4 occurrences of new bug 14353
- 1 occurrence of new bug 14352
- 1 occurrence of new bug 14359
- 1 occurrence of new bug 14360
- 8 new occurrences of bug 14128
- 3 new occurrences of bug 14251
- 2 new occurrences of bug 14177
- 1 new occurrence of bug 14002
- 1 new occurrence of both bug 14163 and 14244
- 1 new occurrence of bug 14353 and 14354

Regards,

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

To be clear that was the end of Friday 23rd. I see you got the email on
Saturday ;)

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Noted.

Thanks,
Naveen

Hello Naveen,

SWAT duty will rotate from you to me at the end of this Friday, thanks
for your work!

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hi All,

I wanted to give a headsup that we're seeing out of space issues on the autobuilder.
The cause is the tmpfs change for qemu images we added recently. It appears 'someone'
forgot to remove the files from the tmpfs after testing completed. This is the cause
of the space errors on debian8 in particular. Was a bit puzzled for a while as it
had plenty of space!

I'll work out a patch to clean up the files after runqemu completes! Just wanted
to ensure people knew the reason and that it should get fixed soon. It has 
implications for backporting those patches to other releases.

Cheers,

Richard

Hello,

Here are the statistics for last week. Alejandro was still on SWAT duty.

415 failures were triaged:

* 221 by Alejandro
- 184 for an issue with a gnutls change that was already worked on
- 16 for the gcc upgrade to 10.3.0 that was then fixed by Richard
- 7 for the go upgrade patch, the fix is still being worked on
- 4 for cancelled builds without any failure
- 2 occurrences of new bug 14345
- 1 occurrence of new bug 14346
- 2 new occurrences of bug 13802
- 2 new occurrences of bug 14029
- 2 new occurrences of bug 14251
- 1 new occurrence of bug 14230

* 194 by Richard
- 180 for a patch he fixed
- 8 for an issue in a patch for prserv he reported on the list
- 6 for an issue with ab-helper changes he reported on the list

Regards,

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hello Alexandre,
I have received this email and will take over tomorrow morning.

Thanks,
Naveen

Hello Naveen,

SWAT duty will rotate from Alejandro to you at the end of this Friday.

Please reply to let me know whether you will be able to work on this
task.

I'll be available to walk you through the process on Monday, don't
hesitate to contact me by email or on IRC.

Thanks!

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hello,

Here are the statistics for last week. Alejandro was on SWAT duty.

10 failures were triaged:

* 6 by Alejandro
- 1 occurrence of new bug 14341
- 2 new occurrences of bug 14251
- 1 new occurrence of bug 14201
- 1 new occurrence of bug 14230
- 1 new occurrence of bug 14295

* 4 by Richard
- 4 for an experimental build

There was an issue with the autobuilder/swatbot reporter code that
prevented more failures to be logged, hence the low number.

Regards,

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hi All,

We've had some issues with the connection between swatbot and the autobuilder 
meaning that swatbot wasn't getting build entries or updates for some periods
over the last few weeks.

With some help from Michael we figured out the issue and I've updated the 
autobuilder notifier code so it that it reconnects properly if logins expire.

Unfortunately we don't yet have a way to replay lost builds data back to swatbot
to bring it's database back in sync.

Over the weekend I did test:

gcc 11 - issues were reported to Khem on the mailing list
gcc 10.3 - there were several failures from this and we're now testing revised patches

Cheers,

Richard

Hello,

Here are the statistics for last week. Paul was on SWAT duty.

21 failures were triaged:

* 18 by Paul
- 1 occurrence of new bug 14331
- 4 new occurrences of bug 14329
- 3 new occurrences of bug 14029
- 2 new occurrences of bug 13802
- 2 new occurrences of bug 14294
- 1 new occurrence of bug 14163
- 1 new occurrence of bug 14200
- 1 new occurrence of bug 14274
- 1 for a new occurence of 14177, 14294 and 14296
- 1 for the valgrind update he replied to on the list
- 1 failure because of a previous build failure

* 1 by Richard
- 1 for a build that was not for SWAT

* 2 by Michael
- 2 builds to test the infra

Regards,

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hello Alejandro,

SWAT duty will rotate from Paul to you at the end of this Friday.

Please reply to let me know whether you will be able to work on this
task.

I'll be available to walk you through the process on Monday, don't
hesitate to contact me by email or on IRC.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hello,

Here are the statistics for last week. Oleksiy was on SWAT duty.

244 failures were triaged:

* 140 by Oleksiy
- 6 occurrences of new bug 14313
- 4 occurrences of new bug 14329
- 2 occurrences of new bug 14320
- 1 occurrence of new bug 14314
- 1 occurrence of new bug 14321
- 4 new occurrences of bug 14029
- 2 new occurrences of bug 14177
- 2 new occurrences of bug 14200
- 2 new occurrences of bug 14230
- 1 new occurrence of bug 13054
- 1 new occurrence of bug 13802
- 1 new occurrence of bug 14128
- 1 new occurrence of bug 14163
- 1 new occurrence of bug 14230
- 1 new occurrence of bug 14254
- 1 new occurrence of bug 14294
- 28 for an issue in util-linux
- 27 for an issue with a libglib-2.0 patch
- 7 for an issue with the run-postinsts patch
- 4 for reproducibility issues following a valgrind upgrade
- 3 for an issue with an mpv patch
- 36 builds cancelled with no other error
- 4 failures in meta-oe, not for SWAT

* 81 by Richard
- 81 for a in his own patch that he fixed

* 23 by me
- 23 builds cancelled with no other error

Regards,

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com