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 0ce391bee57 209: force: #37: 1: Success after baseline build: no new commits discards b547d0830d4 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f7841512691 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 75e470a9e55 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 63c29ebaf42 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards b2d3ded54a3 204: force: #26: : Failure after baseline build: no new commits discards 65e19cac23c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 43082f47af2 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 89b06d145d6 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 29a2f599d92 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 482da487cab 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7ee817e4694 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 636d94309db 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7aa4de8db7f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 4453da926c3 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f176cb32866 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 011e81149e2 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2171fc83138 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 82d355fbde7 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 485c62d2c54 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 3cc8dd5a0d8 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards fb7bff4f02f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards bf3add9a0ed 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c4ead1bfa3f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 36b8c0f5cd6 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3a1748fe331 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 758d5756c52 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 1d80dd3a8bd 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 3e089deed6a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards aaaef43488c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards ebe029f8596 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards c630cac9434 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards daf7e5ae0bc 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 62cd254ff70 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards b5e1b30e488 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 2370a444ceb 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards b1581e0cda2 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 84fb688b369 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 1c3acde3f51 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 6fd9164db30 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 959a279299f 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 76bc246ed38 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards b1de4424b4f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards b54eb2965b4 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 3594de2e6bb 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards b8d9f3890fb 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards d4c14b49695 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 181fe6e11c1 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards a1d245e0b05 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 4c6a214dbeb 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 3f904f02120 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 758b2fb1da3 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards e5aa28e1dd0 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards cf89547b8e3 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards c58a52caa9d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 668ff3db94a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards fd90335d2f0 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 3de818f37c7 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards f9952a74c87 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 46f007587b4 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 3d0b149db61 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards c02c58bf30c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards cab8bf23028 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 887560771ba 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 6a91d723b00 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 9119ea11351 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards a507defe4ab 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards a50d70001b4 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards c68a03ca077 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 43aa91ffeb7 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards c2cd7424c81 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 8f57d5cda77 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards b469070ad3d 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 593837a8f96 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards b15291f08f8 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 694e6155a6e 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards a2c9e2e5ab5 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards bbefca5c00a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 800e17600ec 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 2cc86207558 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards dd15cbb77dc 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 62b219ba8eb 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 3bd4d6da4c9 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 5a217ae99b2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 8d981c1890a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 8d11c8440a9 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 780daca1573 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 6e370c5aa1d 122: onsuccess: #909: 1: Success after linux: 2753 commits discards f7f7e20f976 121: onsuccess: #908: 1: Success after glibc: 2 commits discards f8e749e7a25 120: onsuccess: #906: 1: Success after binutils: 29 commits discards f00748b1c55 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 9d874a66a1d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 5bb1f8d4214 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 0b3ff513d33 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards df54842e0dc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 4b83264f913 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 8a68baba64a 113: onsuccess: #898: 1: Success after linux: 3 commits discards 7197a1d34f7 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 801ded60601 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 1d534f5f882 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards d3b6a5d9a5d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 627d2503b3e 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new d410fdc3b82 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 80003363db3 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 18580814606 112: onsuccess: #896: 1: Success after binutils: 24 commits new ec424f45c60 113: onsuccess: #898: 1: Success after linux: 3 commits new 425c99b359b 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 2bf7f8e1eab 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 38563c511a4 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 2c1e715b944 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new cff94b3a2e0 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 656f2bb5c0d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 731e2c7e3b9 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5db03b718ea 121: onsuccess: #908: 1: Success after glibc: 2 commits new fb848e675b1 122: onsuccess: #909: 1: Success after linux: 2753 commits new 7253598a383 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 2a3091cd051 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 31743e07e45 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 595fa8d265f 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new aa2278e5767 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 06e1bf4b385 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new f8a3eccea81 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new c3f60a72e60 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new e355f320eee 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 7363a8fdde0 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new b8516a4eaff 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 2916b405c14 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new f7ba91d61b2 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 9d29e6d247c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 6656cfb526b 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 853b25605b9 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 15e7a249fc4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 61d9fe17a69 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 22f5fccd12d 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 254f408c844 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new b3eaee1f0c8 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 92032964d10 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new ea9eba696d5 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 2334c4d32f1 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 6c3cd7ee006 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 6cade2ed4f3 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new ef2a7186b78 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new e96a397d2d5 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new a37a2d1a12d 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new b2ecb57e34d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 20b4686abbf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new da9bc55615f 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 78ab5b5b09a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 9b71949b128 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new cc2dcd4fd64 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new aac354ec8f1 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 8c021b46d86 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new dc6c2f914d0 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 021aa6ef184 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 0695e4e5c08 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 9f3f793fbfa 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 70e353a2588 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 76f30c0871f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 48cda5bf198 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 735bd9b8ed1 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 5f82296c7d5 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new d5830749349 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new c0468d9d0ea 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 0d88196c37e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 1f4df512593 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new d9f83394693 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 8d2307242e1 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 57ec164a36c 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new cb8c0ba9506 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 5659488c41c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new f57fc347b60 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 60bbe8b2874 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new f6f744ebf0f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new a75637cc463 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 0792b542e90 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new c21f11233ab 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new f19f2d0915a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 10f9bbf5346 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new cce1bb6995e 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ecd8d4c35c5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5f3fcbb62db 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 40ebed4a8b2 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 01419fba0fa 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4d11b247f9a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 98a7a3d9465 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 71e15249434 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new ad0d7e97d7a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 42a93a41033 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 089056d0484 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e0bb0483201 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 35bc5e8284e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 071f2a50316 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 7a0f6af0e57 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a34ffbfca89 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 2924a1fe867 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 4a0460459a9 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b26e006b33e 204: force: #26: : Failure after baseline build: no new commits new 05cd5418da9 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new ba435182915 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 37cc49b4f9f 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 2b488db4877 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new a9e2ae467b5 209: force: #37: 1: Success after baseline build: no new commits new b5c198a82ac 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...]
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 (0ce391bee57) \ 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 2232 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 35348 -> 35408 bytes 04-build_abe-gcc/console.log.xz | Bin 204024 -> 203412 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8368 bytes 07-build_abe-glibc/console.log.xz | Bin 242368 -> 242704 bytes 08-build_abe-gdb/console.log.xz | Bin 35072 -> 35108 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3792 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2968 -> 2952 bytes 11-check_regression/console.log.xz | Bin 2848 -> 3728 bytes 11-check_regression/results.compare | 24 +---------- 11-check_regression/results.compare2 | 74 +++++++++++++++++++++++++++++++++- 12-update_baseline/console.log | 46 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 17 ++++---- sumfiles/gdb.log.0.xz | Bin 1940980 -> 1948520 bytes sumfiles/gdb.log.1.xz | Bin 27040 -> 27172 bytes sumfiles/gdb.log.2.xz | Bin 5424 -> 5416 bytes sumfiles/gdb.log.3.xz | Bin 5424 -> 5412 bytes sumfiles/gdb.sum | 19 ++++----- sumfiles/gdb.sum.0 | 15 +++---- sumfiles/gdb.sum.1 | 17 ++++---- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 29 files changed, 137 insertions(+), 93 deletions(-)