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 6ad3bb6d051 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards e547b858887 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 50ca128c5bb 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards bf66c74a9ef 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 875566855b2 204: force: #26: : Failure after baseline build: no new commits discards 9316d7943c5 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards af0ab93f33f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards dbf6ebb215e 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2b8e9cd502c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2b2ed59a1f8 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1686972531f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f6b21e2edfa 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 42b84639e66 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards dc293035f5a 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 05c54f135d2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 531de0c4726 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e64e57f0f87 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a5ceded96c6 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 09490cdce92 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e692d266b9b 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 762b5421146 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 8dfa808796f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 245b2a79579 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards d8e2668aa02 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards b658e8efe95 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards ccc81b756aa 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards f5a8e097312 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards e979749f3f2 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 6ab1bbe77ef 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 4612887fc39 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 10167939857 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards bf0ac9c86f1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 953066a917e 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards ca6379a17d9 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 718ae9e81cd 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 22129add1f4 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards e743be2377a 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 7009a3fb61c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards c77d30d48a4 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 55cce0fb705 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 727dee43df9 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards d4497e3e2ff 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards da4cd963c7e 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 14dd819d4b0 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 702c025a672 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 4128d9c651b 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards ba742861732 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 00929e63d79 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards cea29fc6784 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 8c67f6c6c19 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 77f06975662 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 4862b40650f 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 165e7b55047 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards e24db1df809 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards fc3d9c38bac 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 79a363e0188 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 56b19f927c2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 224fbf6050d 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 4d3da5b8abd 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 4e6441369ed 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 7cc893ae81b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 50c5ad6e298 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 0c093da2681 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 3337e2774fa 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards de09690cd57 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 84d42bfa4f5 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 1832537d9d7 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards c42cebfba5e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 988db039532 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 6f241f7ec99 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards d27039ab960 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 73f1b4ed0d9 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 694509a21f2 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 111b98db5bd 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 7b981171314 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 5e12a6b1ad8 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 477c9b61a04 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 2b26f9c10d1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 1953ee35274 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards f4573fdf329 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 5b0ba83f9b9 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 5ebf3eba4e3 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 8e3ce56fa00 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 573a3df0f94 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 25ce5599b45 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 22e7dcc0d4e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards ecc2e3be8a0 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5dbcf2b3910 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 09c71667383 120: onsuccess: #906: 1: Success after binutils: 29 commits discards ec7d0fae265 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards baffa61b74e 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 5543c040a0f 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards ebc87771bbd 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 1d9ba11c1a5 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 35e6c51af2e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 89a2dcfed29 113: onsuccess: #898: 1: Success after linux: 3 commits discards 566fde48855 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 83724d31f04 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards ce5759b7d94 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards d16ffcc8239 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 275568c394f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new d7ffec9933c 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new d3b6a5d9a5d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 1d534f5f882 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 801ded60601 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 7197a1d34f7 112: onsuccess: #896: 1: Success after binutils: 24 commits new 8a68baba64a 113: onsuccess: #898: 1: Success after linux: 3 commits new 4b83264f913 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new df54842e0dc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 0b3ff513d33 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 5bb1f8d4214 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 9d874a66a1d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new f00748b1c55 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new f8e749e7a25 120: onsuccess: #906: 1: Success after binutils: 29 commits new f7f7e20f976 121: onsuccess: #908: 1: Success after glibc: 2 commits new 6e370c5aa1d 122: onsuccess: #909: 1: Success after linux: 2753 commits new 780daca1573 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 8d11c8440a9 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 8d981c1890a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 5a217ae99b2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 3bd4d6da4c9 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 62b219ba8eb 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new dd15cbb77dc 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 2cc86207558 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 800e17600ec 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new bbefca5c00a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new a2c9e2e5ab5 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 694e6155a6e 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new b15291f08f8 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 593837a8f96 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new b469070ad3d 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 8f57d5cda77 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new c2cd7424c81 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 43aa91ffeb7 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new c68a03ca077 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new a50d70001b4 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new a507defe4ab 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 9119ea11351 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 6a91d723b00 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 887560771ba 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new cab8bf23028 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new c02c58bf30c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 3d0b149db61 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 46f007587b4 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new f9952a74c87 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 3de818f37c7 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new fd90335d2f0 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 668ff3db94a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new c58a52caa9d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new cf89547b8e3 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new e5aa28e1dd0 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 758b2fb1da3 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 3f904f02120 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 4c6a214dbeb 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new a1d245e0b05 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 181fe6e11c1 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new d4c14b49695 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new b8d9f3890fb 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 3594de2e6bb 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new b54eb2965b4 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new b1de4424b4f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 76bc246ed38 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 959a279299f 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 6fd9164db30 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 1c3acde3f51 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 84fb688b369 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new b1581e0cda2 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 2370a444ceb 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new b5e1b30e488 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 62cd254ff70 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new daf7e5ae0bc 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new c630cac9434 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new ebe029f8596 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new aaaef43488c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 3e089deed6a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 1d80dd3a8bd 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 758d5756c52 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 3a1748fe331 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 36b8c0f5cd6 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c4ead1bfa3f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new bf3add9a0ed 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new fb7bff4f02f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 3cc8dd5a0d8 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 485c62d2c54 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 82d355fbde7 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2171fc83138 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 011e81149e2 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f176cb32866 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4453da926c3 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7aa4de8db7f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 636d94309db 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 7ee817e4694 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 482da487cab 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 29a2f599d92 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 89b06d145d6 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 43082f47af2 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 65e19cac23c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b2d3ded54a3 204: force: #26: : Failure after baseline build: no new commits new 63c29ebaf42 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 75e470a9e55 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f7841512691 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new b547d0830d4 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 0ce391bee57 209: force: #37: 1: Success 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 (6ad3bb6d051) \ 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 1764 -> 2232 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35248 -> 35348 bytes 04-build_abe-gcc/console.log.xz | Bin 202828 -> 204024 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8192 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 241768 -> 242368 bytes 08-build_abe-gdb/console.log.xz | Bin 34812 -> 35072 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3788 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2876 -> 2968 bytes 11-check_regression/console.log.xz | Bin 5700 -> 2848 bytes 11-check_regression/mail-body.txt | 20 - 11-check_regression/results.compare | 19 +- 11-check_regression/results.compare2 | 130 +-- 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 22 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- sumfiles/gdb.log.0.xz | Bin 2010724 -> 1940980 bytes sumfiles/gdb.log.1.xz | Bin 34764 -> 27040 bytes sumfiles/gdb.log.2.xz | Bin 14248 -> 5424 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5424 bytes sumfiles/gdb.sum | 1695 ++++++++++++++++++-------------- sumfiles/gdb.sum.0 | 1697 +++++++++++++++++++-------------- sumfiles/gdb.sum.1 | 346 +++++-- sumfiles/gdb.sum.2 | 268 ++++-- sumfiles/gdb.sum.3 | 182 ++++ 29 files changed, 2654 insertions(+), 1826 deletions(-) create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.3