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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards ddbd640d562 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards a0e2b2424b0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 58d006142a3 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards bc68cf84bfa 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b488a1af5b2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f534738ba89 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a8fd9e1e829 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9e491ecbc03 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3720770d991 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 5fe2a08c198 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e8367700173 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7857b8ea16c 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards dfc9262be6f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards bfac00a47a8 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4fc9bd4e14f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 13608521b74 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 1fd6542829b 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards b4c16f054d1 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 698d5b596c1 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards b23eda6104d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 780a94b085a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 10802220597 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 82ca886f767 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 56296b08385 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards b9a31b6dd14 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards ea3634c53d5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 8ed2c112110 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards e7c7c95eb9d 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 1a5134717c2 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 37df8712566 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards bdd3293e9b4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 6864dfc9d35 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 2333aa895bc 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards c533f6212b0 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 26cd956c156 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards c48c938b51d 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 98adeae3457 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 01820c809c2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards adcb8bc6829 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 98a7fa432e2 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 0a89dbe1516 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards b43dedee80e 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 0a3ca31ffd5 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 414a8ee0c9d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 0331ae1ab75 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 28c1c8de767 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 637aa40b044 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards ddd91996b49 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 9c21f0fe6cf 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards a2b012e8e02 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 5589e305721 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 5190850d55a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards ad18cc1f1b5 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 8e02c052771 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 92b637ece2f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 3edd432330b 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 49758443715 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 8ae3d0b1510 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards cc4af5a09ff 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 8b177491d1a 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards ac141733f26 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 56c8f7b0727 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 31a2d836403 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 5dd3af22b3a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards a7e32d83255 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 5141fc31e23 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 119e637a07f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 7f89d195f25 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 178e6c20c5b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 02e07bc449a 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards c8c0b716f92 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards e436ebcdc2c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards c6c4219b5f1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 7b634c46cae 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards b769e3a8d95 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 6e9b1e2fced 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards e74189c20b5 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 32a119d17ad 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 883de510884 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 2bb7f572db9 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 6820e294018 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards fbaa572f607 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 738711bd7af 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards f045b1dc2a8 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards b2ced024808 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 485901f5bde 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards a2f0f20c7f9 113: onsuccess: #898: 1: Success after linux: 3 commits discards 77e60be497b 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 448a3547b19 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards ace15799072 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 2dc4ef3f99f 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 4947268fb7a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 4a871287089 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 88f28f46d7d 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 4c4d24a3bed 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 52c0ec1eaab 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 5dc59696ae8 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 03b5898e3a4 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 5479ec729bf 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards f2e32dbbbf2 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards ba8222b2009 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 50803e14baa 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new df177425900 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new c17fc080333 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 62eff2e61a4 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 44d7d7f8769 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 071c6916833 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new d107de39e78 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new cc8f7de05c9 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new e94b1fc52f7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new c4e5261e3cc 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 7fd44a05aad 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 11c40d0ea51 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 8acef7777f8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 184050f6f74 112: onsuccess: #896: 1: Success after binutils: 24 commits new 483d616e90b 113: onsuccess: #898: 1: Success after linux: 3 commits new 22a39751256 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 07fda7ba74b 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 49a38c52d41 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new f84ff9750b1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 4c16b9ffc73 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 7e02c9fbd83 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 21301c04672 120: onsuccess: #906: 1: Success after binutils: 29 commits new 1ca202d8f03 121: onsuccess: #908: 1: Success after glibc: 2 commits new 49546695449 122: onsuccess: #909: 1: Success after linux: 2753 commits new 31ae7d6fb77 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new b997437b976 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 97ce674d095 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 8a1cf999d90 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new f437f0214a4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new f5bef6913b3 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 07f41c3cc13 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 44fc346913d 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 28761e02d48 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new bf7f10d7023 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 95a55da239e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 138e0b14064 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new cba8cb8bc78 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 71fa59445ff 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new f2364388dac 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 80a58b76be3 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 4d8379f8a3f 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new e07ef62e2f2 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 38ecc2a34fc 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 683bdd2c30f 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 8e16780b072 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 4ccd7c4f693 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 8e0f6fadb39 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 5ee41403ae7 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 47680847464 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 4dc50670f41 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new a1722de672a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 42b962d0fb0 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 92ea6b49e00 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new b882c0c4ac6 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new ba4ab28cf18 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 6019da9a7d1 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 5ef0aafd688 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 8311fbc5c80 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5567de9f9d1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 21129b12fb0 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 76f8b0da6e6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new c8cb452acf5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 3df0b82492b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new a5779566d4b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 16b67a5b557 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 475e177a697 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 899e662fc6a 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 1e5193385f9 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new e9b2ef5eb65 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 10859f20288 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 8c0eec199e3 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new b4e1f3a530f 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 5e11817d0a6 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 140fefa6d5b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new ad31f15f7ac 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 7b633b679c3 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 4c824498289 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 3cd1290c2d5 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new e9f9e2ea492 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 374a71648fe 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 403e7fd2dbd 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new d18da852cd2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 34dc6d88a49 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new c9542d9b034 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 237c40e2eac 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 07eaa6c45b1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 1862fd3016d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 27366209a19 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 330ed6c495d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a2302a1fe32 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 3c70599c087 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 98b6758e0ae 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f4e394ee9f9 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f07311aa74e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c4ea924ecb7 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3451c3ecc3e 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e08d0bc5567 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 62a667a666a 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 92d197d1d7f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 84873300b09 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4ce741b852f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2cad6c3b15f 200: onsuccess: #16: 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 (ddbd640d562) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 1796 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 38940 -> 39168 bytes 04-build_abe-gcc/console.log.xz | Bin 203616 -> 205368 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9588 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 243912 -> 246468 bytes 08-build_abe-gdb/console.log.xz | Bin 38628 -> 38784 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2000 bytes 11-check_regression/console.log.xz | Bin 6612 -> 7536 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 9 + 11-check_regression/mail-body.txt | 47 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 135 +- 11-check_regression/results.regressions | 17 + 12-update_baseline/console.log | 42 +- 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 | 49 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 17 + sumfiles/gdb.log.xz | Bin 1923280 -> 2014072 bytes sumfiles/gdb.sum | 4381 +++++++++++++++---------------- 31 files changed, 2404 insertions(+), 2364 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