This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards bf821814c1e 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 99b53d913f1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 85495f19447 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 7727024eefd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 012ec58fd15 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 6e53e0eb9c0 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9b41b2fc0ee 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 45f3172cc98 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 7a35473ee68 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards efc0f8c87a1 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards e6b57419b5b 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 04d3172313c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 4e1a3f8b8f4 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards a1e8ebdc7a4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 673fb598222 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards ad7a31bb3ed 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 77854e6853a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards cc386ea880e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 058e05cdc95 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 06b13d68289 94: onsuccess: #832: 1: Success after binutils: 5 commits discards a21fd4371e0 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 6c1733e319c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards ab3a4ae433b 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards ae3a52c56f1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 9b1434a4670 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards bd446d3b576 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 8a2fe9ae128 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards a6cf2e8aa4f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards e19c0fb45df 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards a7e64d8646d 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards a0855d1da59 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards f8d2aff0c9f 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 506dac2fd90 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 8e7a119a077 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards a69f9086003 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 2dbe31d59dc 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards a7cbb745dec 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 05623ff9f97 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 7b0fb269f28 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 54692b276c1 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 2700dc4e63a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 84e7852e2bc 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 05accb5ee09 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 51d80fce8ef 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards a93adb8dc14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 8649f800044 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards ca5cab9ed3e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards c852cb8ac79 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8540e3b620c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 2b0e6f42306 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 5dbb18dcdd0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 7ee009bb2a8 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards b3478d9bddc 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f7331f59c4b 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 630f33c5b98 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards b8f5a7509ea 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 22a3aa0d2b0 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards bc6a333fc07 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards c3d890b9bde 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 0a17d01fd5d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 843376e126f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 40149b5a9ad 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 00c9e3d5c1b 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 8bac9b076fb 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 9591b435fad 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 52809ab3596 48: onsuccess: #782: 1: Success after binutils: 8 commits discards bdabebc7eda 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards de4da114b44 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 94fc7633003 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 408fe86ea2c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards d0d57b3b87a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards f220b01bee3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards fbe076f66da 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 150bb87e51d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards dc9b82d2e99 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards a7c05f4cabf 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards eef7dfff45e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards e777fca9230 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards a62c633942b 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards dc4d724f3f6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 8d1dea8b1b1 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 66fc3e40740 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards bc44c70ba6f 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards a79242072a3 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 1f7d7c191b9 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 9cc317864a4 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 16ce15476de 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards bf43249444a 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 2dfc72e8658 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards a271892f75f 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards e3409d61b03 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 4e933ebd5f1 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 57f4505a14c 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 02a311b77b0 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d6a2ac76e6f 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d17854b80fd 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9a00729e868 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards bdd84efc398 16: onsuccess: 1: Successful build after binutils: 4 commits discards 25c272d2e45 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 14b86d7e08c 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 128a279faf9 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d2c5f7d8ab0 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 64f8e7b4147 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d62144261d4 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 91a484dee8e 16: onsuccess: 1: Successful build after binutils: 4 commits new f44f19d094d 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ed7262575c6 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8aad06f750d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0a5996f9f18 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 626a0fec65a 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cbc8dadb101 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 67508e1f2c1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new c4e8d0ca025 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 2b8d4deffcd 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 17aaa4f16f1 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 1345927d62e 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 53ba6ab2d1c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new c15deca5b6e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new c02cb654980 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new e8746e57edc 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 7c127f1cc5b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new ae037d49a03 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new a748113b361 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 0c091c80c0a 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 1d094f8b2af 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new d66e58d030d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 86192a74d11 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new bb4f8653718 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new bbf61966ad2 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 6b9311f974e 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new a11e5f0f836 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 41b870f7f40 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 210627e9a24 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 05bb1e94c42 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new f8c3b814a05 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 774b7e23dc8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 2d3340dd2be 48: onsuccess: #782: 1: Success after binutils: 8 commits new a82a59f8062 49: onsuccess: #785: 1: Success after binutils: 12 commits new 0c7c072d40e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 6d9685e3065 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 0bbc244e290 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new d9f6215df13 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 699357f77e7 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 51ffe1af45b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new d292a1ca4ca 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new b72e8e455e2 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 4d10d3d1b1b 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 2e7fda5e00b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new ebb0f78c985 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new c6f12f6db2b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 7d99b927e73 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 940eb0216cf 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 4cb24f460c9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 41705b0a9fd 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 5bb925b9c3c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 00e49b69ef8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 7f13056d8e9 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new f7a8a05e17a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new eaf9845afa6 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 8ee72e80c5e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 67f4713483e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 2f0a3b84860 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 31074a04498 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 537d76c01a8 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 1f5fa162150 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new dcc6657bc17 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new d688db2bdbd 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 486f93017ad 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new b9c0196b6e1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 0ac6b561627 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 00a5fd8fbde 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 296791af455 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 7505a55e63f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new aba16e62cef 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 28b3434932b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 672cfd0a830 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 061a02eb474 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 9b3f71de24b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 8ff6de6b88b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 65c150ee69c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new d60db611484 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 92bb328b4c5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new f3fa1b38c05 94: onsuccess: #832: 1: Success after binutils: 5 commits new db36c72cff4 95: onsuccess: #835: 1: Success after binutils: 3 commits new d027896f2f1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 4dc1621e2c9 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 20cd329f146 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 2f96a9a03c3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 91567e7972e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new a26899f7d6e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new c6798c2192e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 2b3a48b5098 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 2a7c1245ff8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 8f06d55a9d6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new cbacae92809 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 7b054ea04c8 107: onsuccess: #849: 1: Success after binutils: 5 commits new 2ea43c1d010 108: onsuccess: #850: 1: Success after gcc: 2 commits new 7572a51d1d0 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 71a87bc82b1 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a0af8d81a1b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 36ca3dfbe3d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 98cc57cd9c0 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new b63a3b3360e 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (bf821814c1e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39820 -> 39084 bytes 04-build_abe-gcc/console.log.xz | Bin 213872 -> 214544 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 244332 -> 243288 bytes 08-build_abe-gdb/console.log.xz | Bin 39160 -> 38824 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2920 -> 2596 bytes 11-check_regression/console.log.xz | Bin 8732 -> 7792 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 8 +- 11-check_regression/mail-body.txt | 59 +- 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 573 +--- 11-check_regression/results.regressions | 31 +- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 61 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 31 +- sumfiles/g++.log.xz | Bin 3756372 -> 3748248 bytes sumfiles/g++.sum | 177 +- sumfiles/gcc.log.xz | Bin 3285492 -> 3297028 bytes sumfiles/gcc.sum | 4675 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085980 -> 1084188 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230816 -> 231112 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451508 -> 453260 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2865 insertions(+), 3025 deletions(-)