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_build/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 79785be91ad 243: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] discards e6bf6dd8fc5 242: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] discards 9c819878e51 241: onsuccess: #27: 6: Success after binutils/gcc/linux/gl [...] discards 3c3a04bd9bf 240: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] discards ec0d76621d8 239: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] discards fd15d2d9b41 238: onsuccess: #22: 6: Success after binutils/gcc/linux/gd [...] discards 3c1c86f74ed 237: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] discards 788c0c2b963 236: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards 265780badfd 235: onsuccess: #19: 6: Success after binutils/gcc/linux/gl [...] discards afa76392a5c 234: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards f8965fd9e4b 233: onsuccess: #17: 6: Success after binutils/gcc/linux/gd [...] discards 682a23f5b99 232: onsuccess: #16: 6: Success after binutils/gcc/linux/gl [...] discards a9279b63eb3 231: onsuccess: #15: 6: Success after binutils/gcc/linux/gd [...] discards 4aa6e86e587 230: onsuccess: #14: 6: Success after binutils/gcc/linux/gl [...] discards 773773079c5 229: onsuccess: #13: 6: Success after binutils/gcc/linux/gl [...] discards d291c60640b 228: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards e51d0f33bea 227: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards 276e652fcfd 226: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards 1c555a063bb 225: onsuccess: #9: 6: Success after binutils/gcc/linux/gdb [...] discards 30c87d9474c 224: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 2fa9d890593 223: onsuccess: #7: 6: Success after binutils/gcc/linux/gli [...] discards dfc11fed5fd 222: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards d5b223ad930 221: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 579af5a8ecc 220: onsuccess: #4: 6: Success after binutils/gcc/linux/gdb [...] discards 5eab6eda8ad 219: onsuccess: #3: 6: Success after binutils/gcc/linux/gli [...] discards baa1c7151d9 218: onsuccess: #2: 6: Success after binutils/gcc/linux/gdb [...] discards 187b89e44f4 217: onsuccess: #1: 6: Success after binutils/gcc/glibc/gdb [...] discards 3032465a117 216: onsuccess: #642: 6: Success after binutils/gcc/linux/g [...] discards 9c45bff4229 215: onsuccess: #641: 6: Success after binutils/gcc/linux/g [...] discards b5339902af5 214: onsuccess: #640: 6: Success after binutils/gcc/linux/g [...] discards 043339dd761 213: onsuccess: #639: 6: Success after binutils/gcc/linux/g [...] discards e5ee44957df 212: onsuccess: #638: 6: Success after binutils/gcc/linux/g [...] discards 07c0ecc257c 211: onsuccess: #637: 6: Success after binutils/gcc/linux/g [...] discards a6844c6f8b5 210: onsuccess: #636: 6: Success after binutils/gcc/linux/g [...] discards 7e7b195fd09 209: onsuccess: #635: 6: Success after binutils/gcc/gdb: 35 [...] discards 9a5fc0664fa 208: onsuccess: #634: 6: Success after binutils/gcc/linux/g [...] discards b2808b19d87 207: onsuccess: #633: 6: Success after binutils/gcc/linux/g [...] discards cbe03424a4c 206: onsuccess: #632: 6: Success after binutils/gcc/linux/g [...] discards b0227dac99d 205: onsuccess: #631: 6: Success after binutils/gcc/linux/g [...] discards 9fcc8eddcc4 204: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards a9af9fdbfbb 203: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards 21973d2ad26 202: onsuccess: #628: 6: Success after binutils/gcc/glibc/g [...] discards a0e01611448 201: onsuccess: #627: 6: Success after binutils/gcc/glibc/g [...] discards 044fa61fbf4 200: onsuccess: #626: 6: Success after binutils/gcc/linux/g [...] discards b71844b7936 199: onsuccess: #625: 6: Success after binutils/gcc/linux/g [...] discards 1f7e18d9d24 198: onsuccess: #624: 6: Success after binutils/gcc/linux/g [...] discards 92e626236e4 197: onsuccess: #623: 6: Success after binutils/gcc/linux/g [...] discards 17e0500c8cc 196: onsuccess: #622: 6: Success after binutils/gcc/linux/g [...] discards 951b723eb57 195: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards f8db0658915 194: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards dc75dad0191 193: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards aae95c9f8a9 192: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards 97c65d47dd2 191: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards 4ba4feb9661 190: onsuccess: #616: 6: Success after binutils/gcc/linux/g [...] discards bf2a8b75676 189: onsuccess: #615: 6: Success after binutils/gcc/gdb: 16 [...] discards 90f71ced64f 188: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 718f11dfc55 187: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards 6ffb5bb956f 186: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards e6a5aaf1a9e 185: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards b01d5b237cd 184: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards 7d5575d43b9 183: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards 6424cbde678 182: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards dc88f33d17a 181: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards 93159f21032 180: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 55cd80b232c 179: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards c1892355b92 178: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards a48d83acd54 177: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards dd16f59bb5c 176: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards e87ac4469ab 175: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards 622635fd737 174: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards e9c2a46fa05 173: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards 80ac33d7771 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/g [...] discards b24abfadac7 171: onsuccess: #596: 5: Success after gdb: 21 commits discards 63511f105b9 170: force: #595: 5: Failure after gdb-13-branchpoint-245-g [...] discards 4242a33270b 169: force: #594: 6: Success after gdb: 2 commits discards 1ae3460bd24 168: onsuccess: #593: 6: Success after linux: 10 commits discards c232c02e44f 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416- [...] discards f0a0295c128 166: onsuccess: #590: 6: Success after gcc: 23 commits discards 751bce5587e 165: onsuccess: #589: 6: Success after binutils: 24 commits discards ba726ff19cf 164: onsuccess: #587: 6: Success after binutils/gcc/linux/g [...] discards 9e7ddb99c43 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards 5bb8c3ce32e 162: onsuccess: #585: 6: Success after binutils/gcc/linux/g [...] discards 3d9973dce30 161: onsuccess: #584: 6: Success after binutils/gcc/linux/g [...] discards e08f4dfbcbd 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 [...] discards 25d791233f8 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 [...] discards 7b019cdf387 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 [...] discards da4fe9b659e 157: onsuccess: #580: 6: Success after binutils/gcc/linux/g [...] discards fec9fc61f7e 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 [...] discards 9ba4242daca 155: onsuccess: #578: 6: Success after binutils/gcc/linux/g [...] discards cc047c45360 154: onsuccess: #577: 6: Success after binutils/gcc/linux/g [...] discards cd779cb18a6 153: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 40e293a609e 152: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards dc3c037edc8 151: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 9ce99426730 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/g [...] discards 163c5fa55a3 149: onsuccess: #572: 6: Success after binutils/gcc/linux/g [...] discards b0bfb729311 148: onsuccess: #571: 6: Success after binutils/gcc/linux/g [...] discards 8aba344cbe6 147: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards 061efe8d73d 146: onsuccess: #569: 6: Success after binutils/gcc/linux/g [...] discards 0e316a622fa 145: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards 4eae6361531 144: onsuccess: #567: 4: Success after gcc: 12 commits discards 62de3e3154a 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g [...] new da8a559ca1c 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g [...] new bed7a960185 144: onsuccess: #567: 4: Success after gcc: 12 commits new d6d02a1d103 145: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new 1adae74290d 146: onsuccess: #569: 6: Success after binutils/gcc/linux/g [...] new eca694ccff5 147: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new f094e47b22b 148: onsuccess: #571: 6: Success after binutils/gcc/linux/g [...] new e9ae2c5689c 149: onsuccess: #572: 6: Success after binutils/gcc/linux/g [...] new e91c3b913e5 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/g [...] new 9fd1f49fbe1 151: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 47726a5ceb9 152: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new b335520d99d 153: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new 8fb10c74b37 154: onsuccess: #577: 6: Success after binutils/gcc/linux/g [...] new ed4877ca08f 155: onsuccess: #578: 6: Success after binutils/gcc/linux/g [...] new 854c9384f8f 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 [...] new a9b4e95d419 157: onsuccess: #580: 6: Success after binutils/gcc/linux/g [...] new a0e0cd7cbee 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 [...] new b6cde8c45ee 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 [...] new 3f7cf9b2d74 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 [...] new 5e1c872adff 161: onsuccess: #584: 6: Success after binutils/gcc/linux/g [...] new e75c413cf33 162: onsuccess: #585: 6: Success after binutils/gcc/linux/g [...] new 0ce6554fcb4 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new 34b528c828f 164: onsuccess: #587: 6: Success after binutils/gcc/linux/g [...] new 86522ab6722 165: onsuccess: #589: 6: Success after binutils: 24 commits new b5e01e145b8 166: onsuccess: #590: 6: Success after gcc: 23 commits new d94851f3b5b 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416- [...] new 48066d01baa 168: onsuccess: #593: 6: Success after linux: 10 commits new 7121f3358aa 169: force: #594: 6: Success after gdb: 2 commits new d75b11d0d4f 170: force: #595: 5: Failure after gdb-13-branchpoint-245-g [...] new 3d62b3514a0 171: onsuccess: #596: 5: Success after gdb: 21 commits new b36b7740929 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/g [...] new 79bb0e6cb88 173: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new 1dc23459990 174: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 6802cd80347 175: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 9b7e46969e3 176: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new d07cba2153d 177: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 855217071e1 178: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 770f58acbe1 179: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new cfc196cb9e0 180: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new b0a400fabf5 181: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 94168d1849e 182: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new 9d9b39b5192 183: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new a1286a23682 184: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new 285501d4fe4 185: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new cc76ac5e825 186: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new 5b617ba9f86 187: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new 1baebdf3980 188: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new 8012df4a6bf 189: onsuccess: #615: 6: Success after binutils/gcc/gdb: 16 [...] new 0b24643e33f 190: onsuccess: #616: 6: Success after binutils/gcc/linux/g [...] new 6ae5c2bd94f 191: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new 5957f18767c 192: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new 863955573ea 193: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new b35e6a5e1b4 194: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new 0f4baf37f11 195: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new 94ca6a1fa1e 196: onsuccess: #622: 6: Success after binutils/gcc/linux/g [...] new 8ff78b7834f 197: onsuccess: #623: 6: Success after binutils/gcc/linux/g [...] new b060c45d048 198: onsuccess: #624: 6: Success after binutils/gcc/linux/g [...] new a3b9f3e7724 199: onsuccess: #625: 6: Success after binutils/gcc/linux/g [...] new 798b49be0c7 200: onsuccess: #626: 6: Success after binutils/gcc/linux/g [...] new 0fed3b9f2a8 201: onsuccess: #627: 6: Success after binutils/gcc/glibc/g [...] new 3f0a126d858 202: onsuccess: #628: 6: Success after binutils/gcc/glibc/g [...] new 48ba589bffd 203: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new be0f479c732 204: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new 1c91d129e00 205: onsuccess: #631: 6: Success after binutils/gcc/linux/g [...] new 4f8cd966431 206: onsuccess: #632: 6: Success after binutils/gcc/linux/g [...] new 77c15dfaf06 207: onsuccess: #633: 6: Success after binutils/gcc/linux/g [...] new d5b589a527c 208: onsuccess: #634: 6: Success after binutils/gcc/linux/g [...] new 6607f4857c7 209: onsuccess: #635: 6: Success after binutils/gcc/gdb: 35 [...] new 53b9d2b9da0 210: onsuccess: #636: 6: Success after binutils/gcc/linux/g [...] new 173ba741e66 211: onsuccess: #637: 6: Success after binutils/gcc/linux/g [...] new fe30136b98f 212: onsuccess: #638: 6: Success after binutils/gcc/linux/g [...] new b14da5524f8 213: onsuccess: #639: 6: Success after binutils/gcc/linux/g [...] new 7ebb69307ac 214: onsuccess: #640: 6: Success after binutils/gcc/linux/g [...] new f3f405a331e 215: onsuccess: #641: 6: Success after binutils/gcc/linux/g [...] new 180b807df64 216: onsuccess: #642: 6: Success after binutils/gcc/linux/g [...] new a7c10535ec3 217: onsuccess: #1: 6: Success after binutils/gcc/glibc/gdb [...] new b3992bd4898 218: onsuccess: #2: 6: Success after binutils/gcc/linux/gdb [...] new c0ce1bcd78b 219: onsuccess: #3: 6: Success after binutils/gcc/linux/gli [...] new 83a07090bc2 220: onsuccess: #4: 6: Success after binutils/gcc/linux/gdb [...] new e2b83bcdaa8 221: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new f999d675cff 222: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 1ece3853107 223: onsuccess: #7: 6: Success after binutils/gcc/linux/gli [...] new cab6595533b 224: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 2fcbadf46bf 225: onsuccess: #9: 6: Success after binutils/gcc/linux/gdb [...] new 07b5aae2c16 226: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new 30be485fa70 227: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new 71f49a95d6a 228: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 009fcce5902 229: onsuccess: #13: 6: Success after binutils/gcc/linux/gl [...] new f50112b61eb 230: onsuccess: #14: 6: Success after binutils/gcc/linux/gl [...] new 515b136c5c6 231: onsuccess: #15: 6: Success after binutils/gcc/linux/gd [...] new 2ddc02c1796 232: onsuccess: #16: 6: Success after binutils/gcc/linux/gl [...] new c886f1b8d9e 233: onsuccess: #17: 6: Success after binutils/gcc/linux/gd [...] new b0c73efe29a 234: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new 872b25100e6 235: onsuccess: #19: 6: Success after binutils/gcc/linux/gl [...] new 1e389b14046 236: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new b94c14e8657 237: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] new d6a5795eb05 238: onsuccess: #22: 6: Success after binutils/gcc/linux/gd [...] new 87204b6aa6c 239: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] new 0f756df9c25 240: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] new 9063b358ef1 241: onsuccess: #27: 6: Success after binutils/gcc/linux/gl [...] new be8656d4462 242: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] new bc49e136531 243: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] new abc5419b646 244: onsuccess: #30: 6: 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 (79785be91ad) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 2040 -> 2004 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2492 bytes 04-build_abe-binutils/console.log.xz | Bin 35028 -> 34968 bytes 05-build_abe-gcc/console.log.xz | Bin 203196 -> 204060 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8404 -> 8888 bytes 08-build_abe-glibc/console.log.xz | Bin 241484 -> 240976 bytes 09-build_abe-gdb/console.log.xz | Bin 34644 -> 34700 bytes 10-check_regression/console.log.xz | Bin 4104 -> 4076 bytes 10-check_regression/jira-body.txt | 1 - 10-check_regression/mail-body.txt | 2 +- 11-update_baseline/console.log | 68 +++++++++++++++++------------------ 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 21 files changed, 59 insertions(+), 61 deletions(-) delete mode 100644 10-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt