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 29f8cf0bebbd 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 1 [...] discards abffac468fc0 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards b4f7244f4af5 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards b0097f590674 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] discards 297fd3c17816 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] discards 4ba25fd69773 129: onsuccess: #878: 1: Success after linux: 3008 commits discards be2ee99674be 128: onsuccess: #876: 1: Success after binutils: 12 commits discards d47a33246e3b 127: onsuccess: #874: 1: Success after linux: 219 commits discards 8ba61e98848f 126: onsuccess: #873: 1: Success after glibc: 2 commits discards a29c60738a7c 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 957bd3f22e92 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] discards 3754b08e7b1d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] discards e9453833e0e7 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] discards 366650701cd3 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] discards 0fa44e5129ba 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] discards 39729cd83401 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] discards 9dbd15b77470 118: onsuccess: #863: 1: Success after linux: 12 commits discards 167aede51582 117: onsuccess: #861: 1: Success after binutils: 18 commits discards f714dc57d65c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] discards f217ed25f590 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] discards dc08643f7434 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] discards e202054f5307 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] discards db7c0c61ef16 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] discards 81d8e2705d04 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] discards 23e587552656 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] discards d03a67202752 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] discards 800dcd390b6e 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 838b66bf868f 107: onsuccess: #849: 1: Success after binutils: 5 commits discards fee4496bbb00 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] discards bfddafce3347 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] discards 2cb7c522db2d 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] discards cc8366115c48 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] discards 96d1a19dd98a 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] discards 7cb44923d978 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] discards 0ed91aac84f4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] discards 1c9b0f0d3e59 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] discards 989894dc0fe6 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards a07132afa8b1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 563e58ab3b84 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 1986ba9aacf6 95: onsuccess: #835: 1: Success after binutils: 3 commits discards fae4a08e2809 94: onsuccess: #832: 1: Success after binutils: 5 commits discards eb0828b656ad 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 418be8dc3465 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 1e1aed82e5ed 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 2c56f6ba3b6c 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 98469d5f99fc 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards c59798e08641 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] discards 0f84d7d1dcdd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards a786031d1983 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards adede0396a70 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards 7f4c5c874d44 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 7b47f0fde196 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 1a3d15dac8fa 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] discards 58ab8e05f267 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] discards def9ceb2e600 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] discards 9f21f75db370 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] discards 880bd3c26409 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] discards 1d15bdbf04cf 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] discards ede35b7f1cb4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards e71e1b6307a6 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards a0a60a30bf59 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards 7304346bb4b0 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 628818ef49f0 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] discards 9fca8b692e02 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] discards 51ea99acd448 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards f697697123fd 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] discards d181d033fdfe 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 789849d4f66b 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] discards ade6a2ac2e93 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards ffcc9ef65ce7 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] discards 927bf970f49e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 65b52a5e9c0b 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 7b87c2fbce8f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards c51e0a5f89d7 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards b5dc836b59a7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] discards c5d38d06dd30 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 5580696988cd 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards 925941682607 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] discards 93ecab29ff82 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] discards 9cff69a8203c 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] discards 65bf19a0db05 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] discards bf1fe12f5dd5 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] discards 508bca81723b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] discards 22e1ee8b89e5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] discards 36689f0cfe3c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] discards 4c2c5da32801 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 8095efef9a95 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 674e44e682a3 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] discards 0c5d83aa4d53 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] discards 0fec7ecd60b9 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] discards 338de786816c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] discards 246b59ce80c4 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] discards e839f9547ace 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] discards 375eefd0baf3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] discards da0ef418f2e5 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] discards 5304389251cd 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] discards 81647035f936 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] discards e9d5c32d7a62 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] discards 5a64352c09aa 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] discards ab68993c2ade 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] discards 27d65ae2e633 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] new 4621f7be393b 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] new 0237956b63b5 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] new 3598d8deef4e 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] new 1e14b15f7f8e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] new ad983d01f651 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] new 7208a885cb2e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] new 3fc24a1ad737 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] new 9fd137ae3e69 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] new 286ba08eb581 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] new 0affe18c2092 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] new f45cc979b9f5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] new 97f422f4c212 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] new e69768bf90ff 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] new 6793e11f3f0c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] new b9e69b678516 48: onsuccess: #782: 1: Success after binutils: 8 commits new b00646019ac1 49: onsuccess: #785: 1: Success after binutils: 12 commits new 5ce5f6c7bce8 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] new 9518be25d42f 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] new 43d5a48a1abc 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] new 484d093ff53b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] new 69f979f0e11c 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] new 2f77e3cecc3d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] new 47e0ce351e4c 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new ea94ddbf08dd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] new 203614a80d48 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new 6452b5281c24 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new f17dc64a1277 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] new 402d43aa34ba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 407b4cdf4c90 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 44547057e6ea 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new d3049e0e5eb8 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new 2a4cf6ec4ca9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] new e2d239da1355 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 82dce8fad2b1 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] new 5d93e9ca6550 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new b49305c7fae7 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] new 78d7728d7abd 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 0046ff88acee 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] new ddf7680920ef 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] new 7e208cf144e9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 62054ca27e84 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new 3beb943b0395 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new cc1c6f077140 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 203c48ecbc49 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] new 7bb65c0055fb 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] new fb5f075bf568 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] new f367900b0986 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] new 915d7819115f 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] new 8b1b59a6f2ee 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] new 26befe7db913 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 8a40ca0a69f2 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new 5a12882a6831 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new e8ec22173a86 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new cf47725837af 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new bb71d72fc48c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] new 0f95a123a087 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new adb602b2f810 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new febc1dd8fea4 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 817351a8d3d7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new 06d82db2b2a3 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 4f1fc9e656e7 94: onsuccess: #832: 1: Success after binutils: 5 commits new 1026c0f9940f 95: onsuccess: #835: 1: Success after binutils: 3 commits new 45acb8c63d63 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new de30c157e733 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new bc9462e7ae14 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 39a5266f5a5c 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] new 0d6afef12425 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] new a8807d904a86 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] new d53ea38ad92f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] new d91dcdb7fd79 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] new 4b5d2ed38ca7 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] new 20d648475947 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] new 672fa26de006 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] new d51b90481913 107: onsuccess: #849: 1: Success after binutils: 5 commits new 5ad52e24808f 108: onsuccess: #850: 1: Success after gcc: 2 commits new 809eb134e0de 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] new b6d989ba3a9e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] new d959eada4cfd 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] new 47dd3d66bd91 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] new bc64cd9688eb 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] new 31b78cb7308e 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] new ffd6308f4869 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] new 4b87ac400f88 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] new 87d3f6de86f2 117: onsuccess: #861: 1: Success after binutils: 18 commits new feb1beb9abd7 118: onsuccess: #863: 1: Success after linux: 12 commits new 8026fe233b03 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] new 2a761ca35529 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] new 57737eca9f27 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] new 1dbfbd94370e 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] new 2d455fcfe55c 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] new 4108d2964d0a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] new 035455fcafe4 125: onsuccess: #871: 1: Success after binutils: 26 commits new 3a7ca0843c7a 126: onsuccess: #873: 1: Success after glibc: 2 commits new 17f5dd6d7d81 127: onsuccess: #874: 1: Success after linux: 219 commits new a7d8dd5fd869 128: onsuccess: #876: 1: Success after binutils: 12 commits new 53b61a23ec4f 129: onsuccess: #878: 1: Success after linux: 3008 commits new ee3232e45cee 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] new 50c50763e2a5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] new 04d297cfecb4 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new 6229f222bbf5 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new 4f225209b68b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 1 [...] new fa2721d047da 135: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...]

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 (29f8cf0bebbd) \ 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 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39580 -> 40084 bytes 04-build_abe-gcc/console.log.xz | Bin 213428 -> 216600 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8988 bytes 07-build_abe-glibc/console.log.xz | Bin 243672 -> 243548 bytes 08-build_abe-gdb/console.log.xz | Bin 39336 -> 39328 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3892 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2604 -> 2568 bytes 11-check_regression/console.log.xz | Bin 5776 -> 6768 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 60 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 58 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 - sumfiles/g++.log.xz | Bin 3769764 -> 3774856 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 3315620 -> 3308548 bytes sumfiles/gcc.sum | 4896 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081820 -> 1079996 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232456 -> 233052 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456808 -> 456572 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2714 insertions(+), 2736 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions