Issues found in current buildd logs for dvtm:
In the last run, there were no currently detectable issues found in the logs of dvtm.Scanned logs (date is the date the log was generated, not the date it was scanned):
- alpha 0.15+40.g311a8c0-1 2019-01-03 11:15
- amd64 0.15+40.g311a8c0-1 2019-01-03 12:11
- arm64 0.15+40.g311a8c0-1 2019-01-03 10:51
- armel 0.15+40.g311a8c0-1 2019-01-03 11:32
- armhf 0.15+40.g311a8c0-1 2019-01-03 14:24
- hppa 0.15+40.g311a8c0-1 2019-01-03 11:32
- i386 0.15+40.g311a8c0-1 2019-01-03 14:11
- ia64 0.15+40.g311a8c0-1 2019-01-03 10:51
- loong64 0.15+40.g311a8c0-1 2023-08-17 09:56
- m68k 0.15+40.g311a8c0-1 2019-01-03 11:06
- mips64el 0.15+40.g311a8c0-1 2019-01-03 10:42
- powerpc 0.15+40.g311a8c0-1 2019-01-03 14:16
- ppc64 0.15+40.g311a8c0-1 2019-01-03 11:08
- ppc64el 0.15+40.g311a8c0-1 2019-01-03 11:09
- riscv64 0.15+40.g311a8c0-1+b1 2024-01-02 06:30
- s390x 0.15+40.g311a8c0-1 2019-01-03 11:07
- sh4 0.15+40.g311a8c0-1 2019-01-03 12:35
- sparc64 0.15+40.g311a8c0-1 2019-01-03 10:53
- x32 0.15+40.g311a8c0-1 2019-01-03 18:25