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 9d03034a34b 246: onsuccess: #32: 6: Success after binutils/gcc/linux/gl [...] discards c1d1141df58 245: onsuccess: #31: 6: Success after binutils/gcc/linux/gd [...] discards 76389194e65 244: onsuccess: #30: 6: Success after binutils/gcc/linux/gd [...] discards 521de6944cf 243: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] discards f64059ee155 242: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] discards d7d40467ac0 241: onsuccess: #27: 6: Success after binutils/gcc/linux/gl [...] discards 0da15842b39 240: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] discards 8e81d5ef28c 239: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] discards f0fe33c5647 238: onsuccess: #22: 6: Success after binutils/gcc/linux/gd [...] discards b145500010d 237: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] discards ae4ce120afc 236: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards 5321c7c266a 235: onsuccess: #19: 6: Success after binutils/gcc/linux/gl [...] discards 710f7ba2017 234: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards ce4137c31ed 233: onsuccess: #17: 6: Success after binutils/gcc/linux/gd [...] discards a169f65259c 232: onsuccess: #16: 6: Success after binutils/gcc/linux/gl [...] discards 040248375a5 231: onsuccess: #15: 6: Success after binutils/gcc/linux/gd [...] discards 1d48a5725ad 230: onsuccess: #14: 6: Success after binutils/gcc/linux/gl [...] discards d1f2ab65b98 229: onsuccess: #13: 6: Success after binutils/gcc/linux/gl [...] discards 56eb551f83a 228: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards d41d7c6bb97 227: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards 7dff2ae997e 226: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards d845fcdf259 225: onsuccess: #9: 6: Success after binutils/gcc/linux/gdb [...] discards 83948049444 224: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 05a893451e5 223: onsuccess: #7: 6: Success after binutils/gcc/linux/gli [...] discards 697b4775099 222: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards 83f97ba2a0e 221: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 9de87a4385d 220: onsuccess: #4: 6: Success after binutils/gcc/linux/gdb [...] discards fba1b71c8db 219: onsuccess: #3: 6: Success after binutils/gcc/linux/gli [...] discards 28d917b038f 218: onsuccess: #2: 6: Success after binutils/gcc/linux/gdb [...] discards 047b22dbf08 217: onsuccess: #1: 6: Success after binutils/gcc/glibc/gdb [...] discards a23588c9175 216: onsuccess: #642: 6: Success after binutils/gcc/linux/g [...] discards 3495b3ff24c 215: onsuccess: #641: 6: Success after binutils/gcc/linux/g [...] discards b0f5e682197 214: onsuccess: #640: 6: Success after binutils/gcc/linux/g [...] discards 860245b6cc5 213: onsuccess: #639: 6: Success after binutils/gcc/linux/g [...] discards e055095ae27 212: onsuccess: #638: 6: Success after binutils/gcc/linux/g [...] discards c8a237d04a9 211: onsuccess: #637: 6: Success after binutils/gcc/linux/g [...] discards f2160e1cd44 210: onsuccess: #636: 6: Success after binutils/gcc/linux/g [...] discards c1de5c974b9 209: onsuccess: #635: 6: Success after binutils/gcc/gdb: 35 [...] discards 229f262feab 208: onsuccess: #634: 6: Success after binutils/gcc/linux/g [...] discards 27ef800eb6b 207: onsuccess: #633: 6: Success after binutils/gcc/linux/g [...] discards 3e17d9966b4 206: onsuccess: #632: 6: Success after binutils/gcc/linux/g [...] discards e3660f37028 205: onsuccess: #631: 6: Success after binutils/gcc/linux/g [...] discards 39131fb7344 204: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards 219121a3028 203: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards d565a4d8063 202: onsuccess: #628: 6: Success after binutils/gcc/glibc/g [...] discards 29842ad508a 201: onsuccess: #627: 6: Success after binutils/gcc/glibc/g [...] discards 9b6396f227b 200: onsuccess: #626: 6: Success after binutils/gcc/linux/g [...] discards 0583264e649 199: onsuccess: #625: 6: Success after binutils/gcc/linux/g [...] discards 71163eafd2e 198: onsuccess: #624: 6: Success after binutils/gcc/linux/g [...] discards aa934b7c86b 197: onsuccess: #623: 6: Success after binutils/gcc/linux/g [...] discards bd39a30ef98 196: onsuccess: #622: 6: Success after binutils/gcc/linux/g [...] discards 0878debf47f 195: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards 0b38bfcd632 194: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards 42f404effc4 193: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards e0130087581 192: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards 7256c9a20e5 191: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards 0927c7ad01a 190: onsuccess: #616: 6: Success after binutils/gcc/linux/g [...] discards 83df327ff63 189: onsuccess: #615: 6: Success after binutils/gcc/gdb: 16 [...] discards 2f98c691132 188: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 19fece69071 187: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards 889cce95c1b 186: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards 110133845b9 185: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards b453e0e5098 184: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards b726fb7ff01 183: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards dcdaba8ba49 182: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards a3d6b76f250 181: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards 1ea4226e9ef 180: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 765eb9166ae 179: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards 28606a2978e 178: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards 4d728a61b5c 177: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards 499ef60d0c3 176: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards c34d17581a6 175: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards 97b60de7836 174: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards 3d38c34befd 173: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards bbdd9ed7fc6 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/g [...] discards 3a80cb0e51d 171: onsuccess: #596: 5: Success after gdb: 21 commits discards 5438ebd33a7 170: force: #595: 5: Failure after gdb-13-branchpoint-245-g [...] discards a3fe4c3eabe 169: force: #594: 6: Success after gdb: 2 commits discards 553fd2d0491 168: onsuccess: #593: 6: Success after linux: 10 commits discards 05e60a3119e 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416- [...] discards c7d70ac49c6 166: onsuccess: #590: 6: Success after gcc: 23 commits discards f481cc84603 165: onsuccess: #589: 6: Success after binutils: 24 commits discards 5794dcee468 164: onsuccess: #587: 6: Success after binutils/gcc/linux/g [...] discards 97c01fdd5a2 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards e8d76828eca 162: onsuccess: #585: 6: Success after binutils/gcc/linux/g [...] discards 6418419ba8c 161: onsuccess: #584: 6: Success after binutils/gcc/linux/g [...] discards c9135bc3a6d 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 [...] discards 69151af4056 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 [...] discards be22f2dcf1c 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 [...] discards 565a65243e0 157: onsuccess: #580: 6: Success after binutils/gcc/linux/g [...] discards aef3589f9d3 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 [...] discards 5f130911262 155: onsuccess: #578: 6: Success after binutils/gcc/linux/g [...] discards 739be8cc791 154: onsuccess: #577: 6: Success after binutils/gcc/linux/g [...] discards 8ae185e5f0d 153: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 8133314ecd9 152: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards f9cdd970873 151: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 3d22e698d31 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/g [...] discards 8295453c180 149: onsuccess: #572: 6: Success after binutils/gcc/linux/g [...] discards 988b75c606f 148: onsuccess: #571: 6: Success after binutils/gcc/linux/g [...] discards e3f761abdee 147: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards 306d53e83dd 146: onsuccess: #569: 6: Success after binutils/gcc/linux/g [...] new d3a8b1bd122 146: onsuccess: #569: 6: Success after binutils/gcc/linux/g [...] new 810d87c0814 147: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new ad682a2ba6d 148: onsuccess: #571: 6: Success after binutils/gcc/linux/g [...] new ff87d84743e 149: onsuccess: #572: 6: Success after binutils/gcc/linux/g [...] new 99f81d4d90a 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/g [...] new 816d9e45f93 151: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 9054943dc12 152: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new deefdb2545f 153: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new 9dd716e6865 154: onsuccess: #577: 6: Success after binutils/gcc/linux/g [...] new ff1df529d38 155: onsuccess: #578: 6: Success after binutils/gcc/linux/g [...] new b4dc025de91 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 [...] new 114ab5fd4b4 157: onsuccess: #580: 6: Success after binutils/gcc/linux/g [...] new 61cfd0d3e17 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 [...] new c94ecbd1231 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 [...] new 4892f42f7a8 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 [...] new 34e53592e48 161: onsuccess: #584: 6: Success after binutils/gcc/linux/g [...] new c7ede79320d 162: onsuccess: #585: 6: Success after binutils/gcc/linux/g [...] new e4eecff4369 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new 6141d6182c2 164: onsuccess: #587: 6: Success after binutils/gcc/linux/g [...] new a8cae28e44b 165: onsuccess: #589: 6: Success after binutils: 24 commits new df50d3e892b 166: onsuccess: #590: 6: Success after gcc: 23 commits new 4f266006d8d 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416- [...] new 203f94c48ca 168: onsuccess: #593: 6: Success after linux: 10 commits new 6ea2eada2cf 169: force: #594: 6: Success after gdb: 2 commits new 42e4e640333 170: force: #595: 5: Failure after gdb-13-branchpoint-245-g [...] new 76bee53ff3c 171: onsuccess: #596: 5: Success after gdb: 21 commits new 33df955bb38 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/g [...] new e25d774105d 173: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new 0be28ace740 174: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 3e15b5f0109 175: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 5c8057b95db 176: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new ee8c5c2832d 177: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 35aa06a0550 178: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 3de36f8a6a0 179: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new a3ab1a58011 180: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new 781b592b3c1 181: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 05285ae5258 182: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new b7aa80ae8d7 183: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new b4b4ffd9167 184: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new a83832458bc 185: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new f79bd32a6bb 186: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new c4608ae7a5c 187: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new ba807ccbb51 188: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new 7d9af119549 189: onsuccess: #615: 6: Success after binutils/gcc/gdb: 16 [...] new e08cbbe8ac2 190: onsuccess: #616: 6: Success after binutils/gcc/linux/g [...] new 8cbadff3058 191: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new 62804f17199 192: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new da0f8f0d541 193: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new 384d36dca13 194: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new 0680b133fa1 195: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new e529169aa3b 196: onsuccess: #622: 6: Success after binutils/gcc/linux/g [...] new 8769b857e0d 197: onsuccess: #623: 6: Success after binutils/gcc/linux/g [...] new 33a1524d3ad 198: onsuccess: #624: 6: Success after binutils/gcc/linux/g [...] new 277599e25bc 199: onsuccess: #625: 6: Success after binutils/gcc/linux/g [...] new e23646f266e 200: onsuccess: #626: 6: Success after binutils/gcc/linux/g [...] new 7bb0bd5af74 201: onsuccess: #627: 6: Success after binutils/gcc/glibc/g [...] new b5caa8395a5 202: onsuccess: #628: 6: Success after binutils/gcc/glibc/g [...] new d56e7df1a2e 203: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new 1a882dfca9b 204: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new 717067bef45 205: onsuccess: #631: 6: Success after binutils/gcc/linux/g [...] new f46674ec505 206: onsuccess: #632: 6: Success after binutils/gcc/linux/g [...] new 88b0229c721 207: onsuccess: #633: 6: Success after binutils/gcc/linux/g [...] new 69c5742c94e 208: onsuccess: #634: 6: Success after binutils/gcc/linux/g [...] new 44b69b839c0 209: onsuccess: #635: 6: Success after binutils/gcc/gdb: 35 [...] new c571b2ff9f6 210: onsuccess: #636: 6: Success after binutils/gcc/linux/g [...] new ff223830408 211: onsuccess: #637: 6: Success after binutils/gcc/linux/g [...] new e258a22751e 212: onsuccess: #638: 6: Success after binutils/gcc/linux/g [...] new 9609209d8b9 213: onsuccess: #639: 6: Success after binutils/gcc/linux/g [...] new 7b756d5383a 214: onsuccess: #640: 6: Success after binutils/gcc/linux/g [...] new f722dba8ecf 215: onsuccess: #641: 6: Success after binutils/gcc/linux/g [...] new 42e8c39061a 216: onsuccess: #642: 6: Success after binutils/gcc/linux/g [...] new e407f9bf399 217: onsuccess: #1: 6: Success after binutils/gcc/glibc/gdb [...] new 62e1a256352 218: onsuccess: #2: 6: Success after binutils/gcc/linux/gdb [...] new 47c0e1c8ce9 219: onsuccess: #3: 6: Success after binutils/gcc/linux/gli [...] new fc937256fa8 220: onsuccess: #4: 6: Success after binutils/gcc/linux/gdb [...] new 9d7ef8a38a9 221: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new ba5f3755052 222: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 95dc3fec5c8 223: onsuccess: #7: 6: Success after binutils/gcc/linux/gli [...] new 358c5f81a1f 224: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 953009bd650 225: onsuccess: #9: 6: Success after binutils/gcc/linux/gdb [...] new 24af68ec0cf 226: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new d04cf1eb8d4 227: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new 8308c8112a2 228: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new cfd5f1ba362 229: onsuccess: #13: 6: Success after binutils/gcc/linux/gl [...] new 27646f8f710 230: onsuccess: #14: 6: Success after binutils/gcc/linux/gl [...] new 2a760253b03 231: onsuccess: #15: 6: Success after binutils/gcc/linux/gd [...] new aaf4cd3fe2b 232: onsuccess: #16: 6: Success after binutils/gcc/linux/gl [...] new ea2e4a409a5 233: onsuccess: #17: 6: Success after binutils/gcc/linux/gd [...] new f0d845c797e 234: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new 39c0a203cf4 235: onsuccess: #19: 6: Success after binutils/gcc/linux/gl [...] new fb3699bcd60 236: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new 463d6d68fd0 237: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] new 2bfe9604526 238: onsuccess: #22: 6: Success after binutils/gcc/linux/gd [...] new 76fe0d54abb 239: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] new 81d88660c08 240: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] new 80692f5844f 241: onsuccess: #27: 6: Success after binutils/gcc/linux/gl [...] new c161679efe8 242: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] new e930b26f0a1 243: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] new ad22fe3c9be 244: onsuccess: #30: 6: Success after binutils/gcc/linux/gd [...] new aa21f44ff33 245: onsuccess: #31: 6: Success after binutils/gcc/linux/gd [...] new 220adf08603 246: onsuccess: #32: 6: Success after binutils/gcc/linux/gl [...] new a999da31047 247: onsuccess: #34: 6: [TCWG CI] Success after binutils/gc [...]

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 (9d03034a34b) \ 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 2064 -> 2100 bytes 02-prepare_abe/console.log.xz | Bin 2484 -> 2520 bytes 04-build_abe-binutils/console.log.xz | Bin 34776 -> 35172 bytes 05-build_abe-gcc/console.log.xz | Bin 202300 -> 204156 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8192 -> 8536 bytes 08-build_abe-glibc/console.log.xz | Bin 241132 -> 241300 bytes 09-build_abe-gdb/console.log.xz | Bin 34564 -> 34980 bytes 10-check_regression/console.log.xz | Bin 4132 -> 4552 bytes 10-check_regression/mail-body.txt | 31 ---------------- 10-check_regression/mail-subject.txt | 1 - 11-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 31 ---------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 ++++++++++---------- 24 files changed, 92 insertions(+), 122 deletions(-) delete mode 100644 10-check_regression/mail-body.txt delete mode 100644 10-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt