Total jobs: 285
Total errors: 71 (24.91%)
LAVA errors: 0 (0.00%)
Test errors: 8 (2.81%)
Job errors: 19 (6.67%)
Infra errors: 44 (15.44%)
Canceled jobs: 0 (0.00%)
Device type: beaglebone-black
Total jobs: 43
Total errors: 0 (0.00%)
Device type: dragonboard-845c
Total jobs: 15
Total errors: 1 (6.67%)
Error type: Infrastructure
Error count: 1 (6.67%)
Error: Reboot failed
Count: 1 (6.67%)
IDs:
dragonboard-845c-02:
4105290
Device type: dragonboard-410c
Total jobs: 11
Total errors: 10 (90.91%)
Error type: Job
Error count: 10 (90.91%)
Error: No match for error type 'Job', message 'Unable to update image rootfs: 'mount: mount exited with status 32: mount: /sysroot: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.\n dmesg(1) may have more information after failed mount system call.''
Count: 10 (90.91%)
IDs:
dragonboard-410c-02:
4105188 4105196 4105279 4105283 4105289
4105296 4105299 4105330 4105392 4105408
Device type: x86
Total jobs: 27
Total errors: 6 (22.22%)
Error type: Test
Error count: 6 (22.22%)
Error: lava-test-shell timed out
Count: 6 (22.22%)
IDs:
x86-01:
4105217 4105303 4105318 4105320 4105339
4105344
Device type: qemu
Total jobs: 4
Total errors: 0 (0.00%)
Device type: x15
Total jobs: 178
Total errors: 54 (30.34%)
Error type: Test
Error count: 2 (1.12%)
Error: No match for error type 'Test', message 'Network not able to ping; job exit'
Count: 2 (1.12%)
IDs:
x15-01:
4105270 4105378
Error type: Infrastructure
Error count: 43 (24.16%)
Error: No match for error type 'Infrastructure', message 'wait-device-boardid timed out after 858 seconds'
Count: 1 (0.56%)
IDs:
x15-01:
4105370
Error: No match for error type 'Infrastructure', message 'wait-device-boardid timed out after 821 seconds'
Count: 1 (0.56%)
IDs:
x15-01:
4105368
Error: No match for error type 'Infrastructure', message 'bootloader-commands timed out after 285 seconds'
Count: 3 (1.69%)
IDs:
x15-01:
4100468 4101294 4101580
Error: No match for error type 'Infrastructure', message 'bootloader-commands timed out after 286 seconds'
Count: 37 (20.79%)
IDs:
x15-01:
4100414 4100432 4100480 4100605 4100622
4100744 4100786 4100796 4100820 4100866
4100886 4100894 4100902 4100921 4100953
4100985 4100997 4101011 4101078 4101100
4101138 4101150 4101172 4101198 4101219
4101229 4101261 4101273 4101374 4101377
4101404 4101436 4101451 4101499 4101532
4101538 4101560
Error: Connection closed
Count: 1 (0.56%)
IDs:
x15-01:
4100780
Error type: Job
Error count: 9 (5.06%)
Error: No match for error type 'Job', message 'login-action timed out after 275 seconds'
Count: 1 (0.56%)
IDs:
x15-01:
4101527
Error: No match for error type 'Job', message 'login-action timed out after 262 seconds'
Count: 1 (0.56%)
IDs:
x15-01:
4101401
Error: wait for prompt timed out
Count: 6 (3.37%)
IDs:
x15-01:
4100423 4100459 4100475 4101106 4101342
4101397
Error: No match for error type 'Job', message 'login-action timed out after 271 seconds'
Count: 1 (0.56%)
IDs:
x15-01:
4101097
Device type: frdm-kw41z
Total jobs: 2
Total errors: 0 (0.00%)
Device type: frdm-k64f
Total jobs: 3
Total errors: 0 (0.00%)
Device type: docker
Total jobs: 2
Total errors: 0 (0.00%)
Hello lkft-triage,
How are you?
My name is Noel Dosi, I have a profitable business proposal which I
would love to discuss with you. Please get back to me if you are
interested, so that I would give you the full details.
Regards,
Noel Dosi
Hi folks,
During LPC Linus brought up a concern that linux-next is too lightly
tested, and pull requests that end up reaching him still might be
functionally broken (and kill his laptop).
linux-next works great as an integration branch as far as conflicts
between trees and build issues go, but it's volatile state makes it very
difficult to test it. For example, a single for-next branch that wasn't
tested can ruin testing for everyone else.
I've proposed a new "linus-next" tree which is composed of pull
requests that were sent to Linus. This (in theory) will give us a higher
quality tree that will be composed only of pull requests that were sent
to Linus but not picked up yes. Basically, we'll be frontrunning Linus
as he goes on with his merges.
The tree is located at
git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linus-next.git and
the branch is 'linus-next'.
As far as testing goes, I think that it should be equivalent to what
Linus's tree gets, but I'm open to suggestions.
Thank you!
--
Thanks,
Sasha
Total jobs: 180
Total errors: 77 (42.78%)
LAVA errors: 0 (0.00%)
Test errors: 63 (35.00%)
Job errors: 5 (2.78%)
Infra errors: 7 (3.89%)
Canceled jobs: 2 (1.11%)
Device type: hi6220-hikey-r2
Total jobs: 50
Total errors: 33 (66.00%)
Error type: Infrastructure
Error count: 4 (8.00%)
Error: fastboot-flash-action timed out
Count: 3 (6.00%)
IDs:
hikey-6220-r2-01:
7922664 7924475
hikey-6220-r2-02:
7924460
Error: No match for error type 'Infrastructure', message 'Failed to clean after job'
Count: 1 (2.00%)
IDs:
hikey-6220-r2-02:
7922668
Error type: Test
Error count: 27 (54.00%)
Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed'
Count: 24 (48.00%)
IDs:
hikey-6220-r2-01:
7921660 7923764 7923789
hikey-6220-r2-02:
7921637 7921642 7922656 7923763 7923769
7923790 7923793
hikey-6220-r2-05:
7921627 7921628 7921634 7921635 7921636
7921638 7921639 7921641 7922625 7922627
7922659 7922660 7922665 7923648
Error: No match for error type 'Test', message 'tradefed - adb device lost[4595FE84003F72FC]'
Count: 2 (4.00%)
IDs:
hikey-6220-r2-04:
7923662 7923670
Error: Device NOT found!
Count: 1 (2.00%)
IDs:
hikey-6220-r2-01:
7922654
Error type: Canceled
Error count: 2 (4.00%)
Error: The job was canceled
Count: 2 (4.00%)
IDs:
hikey-6220-r2-05:
7922652 7922657
Device type: qrb5165-rb5
Total jobs: 61
Total errors: 15 (24.59%)
Error type: Test
Error count: 13 (21.31%)
Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed'
Count: 1 (1.64%)
IDs:
rb5-03:
7926646
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds'
Count: 3 (4.92%)
IDs:
rb5-03:
7923701 7923707
rb5-06:
7926602
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 295 seconds'
Count: 1 (1.64%)
IDs:
rb5-07:
7926587
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 282 seconds'
Count: 1 (1.64%)
IDs:
rb5-07:
7926331
Error: No match for error type 'Test', message 'tradefed - adb device lost[f11b68eb]'
Count: 2 (3.28%)
IDs:
rb5-05:
7923736 7926326
Error: No match for error type 'Test', message 'tradefed - adb device lost[4fc7b22]'
Count: 1 (1.64%)
IDs:
rb5-06:
7926218
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 298 seconds'
Count: 1 (1.64%)
IDs:
rb5-06:
7923714
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 592 seconds'
Count: 1 (1.64%)
IDs:
rb5-03:
7923704
Error: No match for error type 'Test', message 'tradefed - adb device lost[93dcfd96]'
Count: 1 (1.64%)
IDs:
rb5-01:
7921658
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 591 seconds'
Count: 1 (1.64%)
IDs:
rb5-07:
7921656
Error type: Infrastructure
Error count: 1 (1.64%)
Error: fastboot-flash-action timed out
Count: 1 (1.64%)
IDs:
rb5-07:
7923735
Error type: Job
Error count: 1 (1.64%)
Error: expect-shell-connection timed out
Count: 1 (1.64%)
IDs:
rb5-05:
7923705
Device type: dragonboard-410c
Total jobs: 1
Total errors: 0 (0.00%)
Device type: x86
Total jobs: 3
Total errors: 0 (0.00%)
Device type: dragonboard-845c
Total jobs: 64
Total errors: 29 (45.31%)
Error type: Job
Error count: 4 (6.25%)
Error: expect-shell-connection timed out
Count: 3 (4.69%)
IDs:
db845c-03:
7923695
db845c-09:
7923671
db845c-10:
7923791
Error: No match for error type 'Job', message 'login-action timed out after 119 seconds'
Count: 1 (1.56%)
IDs:
db845c-07:
7921661
Error type: Test
Error count: 23 (35.94%)
Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed'
Count: 11 (17.19%)
IDs:
db845c-01:
7923660 7923753 7923755
db845c-03:
7923720 7923751 7923752 7923754
db845c-04:
7923698
db845c-09:
7921645 7921649
db845c-10:
7923771
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 291 seconds'
Count: 1 (1.56%)
IDs:
db845c-01:
7923709
Error: No match for error type 'Test', message 'tradefed - adb device lost[f3a58ae3]'
Count: 1 (1.56%)
IDs:
db845c-04:
7923694
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds'
Count: 4 (6.25%)
IDs:
db845c-02:
7923682
db845c-06:
7921650
db845c-09:
7920598 7923673
Error: Device NOT found!
Count: 2 (3.12%)
IDs:
db845c-02:
7921647 7923661
Error: No match for error type 'Test', message 'tradefed - adb device lost[25564f71]'
Count: 2 (3.12%)
IDs:
db845c-08:
7920616 7923635
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 283 seconds'
Count: 1 (1.56%)
IDs:
db845c-01:
7921646
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 53998 seconds'
Count: 1 (1.56%)
IDs:
db845c-04:
7920448
Error type: Infrastructure
Error count: 2 (3.12%)
Error: fastboot-flash-action timed out
Count: 2 (3.12%)
IDs:
db845c-01:
7923684
db845c-07:
7921644
Device type: juno-r2
Total jobs: 1
Total errors: 0 (0.00%)