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 05df84e8113 129: onsuccess: #878: 1: Success after linux: 3008 commits discards ba10a267310 128: onsuccess: #876: 1: Success after binutils: 12 commits discards abea1408b26 127: onsuccess: #874: 1: Success after linux: 219 commits discards 0d34824c44a 126: onsuccess: #873: 1: Success after glibc: 2 commits discards a4beb986f30 125: onsuccess: #871: 1: Success after binutils: 26 commits discards f713ea5033d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 79e68a4058f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards be777a4b198 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards e000dbb8e55 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 6efcbc34eb2 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 03663f03b6a 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards d5307d874b1 118: onsuccess: #863: 1: Success after linux: 12 commits discards 462bdd55640 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 8770a938e9a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 25f10302e95 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 4e0f30621e8 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 54e9ec3fa2a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards ad34133894a 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 22b2f0f3aec 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards b8e390ef567 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 634f5c4483e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 466b8e1331d 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 68ff76dd74e 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 3359d0e26c3 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards b5d6ebeab31 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 1c2291b42ca 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards d86af9f0bd0 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards bacf8009211 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards cab44ad61bc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 3ecbdfc1247 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 87812bbff02 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 54c5155be76 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 19974f710d1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 7efed152dd7 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 0f0578be1d6 95: onsuccess: #835: 1: Success after binutils: 3 commits discards db6c814964f 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 1c040f5128e 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards b379f29e26d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 61090bd8f47 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards cfcdad1ffca 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards f8265cb0984 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 3de0d66f817 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards d9f926a1a06 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 36d87104a84 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 92d986141a4 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 5945c6caccd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 1754e1dadb8 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 09b84958170 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 41c72e340b1 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 8a65176e83f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards fd23ecc286b 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 3f96c08b638 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 02b92768198 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards b7ed11b59e0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards db4fe159f57 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards ff6008e71cf 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards f3f29123c0c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 77813345893 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards c6bbba2119d 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 7d1d2fdcc26 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards b13d82df5a4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards d24ed20b888 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 591a0ea7e44 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 9519f381a52 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8fe7888fe2e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards efeb8846d53 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards d56af85e434 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards b125aa0f46a 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c545a1aefff 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f80542befc0 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards ecd3019385d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards e67790bf8f7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 8a28edfd87f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 8cd408906b8 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards f5c2f57af42 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards de1c1ebcc2b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 06374c0c6ab 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 13a3aca08d4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 202bc0225fb 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards f64dc710e52 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards e353fabb9a7 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 634bce0b4a2 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 04e85c75cd5 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 9d89c49e640 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards f29321bcd62 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 5cc92ed8198 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 10e66dff5b1 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards ff1c3753c53 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 182513b1cc3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 169ec236231 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 28c3622e374 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 89180703d05 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 46526b3116b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards afc24e91073 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 919b05ae5da 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 61ca5b67fd5 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 12742a20788 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 2147795ec38 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards ca7b1f9ff6b 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards ad47126dd38 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 43ea4a71228 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 6f85cf92333 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 696dad93999 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new d66e5b41bac 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new eb5b504417c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new fed02f0fc35 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 4277855a722 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 0d811c7ea7f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 89a5aa9746e 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 977fc827db9 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new ce5af8a3e10 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new ebc17140d97 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 057646b1f7b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 5dfb3ec8204 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new eab6ba1700c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 480188bdbae 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new d4d377cc802 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new b4f31a804ef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 2a1e096e51a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 2924a829c3c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new a50869681b4 48: onsuccess: #782: 1: Success after binutils: 8 commits new cf7b2122115 49: onsuccess: #785: 1: Success after binutils: 12 commits new 347d0c0e246 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new abe7e45da1d 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 4c0a2e01063 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 87036b9635b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 1d345636b10 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 10e58854e95 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new b478abe1dfa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new c01de8f8575 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new ffefd2ad259 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new c511068e43b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new cff0bff192f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 62859b94a65 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new e4ef66c2371 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 78d89a8cb96 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 5b550b0e26a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 0781ecead5e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new f6a32f3cc0a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 406e18e3b8a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 7408e564da0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 8b056c69d57 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new d7e647dcfe1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new dca41b0f417 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new eb8f3d4147d 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 291fc36e61e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new a05630627e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 18c99d4d660 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 1dd4336143e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new feefda5e1ce 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 40e1e907166 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new f72faa59585 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 23a5aebeb41 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 9fc22c350f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new d38cf667c83 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new b0e6507970b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 25346cc4f12 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 916c3b09b95 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 9b4e1b87eda 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new da1f296768f 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 5ebd6237158 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new e1e37055a7e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new b2dbc8f83cf 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 6da28e3495a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 7b749396235 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 76c45efc566 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new ae7c3439226 94: onsuccess: #832: 1: Success after binutils: 5 commits new e9ffc23e907 95: onsuccess: #835: 1: Success after binutils: 3 commits new 70640b6aad6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new f26b910eef0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 6912fa301c4 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 185b025e11f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new f132dc0429e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 8358f6e3d3e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 254e7784d76 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new cdb07163402 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 8a9bc519481 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 3ff33530394 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 23e739cd522 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 90ded295f93 107: onsuccess: #849: 1: Success after binutils: 5 commits new ef148a374a0 108: onsuccess: #850: 1: Success after gcc: 2 commits new 5c306a5d3d8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 238584d2770 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a7d943d958e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 039f7be4397 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 6ca3badb38a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 50fc123b289 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new bece2447382 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 98111f4c421 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 6ff3132d7d8 117: onsuccess: #861: 1: Success after binutils: 18 commits new ea9f62379f4 118: onsuccess: #863: 1: Success after linux: 12 commits new d9a8c8a28a0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new b57f93c6513 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 28beaea1e95 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new ee2540d57ae 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 1c1e70b8fc2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 9a7a5e10931 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 3983e811365 125: onsuccess: #871: 1: Success after binutils: 26 commits new b873edfb9e1 126: onsuccess: #873: 1: Success after glibc: 2 commits new 40f2c854b07 127: onsuccess: #874: 1: Success after linux: 219 commits new a59ffd03b85 128: onsuccess: #876: 1: Success after binutils: 12 commits new 114b54d950c 129: onsuccess: #878: 1: Success after linux: 3008 commits new eb0a812df72 130: onsuccess: #879: 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 (05df84e8113) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 40276 -> 39904 bytes 04-build_abe-gcc/console.log.xz | Bin 216032 -> 215636 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9456 -> 10200 bytes 07-build_abe-glibc/console.log.xz | Bin 245304 -> 244148 bytes 08-build_abe-gdb/console.log.xz | Bin 39460 -> 39116 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2892 bytes 11-check_regression/console.log.xz | Bin 4848 -> 8164 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 200 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 44 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 3769128 -> 3733672 bytes sumfiles/g++.sum | 125 +- sumfiles/gcc.log.xz | Bin 3297096 -> 3317548 bytes sumfiles/gcc.sum | 5305 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1073704 -> 1085196 bytes sumfiles/gfortran.sum | 140 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232008 -> 232824 bytes sumfiles/libgomp.sum | 20 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451356 -> 456388 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 3239 insertions(+), 2815 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions