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 50da64b37ce 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards ad4da72a446 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards fcdc3814916 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7d7d404da49 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8aed048ebf0 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 0d2b2a52497 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ec4639b8cb6 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 46a0341919f 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7f9de7f9d8f 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f57b7e69748 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d0ea935e285 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards fab5a5e5ee5 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0ed7f4a36bd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 1d42837f887 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7958028ec3d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 687f9bd30b9 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards cdc837ba9ab 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1311e2135ef 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards d11cd5cd0ee 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 25a21a951fe 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 195990f7827 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 7ac560a70e0 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards db0c3c3df16 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards f1c172cb32d 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 148028cf02c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 6bc5587ba1c 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards dd77719fe4b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 3ba4831aae5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards a3cdd488ee7 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards a6032659f82 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 63fcf69d8d7 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards e5afc25d487 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards c5eb567add0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards eec5ae8f8ff 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 9468d426826 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards ee7179ed037 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 428c868bd97 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 3ecdbe1fb65 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards a0a4e96d9ea 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards d35b82fbc5b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards ebfab095d30 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 19ca34f955a 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards c764148fa26 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 097d53ecbfa 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 36b139a0664 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 17ac982da33 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 134161b1561 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards a9255fdc256 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards bb04b69ad00 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards aaeabad158d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards cdac6f9a639 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards f791b4b9b3b 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards bbee203c356 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 6a00b0af3a0 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 6d9f05c5d71 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 3938ce13e52 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards d779e2c0db4 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 93e6832f002 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 5067bf7e0cc 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 95c1a7669ec 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 65ae708e245 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards b13c74bfdd8 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards daddc98c4ad 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards ed21b253a74 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 6dc65c9cd01 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 8c5b491bc19 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 86de2eb43b4 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards fdbb56dece2 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards aaf4d15e2b0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards f98d912c269 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 1fa9dfbee41 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards c5db39fd8e4 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 958e2d25405 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 6ed4877d646 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards a28efb4539d 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 7be98af559d 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 9beba91c565 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 54ee0be4b25 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 6674b4520da 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards f9a759292b2 122: onsuccess: #909: 1: Success after linux: 2753 commits discards fd29ab54a69 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 0d038b3fd74 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 82c891efbf6 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 55070d91dc9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 71764b140e0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 6db8a1fd8ce 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 89e791084bc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards dd5d733e14c 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards dd1188ba970 113: onsuccess: #898: 1: Success after linux: 3 commits discards 8697bf07365 112: onsuccess: #896: 1: Success after binutils: 24 commits discards d0dacb08124 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 86574308a69 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 7d5c4f79db4 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 348896e216a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 07a308211e9 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards f3ae29c299c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards f06d0902e21 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards bd9d87a2334 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 441f588d953 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 9e464eba3f9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 39b7e89d69a 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new e849145b56f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 1d3c4c9785c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 35ab73ce11c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 14efe450e0d 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 240e8c49c40 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 74edf51d033 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new d4c023f28b5 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new d3f90d84d81 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 4fa88095866 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 67d60ca61a2 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 9854c1f88e9 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new e65a68ec870 112: onsuccess: #896: 1: Success after binutils: 24 commits new cfab57e68a9 113: onsuccess: #898: 1: Success after linux: 3 commits new 0887bb94bdf 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 3a100fdf6dc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 177549570ff 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new da94f15c352 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 997eec078ed 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 628fe21abec 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new a555e87240f 120: onsuccess: #906: 1: Success after binutils: 29 commits new 17248138073 121: onsuccess: #908: 1: Success after glibc: 2 commits new 46bd2ae305c 122: onsuccess: #909: 1: Success after linux: 2753 commits new a69489074af 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new e23551e4271 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new a8e41fba805 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new f1170833d2a 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 022ec5568c1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 34e0b9c0644 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new df1d3c472f6 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 8375bb0ec22 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new c8c3bb81ea1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 1932520935a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new cbdbc653f4f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 6236ff61246 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 125ba585d50 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 89f316c0492 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new febfc802a7e 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new d95d587be33 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 4d08c55f61f 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new ffdd39b4064 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 802fcb74420 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new b88ed5e9f3c 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 0124cc7bebb 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 2e56743d901 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new f5b99298251 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new abf8eb73f5d 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 0d402a1df59 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new e434bf522d9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 20de0e600d7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new ec5c6e5881d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 3d12727efbf 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new f55b9db73bb 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new a7fd2a27928 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 3f850cc9cb8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new b80dceaa043 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 08d1d4c6503 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new e57f3bf4940 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 0103f7bf162 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f931c5195e1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new b0a6dd838d8 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 69d18096f9d 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 0c3f3036a3f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 8c3ac92bd7d 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 6e30f5f3efd 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new ca90c94c6b6 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new cc82bc66eca 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new a37bf158239 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 3f5f77eb833 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new c6bfaad3947 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 3e28e440787 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 6a63385da91 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 63f54f53d79 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new a42e2299cb3 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 083a1602806 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 71f1ab71514 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 7f9003f5ad2 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 36b7a8bac8b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 182d4dd35a8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new d0296f736af 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new c976ddbecd0 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new f4565cee100 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 57eda7524f1 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 26284832c8e 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 01c169f9e19 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 9412d1e2411 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ef3063a8cf5 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new fe88380e5e0 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new c9286190cc0 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new bb2acfa2760 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d39ff30d364 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f0aadfb2691 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c6487980426 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7f543211030 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 1171d0f4c6e 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b667aa38f69 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7903be0aebe 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3900013a7b3 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new b201209106a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4e776a9206f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 689c424889d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new ead01aa9eb4 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c4bbd0980fa 202: onsuccess: #18: 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 (50da64b37ce) \ 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 1808 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39140 -> 38636 bytes 04-build_abe-gcc/console.log.xz | Bin 205112 -> 203652 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8260 bytes 07-build_abe-glibc/console.log.xz | Bin 245872 -> 246008 bytes 08-build_abe-gdb/console.log.xz | Bin 38552 -> 38252 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3756 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2004 -> 2008 bytes 11-check_regression/console.log.xz | Bin 6344 -> 6784 bytes 11-check_regression/mail-body.txt | 17 - 11-check_regression/results.compare | 10 +- 11-check_regression/results.compare2 | 108 +- 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 | 19 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/gdb.log.xz | Bin 2017408 -> 1923744 bytes sumfiles/gdb.sum | 4364 +++++++++++++++++---------------- 27 files changed, 2328 insertions(+), 2304 deletions(-)