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 bcd03da604 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards 6409ccc2ea 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 6d0414725b 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 014c4ac866 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards f85e163943 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards c99aebc288 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards ebac7faefc 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards 4425793ab2 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards f97666a421 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 9c08884758 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards f268d33b2e 152: onsuccess: #903: 1: Success after linux: 22 commits discards ef336fab79 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 9389581b2d 150: onsuccess: #900: 1: Success after gcc: 11 commits discards c67b5e36d5 149: onsuccess: #899: 1: Success after binutils: 15 commits discards ef8b2eb548 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 52ac25e114 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 0702ca4e34 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards e85235a54e 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 0054c8fe5c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 3c1c6ba5ad 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards dedd3b55bf 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards c590bb1e9d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 6945e4e2ff 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 1d7e568f2c 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards bdb4dd4ac8 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 046ab44f1e 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards b9f9146730 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 16b5e47b94 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 11c24011c6 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 0caaf02ad1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards a3e732b73e 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards e30d1ee6b1 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 81e3492514 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 4ac61be587 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 363a46854e 128: onsuccess: #876: 1: Success after binutils: 12 commits discards f5aac2749c 127: onsuccess: #874: 1: Success after linux: 219 commits discards 4ac2972aa6 126: onsuccess: #873: 1: Success after glibc: 2 commits discards bb85841637 125: onsuccess: #871: 1: Success after binutils: 26 commits discards ec5c9b8129 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 0c6778ca18 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards e3c72a4118 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 482e3ea180 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ca38b287a5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 3da3713b81 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 6c0afa29e0 118: onsuccess: #863: 1: Success after linux: 12 commits discards a73a80af5e 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 43b132cedd 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 90598a5a4f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards c34e3c3a62 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 005b7bc712 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 604dc3baa1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 83c46d26de 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 9c4a85295b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards bfce982585 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 4cc746e346 108: onsuccess: #850: 1: Success after gcc: 2 commits discards b06bb86f37 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 3456115688 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 143f6277e2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 8b53b0bb0f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards d9f43abd66 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 2ca08f2968 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards f4da090d8e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards a6547816ab 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 7623017e83 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 45e2ab3d7e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 55d412fb71 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 5c8439d68e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards a5fa323ffc 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b8f76c15f6 94: onsuccess: #832: 1: Success after binutils: 5 commits discards e00585b684 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 563a8aa1e7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 05710d928a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards c880868634 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 71f4672791 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 4ac5be6049 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 7b09297b1d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards a86fbf98f1 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 963713a2de 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards eb4c5f5f17 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 21405af12c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f08329f3b8 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards abf964e546 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 17da679e10 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 954eb04ec9 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 33f14640a1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards b52b9a26b9 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 850cd2615e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards dad35ea283 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 1c090b81bc 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 2ad587cbdf 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 83a5b3f0a8 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 71a443fbbc 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards da4933a34f 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 251df57877 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 48eb12effe 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards c01148ba9e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards ad96d111b3 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 8e8e99542d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 9d60cafc21 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 51cdf75d4f 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards ecc5d2ca55 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new e035b37ee2 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 72cdd5235d 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 98be176f88 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new e1468c74f4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 2b3acd3643 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 1f81bab7c3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 3621c71859 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new d667668a47 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 2feda143f2 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 6d4639021c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 9c269d9dad 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 7b7a0d9a29 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new bf24d2ff3c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1658505864 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new e7b8cd637d 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 1b6d6c5b5a 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 369855a277 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new a5d631440e 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 059a20c640 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new b789dee92a 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 094e81a5ed 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 9151b02a70 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new cf3abfb75a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 53fc00031b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 542e20359f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 98e50dcb4d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 269fc13eeb 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 1f525d04ab 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new a6d1b4849a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 9cb1c09ed1 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 58b5674516 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 7dc74048f5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new f1634d7dad 94: onsuccess: #832: 1: Success after binutils: 5 commits new 5fe4f79292 95: onsuccess: #835: 1: Success after binutils: 3 commits new 708bc74931 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 7a2e19314a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new d74de2f665 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new a722bf43e7 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 316a6bc201 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new bf68cb95b1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new ec460e3fce 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 7a9a9b9e94 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 74b2d70571 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 983a901354 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 28274dcf04 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new ad98fedeed 107: onsuccess: #849: 1: Success after binutils: 5 commits new ae85a83794 108: onsuccess: #850: 1: Success after gcc: 2 commits new ed00c807b6 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 90e3bd6833 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 073fe14c08 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 48511c3b30 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new bea374cb58 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 3e041eae06 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 78fdf0bcbb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new ce70f1acec 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 1551cbc682 117: onsuccess: #861: 1: Success after binutils: 18 commits new bd151b1116 118: onsuccess: #863: 1: Success after linux: 12 commits new 0bfc18e2c0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 955ac5523e 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new a93b786ad5 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 640f3ef7fe 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 27a64e41a0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 24f919ae80 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 8185d1415d 125: onsuccess: #871: 1: Success after binutils: 26 commits new 2c08489cd6 126: onsuccess: #873: 1: Success after glibc: 2 commits new f0ba803181 127: onsuccess: #874: 1: Success after linux: 219 commits new 15cfb9a113 128: onsuccess: #876: 1: Success after binutils: 12 commits new 9943f70c0d 129: onsuccess: #878: 1: Success after linux: 3008 commits new 927022b4a5 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 524b0193ea 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 1ab8e212c9 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 04a1281567 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new f8fd6be15f 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new b110a3636f 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 82826dcee5 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new f701b3ed4f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new b5f20843d4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 8b4ea7b322 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 078eeabc25 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 93faa3e75e 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new a1bcacf487 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new fac28dd694 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new f40e5ed754 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 5c2a0eb48f 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 4458508fa3 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 592a560006 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 845a7c464e 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new fdea3c25a0 149: onsuccess: #899: 1: Success after binutils: 15 commits new 3262609b19 150: onsuccess: #900: 1: Success after gcc: 11 commits new 10d2f3c69d 151: onsuccess: #902: 1: Success after glibc: 8 commits new 62107fa404 152: onsuccess: #903: 1: Success after linux: 22 commits new 1bbabbafc3 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new da5d11368c 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new f7fcfe4f60 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new ee9d26b03e 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new a8d064e8c2 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 0b730d5a66 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new b206aa3798 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 454853e9cb 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new d8f296c5f9 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 678072178d 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new b1eb5c7935 163: onsuccess: #914: 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 (bcd03da604) \ 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 1760 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39240 -> 39516 bytes 04-build_abe-gcc/console.log.xz | Bin 214484 -> 213636 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8260 bytes 07-build_abe-glibc/console.log.xz | Bin 245076 -> 244412 bytes 08-build_abe-gdb/console.log.xz | Bin 38600 -> 39404 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2856 -> 2568 bytes 11-check_regression/console.log.xz | Bin 7824 -> 7540 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 12 +- 11-check_regression/mail-body.txt | 134 +- 11-check_regression/results.compare | 34 +- 11-check_regression/results.compare2 | 246 +- 11-check_regression/results.regressions | 34 +- 12-update_baseline/console.log | 64 +- 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 | 136 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 34 +- sumfiles/g++.log.xz | Bin 3745392 -> 3743712 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 3297108 -> 3290612 bytes sumfiles/gcc.sum | 4339 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085344 -> 1084068 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232304 -> 232368 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457404 -> 454076 bytes sumfiles/libstdc++.sum | 26 +- 43 files changed, 2561 insertions(+), 2764 deletions(-)