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 2b4e9e9d13 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 3e5342502a 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 6688cee79b 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 399b11fda9 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards dc38b366fd 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards ae1448e3ea 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards baf7daf47a 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards e2b9a413b4 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 4ab3613520 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards f9dee73045 152: onsuccess: #903: 1: Success after linux: 22 commits discards d36d6cd416 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 892d293ae2 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 5114e16654 149: onsuccess: #899: 1: Success after binutils: 15 commits discards cc5ddd7405 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 3a124d7a03 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 32237e602b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 4ceb48628a 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 4b1c6fc16f 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 5f95bbe2ee 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 9ee5416312 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 0ede901acd 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 9bce56f189 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 8401e35d97 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 52cb4d3dd7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 430efa85f3 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 1aedeeb7c1 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards cb054b63a2 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 3ff506703b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards fd65ce2fd1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 102090b3ff 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 9879482fcb 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 11b533c443 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards cf7e88c4e1 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 8a026f43de 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 7e4e29aa8d 127: onsuccess: #874: 1: Success after linux: 219 commits discards cc8d975179 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 71c11cb05a 125: onsuccess: #871: 1: Success after binutils: 26 commits discards ebee22730c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 15d16c8578 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 097cc5fa0d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 6002761119 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ad5c75ebd3 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 489a9a885e 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 226e93f252 118: onsuccess: #863: 1: Success after linux: 12 commits discards d5c19876a4 117: onsuccess: #861: 1: Success after binutils: 18 commits discards f02485ac4d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 9a35db0adc 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 93edb679e5 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 22ab264cb5 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 4f29d3bc7f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 9e259ad04d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 1d53c830b6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 2086219c8b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 68995e200f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 8b5901289b 107: onsuccess: #849: 1: Success after binutils: 5 commits discards ab4ef0225a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards a801550d04 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards dd846699b5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 32ae7b4ac4 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards e284b83486 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 0b170f6ef9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 51f8d4f767 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards fab4f9fcc1 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 79353145ad 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards cba9afed3a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards c24a0e907d 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards e70492e441 95: onsuccess: #835: 1: Success after binutils: 3 commits discards c6cc6a9616 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 36d2c8f6c6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 76fb20ea0d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 1da0d24c6e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards f8d07bb418 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 5b8d21aa42 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards df4ebae523 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 8dcf84603d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 00e42c98e3 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 35aebf7af3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 94060ae909 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards f3f5597602 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 88cb9b092a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 665804dccd 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 65eaa6a1c6 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 79d65be530 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 550c2d9b7e 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 90b57b6963 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 79ca30e23f 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 2ef5a41eb7 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 7a9a6af5e4 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards c0a07f7818 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards c64bc0439c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards a91592788a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards b2ddc84c39 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 8224b31755 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards d982ca11ea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards c95577f810 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 779f68d894 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 50ef11400d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 67c5d53a90 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 199a82387c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 8ef8e16110 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards f064d2abba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 6161bcf127 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ecc5d2ca55 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 51cdf75d4f 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 9d60cafc21 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 8e8e99542d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new ad96d111b3 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new c01148ba9e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 48eb12effe 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 251df57877 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new da4933a34f 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 71a443fbbc 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 83a5b3f0a8 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 2ad587cbdf 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 1c090b81bc 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new dad35ea283 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 850cd2615e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new b52b9a26b9 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 33f14640a1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 954eb04ec9 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 17da679e10 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new abf964e546 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new f08329f3b8 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 21405af12c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new eb4c5f5f17 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 963713a2de 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new a86fbf98f1 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 7b09297b1d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4ac5be6049 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 71f4672791 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new c880868634 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 05710d928a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 563a8aa1e7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e00585b684 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b8f76c15f6 94: onsuccess: #832: 1: Success after binutils: 5 commits new a5fa323ffc 95: onsuccess: #835: 1: Success after binutils: 3 commits new 5c8439d68e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 55d412fb71 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 45e2ab3d7e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 7623017e83 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new a6547816ab 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new f4da090d8e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 2ca08f2968 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new d9f43abd66 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 8b53b0bb0f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 143f6277e2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 3456115688 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new b06bb86f37 107: onsuccess: #849: 1: Success after binutils: 5 commits new 4cc746e346 108: onsuccess: #850: 1: Success after gcc: 2 commits new bfce982585 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 9c4a85295b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 83c46d26de 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 604dc3baa1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 005b7bc712 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new c34e3c3a62 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 90598a5a4f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 43b132cedd 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new a73a80af5e 117: onsuccess: #861: 1: Success after binutils: 18 commits new 6c0afa29e0 118: onsuccess: #863: 1: Success after linux: 12 commits new 3da3713b81 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new ca38b287a5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 482e3ea180 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new e3c72a4118 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 0c6778ca18 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new ec5c9b8129 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new bb85841637 125: onsuccess: #871: 1: Success after binutils: 26 commits new 4ac2972aa6 126: onsuccess: #873: 1: Success after glibc: 2 commits new f5aac2749c 127: onsuccess: #874: 1: Success after linux: 219 commits new 363a46854e 128: onsuccess: #876: 1: Success after binutils: 12 commits new 4ac61be587 129: onsuccess: #878: 1: Success after linux: 3008 commits new 81e3492514 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new e30d1ee6b1 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new a3e732b73e 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 0caaf02ad1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 11c24011c6 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 16b5e47b94 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new b9f9146730 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 046ab44f1e 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new bdb4dd4ac8 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 1d7e568f2c 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 6945e4e2ff 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new c590bb1e9d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new dedd3b55bf 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 3c1c6ba5ad 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 0054c8fe5c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new e85235a54e 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 0702ca4e34 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 52ac25e114 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new ef8b2eb548 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new c67b5e36d5 149: onsuccess: #899: 1: Success after binutils: 15 commits new 9389581b2d 150: onsuccess: #900: 1: Success after gcc: 11 commits new ef336fab79 151: onsuccess: #902: 1: Success after glibc: 8 commits new f268d33b2e 152: onsuccess: #903: 1: Success after linux: 22 commits new 9c08884758 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new f97666a421 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 4425793ab2 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new ebac7faefc 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new c99aebc288 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new f85e163943 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 014c4ac866 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 6d0414725b 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 6409ccc2ea 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new bcd03da604 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...]

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 (2b4e9e9d13) \ 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 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39492 -> 39240 bytes 04-build_abe-gcc/console.log.xz | Bin 214216 -> 214484 bytes 06-build_abe-linux/console.log.xz | Bin 8672 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 245056 -> 245076 bytes 08-build_abe-gdb/console.log.xz | Bin 39196 -> 38600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3448 -> 2856 bytes 11-check_regression/console.log.xz | Bin 12732 -> 7824 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 437 +-- 11-check_regression/mail-body.txt | 110 +- 11-check_regression/results.compare | 447 +-- 11-check_regression/results.compare2 | 1060 ++----- 11-check_regression/results.regressions | 100 +- 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 | 112 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 100 +- sumfiles/g++.log.xz | Bin 3721936 -> 3745392 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 3287360 -> 3297108 bytes sumfiles/gcc.sum | 4697 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1084364 -> 1085344 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 232388 -> 232304 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 456056 -> 457404 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2860 insertions(+), 4365 deletions(-)