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 eb0a812df72 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 114b54d950c 129: onsuccess: #878: 1: Success after linux: 3008 commits discards a59ffd03b85 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 40f2c854b07 127: onsuccess: #874: 1: Success after linux: 219 commits discards b873edfb9e1 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 3983e811365 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 9a7a5e10931 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 1c1e70b8fc2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards ee2540d57ae 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 28beaea1e95 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards b57f93c6513 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards d9a8c8a28a0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ea9f62379f4 118: onsuccess: #863: 1: Success after linux: 12 commits discards 6ff3132d7d8 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 98111f4c421 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards bece2447382 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 50fc123b289 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 6ca3badb38a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 039f7be4397 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards a7d943d958e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 238584d2770 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 5c306a5d3d8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards ef148a374a0 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 90ded295f93 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 23e739cd522 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 3ff33530394 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 8a9bc519481 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards cdb07163402 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 254e7784d76 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 8358f6e3d3e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards f132dc0429e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 185b025e11f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 6912fa301c4 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards f26b910eef0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 70640b6aad6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards e9ffc23e907 95: onsuccess: #835: 1: Success after binutils: 3 commits discards ae7c3439226 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 76c45efc566 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 7b749396235 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 6da28e3495a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards b2dbc8f83cf 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e1e37055a7e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 5ebd6237158 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards da1f296768f 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 9b4e1b87eda 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 916c3b09b95 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 25346cc4f12 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards b0e6507970b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards d38cf667c83 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 9fc22c350f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 23a5aebeb41 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards f72faa59585 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 40e1e907166 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards feefda5e1ce 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 1dd4336143e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 18c99d4d660 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards a05630627e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 291fc36e61e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards eb8f3d4147d 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards dca41b0f417 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards d7e647dcfe1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 8b056c69d57 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 7408e564da0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 406e18e3b8a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards f6a32f3cc0a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 0781ecead5e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 5b550b0e26a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 78d89a8cb96 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards e4ef66c2371 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 62859b94a65 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards cff0bff192f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards c511068e43b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards ffefd2ad259 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards c01de8f8575 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards b478abe1dfa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 10e58854e95 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 1d345636b10 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 87036b9635b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 4c0a2e01063 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards abe7e45da1d 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 347d0c0e246 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards cf7b2122115 49: onsuccess: #785: 1: Success after binutils: 12 commits discards a50869681b4 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 2924a829c3c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 2a1e096e51a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards b4f31a804ef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards d4d377cc802 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 480188bdbae 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards eab6ba1700c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 5dfb3ec8204 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 057646b1f7b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards ebc17140d97 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards ce5af8a3e10 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 977fc827db9 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 89a5aa9746e 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0d811c7ea7f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 4277855a722 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards fed02f0fc35 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards eb5b504417c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards d66e5b41bac 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 696dad93999 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new cc40381f780 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 0108f7392a2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 0c5d60f0331 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 9226e8c9230 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new ee083fd144a 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 7dd9bd8dfe4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new a12f942070c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new d14b38624e7 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 0de75554e63 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 113fd015e2d 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 5274893fc92 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new b6f2d17992b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 66973e0c7d5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 19c6a3614b0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 7d13eae2053 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 418f9b62581 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 5bf8c098011 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 9f860f22758 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 7dbb15e99f5 48: onsuccess: #782: 1: Success after binutils: 8 commits new f8e050bdbfd 49: onsuccess: #785: 1: Success after binutils: 12 commits new 328cad21365 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new f11795f5871 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new de581d8ad4b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 0dd819bc63a 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 07e31650e7b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 53c7bf6fb9b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new d24e658acc3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 72ba16fc4d1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 99d34b2d87d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new a5ddcc4e4ab 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new c6f03526902 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new c2e46cb15f3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new a7c512865f7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 9a544b63182 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 5ac1cbf53ed 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 8d63f46fdaf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 8d1f5624dad 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new e79350ad7cc 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new bebcdf7b72b 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new e9e90bbed37 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 79a6dd08994 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new e1cd568ad95 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new feceab5eb3e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 3c005f7c570 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new e3ecc989650 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 49357091fcc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new b0dd7d9ebe2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new fce6b274b3d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new da12c63e86d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 4647ca8c947 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 89d6c20a416 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new de18808f9c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 74b3fa503a7 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 6ff8fbb7932 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 415e6f7e841 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 19f056719af 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new bce55da6d25 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new fd9f058c1e8 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 19380184abc 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 7cc9429951a 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new e4bc3de69a1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new b525fee49fb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new a810a37af31 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 481b87cd7cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 162a79dfb2d 94: onsuccess: #832: 1: Success after binutils: 5 commits new 51de7dfebd2 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9b6522ad8fa 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 2163168a3f5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new a4c74092590 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 2d3ad4cf831 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 949c447cbcc 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new f50515b29fc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new fea0c16b1c4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 965b722df49 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new e4fe40882a9 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 5512847c147 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new e0aebccb26d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 9b5f5c2348d 107: onsuccess: #849: 1: Success after binutils: 5 commits new 33e22f09478 108: onsuccess: #850: 1: Success after gcc: 2 commits new d1684553550 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 1add1d469f3 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 21943cc6b79 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new fecb467d37f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 4d1112c6249 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 6c5b9d55d0f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new ac55f53495f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 451416b86a6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 9864670b06b 117: onsuccess: #861: 1: Success after binutils: 18 commits new a9c1005cc5e 118: onsuccess: #863: 1: Success after linux: 12 commits new 7614e887157 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new bb213ee53d9 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 488efe52b4a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 591eb85960a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 6c8e7fab85a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 0288c8245e2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 65335292f43 125: onsuccess: #871: 1: Success after binutils: 26 commits new 2d4ba349dab 126: onsuccess: #873: 1: Success after glibc: 2 commits new e52cd1c3b56 127: onsuccess: #874: 1: Success after linux: 219 commits new 081e61f18ce 128: onsuccess: #876: 1: Success after binutils: 12 commits new ede079a96a0 129: onsuccess: #878: 1: Success after linux: 3008 commits new 937a2d87ae9 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 1344549494d 131: onsuccess: #880: 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 (eb0a812df72) \ 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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39904 -> 39540 bytes 04-build_abe-gcc/console.log.xz | Bin 215636 -> 215176 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10200 -> 9600 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 244740 bytes 08-build_abe-gdb/console.log.xz | Bin 39116 -> 39328 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2892 -> 2780 bytes 11-check_regression/console.log.xz | Bin 8164 -> 7508 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 18 +- 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 34 +- 11-check_regression/results.compare2 | 276 +- 11-check_regression/results.regressions | 34 +- 12-update_baseline/console.log | 60 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 34 +- sumfiles/g++.log.xz | Bin 3733672 -> 3754172 bytes sumfiles/g++.sum | 135 +- sumfiles/gcc.log.xz | Bin 3317548 -> 3350216 bytes sumfiles/gcc.sum | 4765 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085196 -> 1081024 bytes sumfiles/gfortran.sum | 103 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2284 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232824 -> 233108 bytes sumfiles/libgomp.sum | 28 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456388 -> 449368 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2883 insertions(+), 2802 deletions(-)