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 5b7db6ac3f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards e6f6eca283 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 1e92817642 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 3b617db836 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 03cf47014f 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 3cfef9a824 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards e09e49bf15 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 91e8afca98 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 414ed10724 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 496ca9fabe 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 4c2a253977 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards bd7f808efc 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 898ca0d6fa 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 55bb913f4d 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 5275732da4 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 95a300c13f 127: onsuccess: #874: 1: Success after linux: 219 commits discards a92dba7178 126: onsuccess: #873: 1: Success after glibc: 2 commits discards a64bebdd30 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 5ac87d3ff0 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 8f6b3bef90 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 85e2818c5c 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 19c469ff2a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 8ede70d677 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 95c371bb5d 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards a03742b715 118: onsuccess: #863: 1: Success after linux: 12 commits discards 8478395c5d 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 9096bd2d3f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards e0a53d4119 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards dc1689b933 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 17388d6129 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 73bf92dd86 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 9734a77fe4 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 4f86164f2d 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 81a23fc65a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards ae3bf1b623 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 56d7a3bd41 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 2e85305058 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards bb15c09cb2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards a78ee770c4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards fa2bafa08a 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 4b563ea81e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 59754e044a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 84a4518e3d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 2046e4b605 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards e1d910b666 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 7ec330cf3c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards d3f7f91a06 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 3584053455 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 786b807dbe 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 7ac3d20fbd 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards d033e12d16 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards fdfea221f3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 5ed7e926ee 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards f61d385cd0 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 8297c09f56 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 5f8a3a1787 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5d4ecc0662 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards be992f5fb8 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 589be7e0f2 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards e31fbd64ff 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 1b6f504a02 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 0f7fc85153 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7f598e8ae7 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 543fc34d54 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 518787c3f2 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards c0abd4f070 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards da09e02acc 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d365b16fd4 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 1a7a1bf71e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 5a75cf5b56 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 80242565fe 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards a9bc360c43 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 3df18066dc 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards e55550582b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards a37ee2ac8f 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards daa7f83625 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 31eb8f9dcb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 2c2c25f357 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards ae5ac02254 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 26d34463dc 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards a6f6944178 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 61156cd036 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards cc8c9225f3 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards c2e8399cd5 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards df2acbed40 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards d8ddbc6b2c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 6bfe6d7ace 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards a33b59f430 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 555d945c76 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 547c6c760c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 3fad6e3070 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards e58047d4c3 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 8ebaa39e93 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 30bd1c7eb8 49: onsuccess: #785: 1: Success after binutils: 12 commits discards cb92101fe4 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 930cac6add 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 4d25f275c6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 49961bc5d4 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards a585dba7e0 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 19301529d4 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards b0e0c4a5a8 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 8ee37f3439 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 8b8a0b1e00 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new b4bb5f776b 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 92fea1ea6c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 185c5f25f4 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new a55848614d 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 8832bfaa9b 48: onsuccess: #782: 1: Success after binutils: 8 commits new d41a8315c3 49: onsuccess: #785: 1: Success after binutils: 12 commits new b0626addad 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 9ca0279232 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 51f590e967 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 6637b4e30f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new bd745a82a2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 7a8fc7708d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 02ec84db40 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 9c056a71fd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new d5264bd26f 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new e81113a750 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 7ec5826572 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 9d46137902 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 2e6c1f5ed7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 4375eed3ec 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new cf895c42f4 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 290a1193d7 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 6a67f5cae2 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 26df8d8547 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 4a625c12ab 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 57a0d4f843 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 63bf975e38 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new d905362749 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new c40cceb691 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new b711be8381 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 177dfe372c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new e0a60bc39d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new f895d6eac4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new f1862164fc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 12af03224b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 2bd598b802 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 0b6dac95f8 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 2e222f9989 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new de924adcd0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 3b53ef1483 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 0048c063c8 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 85971cc643 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 385ae38bf4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new f697139498 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new f853c97731 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new e67a1c2f3c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 807e08b410 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 56e449485d 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 4b78d222a5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 9c9c9eb441 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new cd5e7f0fdf 94: onsuccess: #832: 1: Success after binutils: 5 commits new 26e8dd63c8 95: onsuccess: #835: 1: Success after binutils: 3 commits new e324ddbe4e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 36d98ca4f8 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 8cbf686355 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c691098b47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new c45035f4c8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new ccb41f6f46 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new b352e63d62 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new be036af736 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 58aa93f7d8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new cb0b49ec3d 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new f40d4a077e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new a31262c584 107: onsuccess: #849: 1: Success after binutils: 5 commits new 761c2b3ae1 108: onsuccess: #850: 1: Success after gcc: 2 commits new 93964a6905 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new caaaaf475e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 1dee7cb721 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new ebf0d2ae5f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new f472b2d4e8 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 63bfd40657 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 077c2cbb9c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 14dd49d2f6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 6dfc06d53f 117: onsuccess: #861: 1: Success after binutils: 18 commits new bbfc7f4c4e 118: onsuccess: #863: 1: Success after linux: 12 commits new a1dc543e81 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new ad3e31ab15 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new c8ec0f95de 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new f8f52511f9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new a53a6da6e2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 01dc0e7770 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 3f0aae12fc 125: onsuccess: #871: 1: Success after binutils: 26 commits new c2c8d7b216 126: onsuccess: #873: 1: Success after glibc: 2 commits new 57d53d69e9 127: onsuccess: #874: 1: Success after linux: 219 commits new 53e46c8481 128: onsuccess: #876: 1: Success after binutils: 12 commits new 45f0e79f88 129: onsuccess: #878: 1: Success after linux: 3008 commits new 40c661f858 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new b3a62c2ac8 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new bc422a6aee 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new c52a8413b2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 208e765723 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 64714af42c 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new eebce76ff7 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 3e0986460f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 2f25e84e95 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 4c4ef76ec6 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 7f0c30b1cd 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 47c902f6b6 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new b7fe61c15e 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 9e24e503b4 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits

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 (5b7db6ac3f) \ 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 1744 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 40044 -> 40344 bytes 04-build_abe-gcc/console.log.xz | Bin 215436 -> 214880 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8364 -> 8348 bytes 07-build_abe-glibc/console.log.xz | Bin 245028 -> 244776 bytes 08-build_abe-gdb/console.log.xz | Bin 39936 -> 39712 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2432 bytes 11-check_regression/console.log.xz | Bin 7652 -> 5464 bytes 11-check_regression/mail-body.txt | 42 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 415 +-- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3745176 -> 3768040 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3312456 -> 3313864 bytes sumfiles/gcc.sum | 5382 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1077080 -> 1081568 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232308 -> 232920 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457192 -> 459756 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 2858 insertions(+), 3358 deletions(-)