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 c4bbd0980fa 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards ead01aa9eb4 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 689c424889d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4e776a9206f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b201209106a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3900013a7b3 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7903be0aebe 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b667aa38f69 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 1171d0f4c6e 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7f543211030 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c6487980426 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f0aadfb2691 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d39ff30d364 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards bb2acfa2760 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c9286190cc0 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards fe88380e5e0 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ef3063a8cf5 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9412d1e2411 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 01c169f9e19 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 26284832c8e 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 57eda7524f1 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards f4565cee100 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards c976ddbecd0 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards d0296f736af 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 182d4dd35a8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 36b7a8bac8b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 7f9003f5ad2 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 71f1ab71514 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 083a1602806 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards a42e2299cb3 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 63f54f53d79 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 6a63385da91 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 3e28e440787 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards c6bfaad3947 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 3f5f77eb833 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards a37bf158239 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards cc82bc66eca 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards ca90c94c6b6 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 6e30f5f3efd 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 8c3ac92bd7d 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 0c3f3036a3f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 69d18096f9d 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards b0a6dd838d8 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards f931c5195e1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 0103f7bf162 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards e57f3bf4940 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 08d1d4c6503 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards b80dceaa043 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 3f850cc9cb8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards a7fd2a27928 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards f55b9db73bb 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 3d12727efbf 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards ec5c6e5881d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 20de0e600d7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards e434bf522d9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 0d402a1df59 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards abf8eb73f5d 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards f5b99298251 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 2e56743d901 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 0124cc7bebb 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards b88ed5e9f3c 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 802fcb74420 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards ffdd39b4064 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 4d08c55f61f 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards d95d587be33 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards febfc802a7e 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 89f316c0492 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 125ba585d50 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 6236ff61246 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards cbdbc653f4f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 1932520935a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards c8c3bb81ea1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 8375bb0ec22 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards df1d3c472f6 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 34e0b9c0644 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 022ec5568c1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards f1170833d2a 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards a8e41fba805 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards e23551e4271 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards a69489074af 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 46bd2ae305c 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 17248138073 121: onsuccess: #908: 1: Success after glibc: 2 commits discards a555e87240f 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 628fe21abec 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 997eec078ed 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards da94f15c352 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 177549570ff 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 3a100fdf6dc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 0887bb94bdf 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards cfab57e68a9 113: onsuccess: #898: 1: Success after linux: 3 commits discards e65a68ec870 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 9854c1f88e9 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 67d60ca61a2 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 4fa88095866 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards d3f90d84d81 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards d4c023f28b5 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 74edf51d033 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 240e8c49c40 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 14efe450e0d 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 35ab73ce11c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 1d3c4c9785c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 76b7970dc21 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 777c814e881 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new db71a0c9ffc 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 1e1acc0222c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new cdb1b375244 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 54421fdbfbe 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new ed9102d2d85 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 70be467f697 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new b821cc683c4 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 20375924970 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 37671870e5a 112: onsuccess: #896: 1: Success after binutils: 24 commits new cef8997f61a 113: onsuccess: #898: 1: Success after linux: 3 commits new 265e6b14eea 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new b892fe61946 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new f71177e50f2 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new cef5ca0e9d8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 7d2007b3e98 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 47a2291b8c0 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 94dfaf2792f 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5ce9def61a0 121: onsuccess: #908: 1: Success after glibc: 2 commits new 92e4b648b64 122: onsuccess: #909: 1: Success after linux: 2753 commits new 180c8c20c2e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 0897b6828e5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new da96c12703e 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new c00f171bf33 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 71f428174ed 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new be09b6a1014 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 6d0d0378d08 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 2391408f632 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 1f8f22f6560 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 73b3ba070fc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new c17dc32c0e1 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 4d536e948a1 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new dfcad48eda5 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new c71b7fade38 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new a90236bcca2 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new a58145efd2b 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 5767677fa62 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 3c7298af533 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 8afa2ee9749 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 97993ac35b8 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4ac0b18057b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 921f477991e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new cc103835990 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new f669f3cfbc1 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 857bc2ce1c5 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 504db912b94 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 8929901d3de 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 80005c08ffc 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new c0bbb5d32ed 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 49147c54e5f 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new eec3eb344ca 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 03943668440 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 2a5fc51fe0d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new e3dd0cd0b47 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new dbf641e78d9 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 99abf050119 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 7521dd56a98 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new bd3c52cb5c5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new b22da6610af 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new f2bde302d4d 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 64f01e77df8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 582eb3c89fa 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 55ca503e9ba 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 0ea2485a6ca 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new e17173d73d8 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 1ad93153cab 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new a718834d4d0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 1e6c638b864 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 7a3b2a45e24 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new b364c8b3e95 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new c99bb6ae526 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 01bae48e7b5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 6eb1083aebd 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 4440a663ccc 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new b876c3a5261 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 848a6982f20 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 43a02d6fa45 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new d4aba0fcbf9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 28b3f95f909 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 2a83a89fe8e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new ecfaf2de875 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 26dbeea4d7a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 978ade2cc81 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 11fbfff5a6f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7f0ee770057 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 36764c47bd5 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d9766292a88 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9945d0d8227 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 35dfe8d3aeb 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 3250f1df9d3 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ceec2ddf5d2 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7488197bef4 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 5f373ecd274 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e497c6206a8 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new af1edc0fa18 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new e6930459282 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 05ba09d8781 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 1d434fdd455 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new b9ea44de2d8 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c94b9b9217b 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 14543b7893f 203: onsuccess: #19: 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 (c4bbd0980fa) \ 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 1776 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 38636 -> 39244 bytes 04-build_abe-gcc/console.log.xz | Bin 203652 -> 205504 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8260 -> 9108 bytes 07-build_abe-glibc/console.log.xz | Bin 246008 -> 245932 bytes 08-build_abe-gdb/console.log.xz | Bin 38252 -> 38948 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3776 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2008 -> 1996 bytes 11-check_regression/console.log.xz | Bin 6784 -> 7220 bytes 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 111 +- 12-update_baseline/console.log | 56 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/gdb.log.xz | Bin 1923744 -> 1973836 bytes sumfiles/gdb.sum | 4402 ++++++++++++++++----------------- 26 files changed, 2337 insertions(+), 2306 deletions(-)