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 2cad6c3b15f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4ce741b852f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 84873300b09 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 92d197d1d7f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 62a667a666a 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e08d0bc5567 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 3451c3ecc3e 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c4ea924ecb7 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f07311aa74e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f4e394ee9f9 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 98b6758e0ae 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 3c70599c087 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a2302a1fe32 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 330ed6c495d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 27366209a19 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 1862fd3016d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 07eaa6c45b1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 237c40e2eac 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards c9542d9b034 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 34dc6d88a49 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards d18da852cd2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 403e7fd2dbd 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 374a71648fe 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards e9f9e2ea492 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 3cd1290c2d5 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 4c824498289 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 7b633b679c3 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards ad31f15f7ac 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 140fefa6d5b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 5e11817d0a6 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards b4e1f3a530f 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 8c0eec199e3 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 10859f20288 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards e9b2ef5eb65 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 1e5193385f9 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 899e662fc6a 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 475e177a697 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 16b67a5b557 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards a5779566d4b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 3df0b82492b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards c8cb452acf5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 76f8b0da6e6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 21129b12fb0 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5567de9f9d1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 8311fbc5c80 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 5ef0aafd688 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 6019da9a7d1 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards ba4ab28cf18 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards b882c0c4ac6 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 92ea6b49e00 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 42b962d0fb0 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards a1722de672a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 4dc50670f41 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 47680847464 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 5ee41403ae7 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 8e0f6fadb39 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 4ccd7c4f693 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 8e16780b072 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 683bdd2c30f 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 38ecc2a34fc 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards e07ef62e2f2 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 4d8379f8a3f 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 80a58b76be3 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards f2364388dac 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 71fa59445ff 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards cba8cb8bc78 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 138e0b14064 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 95a55da239e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards bf7f10d7023 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 28761e02d48 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 44fc346913d 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 07f41c3cc13 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards f5bef6913b3 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards f437f0214a4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 8a1cf999d90 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 97ce674d095 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards b997437b976 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 31ae7d6fb77 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 49546695449 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 1ca202d8f03 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 21301c04672 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 7e02c9fbd83 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 4c16b9ffc73 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards f84ff9750b1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 49a38c52d41 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 07fda7ba74b 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 22a39751256 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 483d616e90b 113: onsuccess: #898: 1: Success after linux: 3 commits discards 184050f6f74 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 8acef7777f8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 11c40d0ea51 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 7fd44a05aad 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards c4e5261e3cc 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards e94b1fc52f7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards cc8f7de05c9 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards d107de39e78 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 071c6916833 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 44d7d7f8769 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 62eff2e61a4 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards c17fc080333 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards df177425900 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 14e4d40e048 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 39b7e89d69a 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 9e464eba3f9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 441f588d953 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new bd9d87a2334 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new f06d0902e21 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new f3ae29c299c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 07a308211e9 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 348896e216a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 7d5c4f79db4 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 86574308a69 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new d0dacb08124 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 8697bf07365 112: onsuccess: #896: 1: Success after binutils: 24 commits new dd1188ba970 113: onsuccess: #898: 1: Success after linux: 3 commits new dd5d733e14c 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 89e791084bc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 6db8a1fd8ce 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 71764b140e0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 55070d91dc9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 82c891efbf6 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 0d038b3fd74 120: onsuccess: #906: 1: Success after binutils: 29 commits new fd29ab54a69 121: onsuccess: #908: 1: Success after glibc: 2 commits new f9a759292b2 122: onsuccess: #909: 1: Success after linux: 2753 commits new 6674b4520da 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 54ee0be4b25 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 9beba91c565 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 7be98af559d 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new a28efb4539d 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 6ed4877d646 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 958e2d25405 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new c5db39fd8e4 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 1fa9dfbee41 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new f98d912c269 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new aaf4d15e2b0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new fdbb56dece2 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 86de2eb43b4 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 8c5b491bc19 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 6dc65c9cd01 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new ed21b253a74 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new daddc98c4ad 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new b13c74bfdd8 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 65ae708e245 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 95c1a7669ec 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 5067bf7e0cc 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 93e6832f002 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new d779e2c0db4 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 3938ce13e52 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 6d9f05c5d71 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 6a00b0af3a0 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new bbee203c356 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new f791b4b9b3b 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new cdac6f9a639 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new aaeabad158d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new bb04b69ad00 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new a9255fdc256 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 134161b1561 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 17ac982da33 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 36b139a0664 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 097d53ecbfa 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new c764148fa26 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 19ca34f955a 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new ebfab095d30 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new d35b82fbc5b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new a0a4e96d9ea 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 3ecdbe1fb65 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 428c868bd97 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new ee7179ed037 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 9468d426826 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new eec5ae8f8ff 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new c5eb567add0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new e5afc25d487 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 63fcf69d8d7 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new a6032659f82 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new a3cdd488ee7 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 3ba4831aae5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new dd77719fe4b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 6bc5587ba1c 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 148028cf02c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new f1c172cb32d 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new db0c3c3df16 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 7ac560a70e0 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 195990f7827 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 25a21a951fe 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new d11cd5cd0ee 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 1311e2135ef 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new cdc837ba9ab 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 687f9bd30b9 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7958028ec3d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1d42837f887 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 0ed7f4a36bd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new fab5a5e5ee5 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d0ea935e285 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f57b7e69748 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7f9de7f9d8f 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 46a0341919f 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ec4639b8cb6 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 0d2b2a52497 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 8aed048ebf0 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 7d7d404da49 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new fcdc3814916 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new ad4da72a446 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 50da64b37ce 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...]
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 (2cad6c3b15f) \ 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 1804 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39168 -> 39140 bytes 04-build_abe-gcc/console.log.xz | Bin 205368 -> 205112 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9168 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 246468 -> 245872 bytes 08-build_abe-gdb/console.log.xz | Bin 38784 -> 38552 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2000 -> 2004 bytes 11-check_regression/console.log.xz | Bin 7536 -> 6344 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 9 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 14 +- 11-check_regression/results.compare2 | 145 +- 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/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 17 - sumfiles/gdb.log.xz | Bin 2014072 -> 2017408 bytes sumfiles/gdb.sum | 4334 +++++++++++++++---------------- 30 files changed, 2293 insertions(+), 2402 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