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 14543b7893f 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c94b9b9217b 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards b9ea44de2d8 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 1d434fdd455 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 05ba09d8781 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards e6930459282 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards af1edc0fa18 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e497c6206a8 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 5f373ecd274 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7488197bef4 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ceec2ddf5d2 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 3250f1df9d3 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 35dfe8d3aeb 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 9945d0d8227 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d9766292a88 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 36764c47bd5 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7f0ee770057 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 11fbfff5a6f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 978ade2cc81 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 26dbeea4d7a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards ecfaf2de875 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 2a83a89fe8e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 28b3f95f909 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards d4aba0fcbf9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 43a02d6fa45 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 848a6982f20 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards b876c3a5261 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 4440a663ccc 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 6eb1083aebd 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 01bae48e7b5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards c99bb6ae526 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards b364c8b3e95 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 7a3b2a45e24 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 1e6c638b864 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards a718834d4d0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 1ad93153cab 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards e17173d73d8 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 0ea2485a6ca 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 55ca503e9ba 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 582eb3c89fa 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 64f01e77df8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards f2bde302d4d 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards b22da6610af 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards bd3c52cb5c5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 7521dd56a98 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 99abf050119 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards dbf641e78d9 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards e3dd0cd0b47 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 2a5fc51fe0d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 03943668440 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards eec3eb344ca 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 49147c54e5f 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards c0bbb5d32ed 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 80005c08ffc 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 8929901d3de 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 504db912b94 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 857bc2ce1c5 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards f669f3cfbc1 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards cc103835990 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 921f477991e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 4ac0b18057b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 97993ac35b8 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 8afa2ee9749 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 3c7298af533 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 5767677fa62 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards a58145efd2b 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards a90236bcca2 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards c71b7fade38 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards dfcad48eda5 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 4d536e948a1 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards c17dc32c0e1 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 73b3ba070fc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 1f8f22f6560 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 2391408f632 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 6d0d0378d08 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards be09b6a1014 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 71f428174ed 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards c00f171bf33 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards da96c12703e 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 0897b6828e5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 180c8c20c2e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 92e4b648b64 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5ce9def61a0 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 94dfaf2792f 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 47a2291b8c0 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 7d2007b3e98 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards cef5ca0e9d8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards f71177e50f2 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards b892fe61946 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 265e6b14eea 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards cef8997f61a 113: onsuccess: #898: 1: Success after linux: 3 commits discards 37671870e5a 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 20375924970 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards b821cc683c4 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 70be467f697 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards ed9102d2d85 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 54421fdbfbe 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards cdb1b375244 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 1e1acc0222c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards db71a0c9ffc 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 777c814e881 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new d8e45e9fae6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 87b968de0ea 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 8fff6cab5dd 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new db92015b721 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 1f2dae6b01b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new a1729eae0dc 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new c7967a5c417 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new c2c0f6c0e12 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new ae51dddb67b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 3e8fc49226a 112: onsuccess: #896: 1: Success after binutils: 24 commits new 21678b10634 113: onsuccess: #898: 1: Success after linux: 3 commits new 196f07d59e9 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 78afd1d5ece 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 28e7a3dfca1 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new ef32eb87fb0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 06b29b2d156 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 4d560057c04 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 371b99d98a1 120: onsuccess: #906: 1: Success after binutils: 29 commits new 9914654c41d 121: onsuccess: #908: 1: Success after glibc: 2 commits new c017e869321 122: onsuccess: #909: 1: Success after linux: 2753 commits new 6755162d189 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 9cb9ae241fe 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 126e1af53e7 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 0996b8fb7cd 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 447a00484c0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 80752ede57d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new d6df4891a3c 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 761da5c520b 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 67f0185b464 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 1bde0b1c021 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 435c5af5199 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new f2bae2cfd24 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 05796695316 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new b38685c155e 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 9ebf2d49ca1 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 9f1aa29f9e9 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new b280fdd2c94 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new e9d649078e4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 893b1f68b31 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 465c6714252 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 131f88134df 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new e63ea86a976 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new f1cee452420 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 694bfd2a30e 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new a861febf32c 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 02b28c2635c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 91c6cda943d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new defce9e1989 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 5d327b63496 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 69f2eee61e0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 68f9ad93e64 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 5ac2f97ae31 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new dcd7c2127c6 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 5ee4e28fa21 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 53932c5e49a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 54c10bbb3c2 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new ab2920f8a20 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 33697160060 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 840a46ba802 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 14040d67059 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 618957fdb0a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 493953a23a6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new f3a0198d565 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 61434e7d671 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 51a0a02dcd4 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 3d79a58aa6a 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new e620f4817d1 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 371a514c78a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 030ad386af4 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 9eab29e821e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new c899167b049 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 5ed377b8e62 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new eef715ebd39 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 58ba5b7e7df 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 2736e0b40f3 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new e188e18ab60 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new d070cca825a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new ee79453d727 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 08792a99a1f 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new ea989510f8f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new ea297f258f0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new a14db03f63a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new d125077df4c 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 456e3b0cb51 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new de84e794f10 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 77d4f0c0961 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new cd22cf69c97 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 31653a0d911 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8fc7a9815c2 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new fc557110a2b 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7c83a21fbae 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 28091a5bba0 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9ad0a96fe94 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1849e0696c5 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new d043831889b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 3cc34116d30 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 59148a3c5ea 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new e2287113f40 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 119c2804215 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 3c41ba141bf 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ba0f4e481bf 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 39401ceb186 204: force: #26: : Failure after baseline build: no new commits

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 (14543b7893f) \ 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 -> 1936 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 3456 bytes 03-build_abe-binutils/console.log.xz | Bin 39244 -> 38712 bytes 04-build_abe-gcc/console.log.xz | Bin 205504 -> 203756 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9108 -> 9188 bytes 07-build_abe-glibc/console.log.xz | Bin 245932 -> 244512 bytes 08-build_abe-gdb/console.log.xz | Bin 38948 -> 38488 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1996 -> 1048 bytes 11-check_regression/console.log.xz | Bin 7220 -> 2508 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 7 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 7 - 11-check_regression/results.compare2 | 171 - 11-check_regression/results.regressions | 2 + 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 7 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- results | 6 +- sumfiles/gdb.log.xz | Bin 1973836 -> 0 bytes sumfiles/gdb.sum | 113705 ----------------------------- 26 files changed, 52 insertions(+), 113934 deletions(-) delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 create mode 100644 11-check_regression/results.regressions delete mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum