On Thu, 06 Oct 2011 20:21:42 -0000, Paul Larson <email address hidden> wrote:
> > 1 looks unlikely because we have the same revision of the kernel failing and passing
> > in different runs.
> Can you explain this further? Do you have an example you can point to of this?
linus
9c1f8594df4814ebfd6822ca3c9444fb3445888d passed on beaglexm01
d93dc5c4478c1fd5de85a3e8aece9aad7bbae044 passed on beaglexm04
d93dc5c4478c1fd5de85a3e8aece9aad7bbae044 passed on beaglexm01
d942e43b58dc27b36305bcd374a74f7cc15183a3 failed on panda01
d942e43b58dc27b36305bcd374a74f7cc15183a3 failed on beaglexm03
78bbd284e85f1af56a9fa30760c019357c2a1b4b failed on beaglexm01
78bbd284e85f1af56a9fa30760c019357c2a1b4b failed on panda08
b172e38e435a158cc84169d5b9127a8dd8d21e76 failed on panda09
b172e38e435a158cc84169d5b9127a8dd8d21e76 passed on beaglexm02
f9d81f61c84aca693bc353dfef4b8c36c2e5e1b5 failed on beaglexm02
f9d81f61c84aca693bc353dfef4b8c36c2e5e1b5 failed on panda11
f9d81f61c84aca693bc353dfef4b8c36c2e5e1b5 failed on beaglexm03
f9d81f61c84aca693bc353dfef4b8c36c2e5e1b5 failed on panda12
858b1814b89d043a3866299c258ccdc27eb2538c failed on beaglexm03
858b1814b89d043a3866299c258ccdc27eb2538c failed on panda06
815d405ceff0d6964683f033e18b9b23a88fba87 failed on beaglexm02
815d405ceff0d6964683f033e18b9b23a88fba87 failed on panda17
a102a9ece5489e1718cd7543aa079082450ac3a2 failed on beaglexm04
a102a9ece5489e1718cd7543aa079082450ac3a2 failed on panda24
so apparently no failures before d942e43b58 and no passes after b172e38.
arm-soc/for-next
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm03
bdb424537d00b036a695763c71068acce487b099 failed on panda18
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm01
bdb424537d00b036a695763c71068acce487b099 failed on beaglexm03
bdb424537d00b036a695763c71068acce487b099 failed to deploy on panda13
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm01
bdb424537d00b036a695763c71068acce487b099 passed on panda10
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm01
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm04
bdb424537d00b036a695763c71068acce487b099 passed on panda19
bdb424537d00b036a695763c71068acce487b099 passed on panda03
bdb424537d00b036a695763c71068acce487b099 failed on beaglexm03 for other
reasons
bdb424537d00b036a695763c71068acce487b099 passed on panda14
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm02
bdb424537d00b036a695763c71068acce487b099 passed on panda07
bdb424537d00b036a695763c71068acce487b099 passed on beaglexm01
08db4132dbf24693d6af5b1fdde859c3838feefb passed on panda22
dfa690cd787c72468f8d633c0be81330e4466c08 passed on panda07
dfa690cd787c72468f8d633c0be81330e4466c08 passed on beaglexm02
dfa690cd787c72468f8d633c0be81330e4466c08 passed on panda13
dfa690cd787c72468f8d633c0be81330e4466c08 passed on panda14
dfa690cd787c72468f8d633c0be81330e4466c08 passed on beaglexm04
dfa690cd787c72468f8d633c0be81330e4466c08 passed on panda21
dfa690cd787c72468f8d633c0be81330e4466c08 passed on beaglexm01
dfa690cd787c72468f8d633c0be81330e4466c08 passed on panda14
so there are two failures with that one revision, panda18 and beaglexm03
neither of which have a pass afterwards.
This data suggests that it's not failing boards, unless they are
sometimes ok, sometimes not.
It suggests that there may be a non-deterministic failure caused by the
kernel.
On Thu, 06 Oct 2011 20:21:42 -0000, Paul Larson <email address hidden> wrote:
> > 1 looks unlikely because we have the same revision of the kernel failing and passing
> > in different runs.
> Can you explain this further? Do you have an example you can point to of this?
linus
9c1f8594df4814e bfd6822ca3c9444 fb3445888d passed on beaglexm01 5de85a3e8aece9a ad7bbae044 passed on beaglexm04 5de85a3e8aece9a ad7bbae044 passed on beaglexm01 36305bcd374a74f 7cc15183a3 failed on panda01 36305bcd374a74f 7cc15183a3 failed on beaglexm03 56a9fa30760c019 357c2a1b4b failed on beaglexm01 56a9fa30760c019 357c2a1b4b failed on panda08 cc84169d5b9127a 8dd8d21e76 failed on panda09 cc84169d5b9127a 8dd8d21e76 passed on beaglexm02 93bc353dfef4b8c 36c2e5e1b5 failed on beaglexm02 93bc353dfef4b8c 36c2e5e1b5 failed on panda11 93bc353dfef4b8c 36c2e5e1b5 failed on beaglexm03 93bc353dfef4b8c 36c2e5e1b5 failed on panda12 a3866299c258ccd c27eb2538c failed on beaglexm03 a3866299c258ccd c27eb2538c failed on panda06 64683f033e18b9b 23a88fba87 failed on beaglexm02 64683f033e18b9b 23a88fba87 failed on panda17 718cd7543aa0790 82450ac3a2 failed on beaglexm04 718cd7543aa0790 82450ac3a2 failed on panda24
d93dc5c4478c1fd
d93dc5c4478c1fd
d942e43b58dc27b
d942e43b58dc27b
78bbd284e85f1af
78bbd284e85f1af
b172e38e435a158
b172e38e435a158
f9d81f61c84aca6
f9d81f61c84aca6
f9d81f61c84aca6
f9d81f61c84aca6
858b1814b89d043
858b1814b89d043
815d405ceff0d69
815d405ceff0d69
a102a9ece5489e1
a102a9ece5489e1
so apparently no failures before d942e43b58 and no passes after b172e38.
arm-soc/for-next
bdb424537d00b03 6a695763c71068a cce487b099 passed on beaglexm03 6a695763c71068a cce487b099 failed on panda18 6a695763c71068a cce487b099 passed on beaglexm01 6a695763c71068a cce487b099 failed on beaglexm03 6a695763c71068a cce487b099 failed to deploy on panda13 6a695763c71068a cce487b099 passed on beaglexm01 6a695763c71068a cce487b099 passed on panda10 6a695763c71068a cce487b099 passed on beaglexm01 6a695763c71068a cce487b099 passed on beaglexm04 6a695763c71068a cce487b099 passed on panda19 6a695763c71068a cce487b099 passed on panda03 6a695763c71068a cce487b099 failed on beaglexm03 for other 6a695763c71068a cce487b099 passed on panda14 6a695763c71068a cce487b099 passed on beaglexm02 6a695763c71068a cce487b099 passed on panda07 6a695763c71068a cce487b099 passed on beaglexm01 3d6af5b1fdde859 c3838feefb passed on panda22 68f8d633c0be813 30e4466c08 passed on panda07 68f8d633c0be813 30e4466c08 passed on beaglexm02 68f8d633c0be813 30e4466c08 passed on panda13 68f8d633c0be813 30e4466c08 passed on panda14 68f8d633c0be813 30e4466c08 passed on beaglexm04 68f8d633c0be813 30e4466c08 passed on panda21 68f8d633c0be813 30e4466c08 passed on beaglexm01 68f8d633c0be813 30e4466c08 passed on panda14
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
reasons
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
bdb424537d00b03
08db4132dbf2469
dfa690cd787c724
dfa690cd787c724
dfa690cd787c724
dfa690cd787c724
dfa690cd787c724
dfa690cd787c724
dfa690cd787c724
dfa690cd787c724
so there are two failures with that one revision, panda18 and beaglexm03
neither of which have a pass afterwards.
This data suggests that it's not failing boards, unless they are
sometimes ok, sometimes not.
It suggests that there may be a non-deterministic failure caused by the
kernel.
Cross-referencing the set of patches
in d942e43 but not in 9c1f859 in linus
with those
in bdb4245 but not in dfa690c in arm-soc/for-next
may give some clues.
Thanks,
James