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 39401ceb186 204: force: #26: : Failure after baseline build: no new commits discards ba0f4e481bf 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3c41ba141bf 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 119c2804215 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e2287113f40 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 59148a3c5ea 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 3cc34116d30 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards d043831889b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 1849e0696c5 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 9ad0a96fe94 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 28091a5bba0 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7c83a21fbae 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards fc557110a2b 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 8fc7a9815c2 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 31653a0d911 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards cd22cf69c97 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 77d4f0c0961 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards de84e794f10 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 456e3b0cb51 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards d125077df4c 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards a14db03f63a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards ea297f258f0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards ea989510f8f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 08792a99a1f 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards ee79453d727 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards d070cca825a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards e188e18ab60 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 2736e0b40f3 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 58ba5b7e7df 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards eef715ebd39 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 5ed377b8e62 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards c899167b049 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 9eab29e821e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 030ad386af4 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 371a514c78a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards e620f4817d1 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 3d79a58aa6a 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 51a0a02dcd4 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 61434e7d671 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards f3a0198d565 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 493953a23a6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 618957fdb0a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 14040d67059 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 840a46ba802 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 33697160060 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards ab2920f8a20 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 54c10bbb3c2 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 53932c5e49a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 5ee4e28fa21 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards dcd7c2127c6 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 5ac2f97ae31 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 68f9ad93e64 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 69f2eee61e0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 5d327b63496 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards defce9e1989 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 91c6cda943d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 02b28c2635c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards a861febf32c 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 694bfd2a30e 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards f1cee452420 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards e63ea86a976 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 131f88134df 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 465c6714252 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 893b1f68b31 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards e9d649078e4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards b280fdd2c94 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 9f1aa29f9e9 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 9ebf2d49ca1 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards b38685c155e 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 05796695316 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards f2bae2cfd24 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 435c5af5199 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 1bde0b1c021 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 67f0185b464 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 761da5c520b 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards d6df4891a3c 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 80752ede57d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 447a00484c0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 0996b8fb7cd 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 126e1af53e7 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 9cb9ae241fe 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 6755162d189 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards c017e869321 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 9914654c41d 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 371b99d98a1 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 4d560057c04 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 06b29b2d156 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards ef32eb87fb0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 28e7a3dfca1 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 78afd1d5ece 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 196f07d59e9 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 21678b10634 113: onsuccess: #898: 1: Success after linux: 3 commits discards 3e8fc49226a 112: onsuccess: #896: 1: Success after binutils: 24 commits discards ae51dddb67b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards c2c0f6c0e12 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards c7967a5c417 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards a1729eae0dc 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 1f2dae6b01b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards db92015b721 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 8fff6cab5dd 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 87b968de0ea 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 72ea6fe0733 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 6154f087e92 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 59daaa1ff38 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 3cbd17803c4 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new bf555e7c361 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 968a6bb337c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new ac767f85455 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new a88ef7cfdcb 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 7a3c0c981f5 112: onsuccess: #896: 1: Success after binutils: 24 commits new baca8ec7967 113: onsuccess: #898: 1: Success after linux: 3 commits new 42d53d2d704 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 2f7ed5bc233 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new eda0747e04f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 174b36bae55 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 155659fcaa8 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new c83bde4b5df 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 8401f01fabe 120: onsuccess: #906: 1: Success after binutils: 29 commits new aa6bb0049d1 121: onsuccess: #908: 1: Success after glibc: 2 commits new edde8f11b87 122: onsuccess: #909: 1: Success after linux: 2753 commits new 4809ffe3f1b 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new d5e77c34863 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 91125a1a786 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 2b0b882f1fb 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 1837ad708a6 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 2a7184e2f9f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new a18b028f947 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new f97afdeb218 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new fa3312d60ce 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 19bc57e2add 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new e5ae1ac25a2 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 78fbe325b15 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 588fc5f3b97 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 5c8cc0c01b9 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 6ee6ab63d99 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 089eaead7f6 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 3b93b48f800 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new d785cd79c51 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 86e4bf43b79 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 8b1ec40c96b 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 15be52e8bee 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 88f0ba685c5 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new c46fb46452c 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 69cab0f2f4e 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 94eb06332ba 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new c9f15721570 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 74f995addfc 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 6f266ca54ec 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new c84710366b8 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new f2b7550d83d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 5a9f68f4238 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 22ec462139d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 0235f370cda 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new e0a9207768d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new c6593db8baf 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 6af0745fca4 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 3e68fe83215 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 059037d28dd 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 3294547512b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new f6a5ee047fe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 8519018822e 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new bf8b267aa05 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new b42df5027c5 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 1d7cdd91687 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new e87d0111456 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 4f7e6324adb 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 5bf9dee3081 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new be8fa40c923 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 3f48e85244f 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new a46850a2332 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new cc6fc29f1eb 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new d6d8c7086ee 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 9af66082b67 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 6d183404a61 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 714a1d95e21 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 01178e504f8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 5dd05c6dc4f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new ae14758744d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 9c9d37e730f 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new c21dcdcf1e2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 9c6098b5199 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new b0d26fc3f25 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 6463d986166 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 22e78a7cfa4 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 3471866d00b 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 00d13e3f1c5 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 6c2c61888bc 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8dbaf0db108 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 714e29a3e67 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 3ad7bd73818 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0ce052bec89 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new dab459f09e9 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 74a7e810830 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new b1c4655d40c 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5c20c64ab24 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 45e1dc34e77 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new bd28b716fce 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 73d90400716 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 85aaf01d530 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new f688feaf436 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c54a909b83a 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1202d15276e 204: force: #26: : Failure after baseline build: no new commits new 78924908b5e 205: onsuccess: #27: 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 (39401ceb186) \ 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 1936 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 3456 -> 2480 bytes 03-build_abe-binutils/console.log.xz | Bin 38712 -> 35088 bytes 04-build_abe-gcc/console.log.xz | Bin 203756 -> 203564 bytes 06-build_abe-linux/console.log.xz | Bin 9188 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 244512 -> 241956 bytes 08-build_abe-gdb/console.log.xz | Bin 38488 -> 34748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3792 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1048 -> 2956 bytes 11-check_regression/console.log.xz | Bin 2508 -> 4172 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 10 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.regressions | 2 - 12-update_baseline/console.log | 66 +- 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 | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results | 4 +- sumfiles/gdb.log.0.xz | Bin 0 -> 1947696 bytes sumfiles/gdb.log.1.xz | Bin 0 -> 47652 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 6920 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5620 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 5592 bytes sumfiles/gdb.sum | 114039 +++++++++++++++++++++++++++++ sumfiles/gdb.sum.0 | 114035 ++++++++++++++++++++++++++++ sumfiles/gdb.sum.1 | 2723 + sumfiles/gdb.sum.2 | 219 + sumfiles/gdb.sum.3 | 182 + sumfiles/gdb.sum.4 | 182 + 36 files changed, 231453 insertions(+), 72 deletions(-) delete mode 100644 11-check_regression/results.regressions create mode 100644 sumfiles/gdb.log.0.xz create mode 100644 sumfiles/gdb.log.1.xz create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/gdb.sum.0 create mode 100644 sumfiles/gdb.sum.1 create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3 create mode 100644 sumfiles/gdb.sum.4