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-arm in repository toolchain/ci/base-artifacts.
discards 982a4a459de 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] discards e5a153833ed 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] discards 20919f50a4f 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gd [...] discards 6bf4b51478f 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gl [...] discards f1b3d7c5149 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] discards 0276beec2fb 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gl [...] discards 36ba81137dd 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] discards 3c810d7e602 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards 59658d1d551 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] discards 66f1ed1bf5b 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards c56f8f2f30d 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] discards de57d9dfc05 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards e8b60f83cd4 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards 327ed4f2d3f 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards d904f96b0fb 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] discards ef66656b0c1 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards d459784b259 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] discards 64496d59b84 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards d6dc8468659 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 87f6a15c47b 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] discards 14e6faf6cd6 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] discards ee4dfba88d5 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] discards 2c1deedbb59 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] discards 60d122d7a9c 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards 2ff660696a5 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards 219c266b75a 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] discards 3ece73d67d7 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards 4c82e079a93 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards f6c01901659 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards 1d8884fa3b6 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards 5997018d91b 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards 3818274c118 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] discards 3e5601884e0 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 33dafe42185 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards bf5e837899c 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards a6f92033ed6 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards fa487d56c86 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards e51c85086f2 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards c266a88d2c9 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards 7d9243bf411 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards ab6cc2e6058 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 7018967d914 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards e6daf98ba2b 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards 947c1e7a5a1 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards 19edb5ab077 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] discards 393eaa55577 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards 9cb60d58cbe 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards c81a32eb5cb 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards 2e77af82d4e 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards 184fddd0d5f 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] discards 55c44c4eb33 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] discards 4aef2254872 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] discards 0a654f6ecd7 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] discards 8d5a71af91e 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] discards 256fdf0282d 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] discards 04ac271526b 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] discards b3a68fc1f68 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] discards ce9b9105302 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] discards 4606784c947 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] discards 064a3820a04 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards fdc3f7d425b 162: onsuccess: #579: 6: Success after gcc: 11 commits discards aff17c3819e 161: onsuccess: #578: 6: Success after binutils: 15 commits discards ba79ce9e896 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 635ca8b6210 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards bf7290df253 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 7b30af03521 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 1132fbbc7ae 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] discards 1f595c56b73 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] discards 036fb9c13e0 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards 2e74aefd755 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] discards 8414ee2cfb0 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards e025292d2ae 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] discards f7a0c8ccec6 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] discards 690ccc50eab 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] discards 058389ed915 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] discards 07629c01139 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] discards 13e33c6fed9 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] discards 189e1d9f123 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] discards 56f7b46c579 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] discards 53abe05a98c 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards ecb738d7ba0 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards fc2ea8fe476 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards 7af73415a72 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards c5a78330336 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards 4ff45afa1ab 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 8d926b3f251 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards 1373a1c965f 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards 8b5aa7f3a64 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 6344c707129 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 718659aefaf 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 06c210c1dd6 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 70f78771b5d 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 3079b5d8461 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 96f8d7b61a2 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 0770074440a 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards a004fe64998 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards c463c68849f 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] discards c1c395b7bbe 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] discards ce0a2a9e271 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 7984b94e5f7 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] discards b7caa502fcc 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] new abc5c76ba35 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] new b7efbc0e2d5 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new 5255332be6a 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new f8c5421b7eb 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] new 5c0e82d9e08 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] new 8a33c4a4f55 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new e9f385f1796 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 62937c32170 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 04216d28981 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new b3978648053 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new b7381ddc561 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new b1cbfbf4ed8 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 568fa810eca 134: onsuccess: #544: 6: Success after binutils: 18 commits new 84aaaa048dd 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new 2936a47a076 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new 8744555076f 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new b51b5b93758 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 0b9277486fe 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 992395ce667 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 97bd680ba98 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new ea48472933a 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 71810a218de 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new fb380e9d663 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] new 422bda05926 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] new cbbc51adcd8 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] new 7f0884a8216 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] new 47b26376dc8 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] new 37f9e854e39 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] new fccff36ef68 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] new 25ed639f90e 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] new db71453d442 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new 70c92f7ac22 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] new 7242507f7d9 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new f75ba828541 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] new e1860b9d288 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] new 2558294c899 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new e93e5c8a7ab 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 6bcef5e4939 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new c4bb4f6121a 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new 5c501f552ab 161: onsuccess: #578: 6: Success after binutils: 15 commits new 44af91abc8e 162: onsuccess: #579: 6: Success after gcc: 11 commits new a1f66fa0c11 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new 0e25e69d6a7 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] new 54b71411de8 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] new b2f7b37d192 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] new d91e1687bb4 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] new c2a39327f07 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] new c4656eca830 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] new 6a5098bf20c 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] new 0f0399069c7 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] new 38badabda42 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] new 2c89d7b2519 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] new 915b086d3f9 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new cf56f7ff784 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 64e36616292 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 90af5cc582d 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new 16e49533327 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] new c1a222a5429 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 6b6fa7b893e 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 3159c5fac78 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new 83663e2e3ce 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new d29c373aefa 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new dc854677a30 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new d4c87d78a2b 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new aa071f8847a 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new fda1a844713 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new b976ecfad57 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new 0af7fe503f6 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new 7f0c55d7cc4 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new b70f1e450d3 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] new 2c7fc420e9f 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new 70b303e858e 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new 802aa889cf4 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new db320885a7a 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new 1c19f10258d 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new a3da5d129d6 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] new 2c676a48595 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new fd513738534 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new 267ca5a1cc5 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] new d41b4e9ec12 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] new 7b677f06be6 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] new 8838e5a56d0 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] new 5f09bd415b0 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new ed3ced701cc 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 3d2cf1398e4 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] new 34c4837f62c 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 0a353621b39 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] new ab119b5bdb7 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new fe734760780 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new afdded6c0bc 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 0a3b6e75485 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] new a4c44a24e45 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new 24e2d81a648 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] new 1a984e4eca0 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new e309ea06335 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] new 75dbb90fe26 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gl [...] new 8fbcb5d0d48 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] new 0f60eb35888 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gl [...] new e0ac853de60 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gd [...] new 90eb24c96fc 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] new 14d3cd5142a 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] new 4a9e2ef5cbf 223: onsuccess: #29: 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 (982a4a459de) \ 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 1780 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2512 bytes 04-build_abe-binutils/console.log.xz | Bin 48968 -> 49596 bytes 05-build_abe-gcc/console.log.xz | Bin 235204 -> 235016 bytes 07-build_abe-linux/console.log.xz | Bin 8860 -> 8196 bytes 08-build_abe-glibc/console.log.xz | Bin 233184 -> 233632 bytes 09-build_abe-gdb/console.log.xz | Bin 46568 -> 47728 bytes 10-check_regression/console.log.xz | Bin 4028 -> 4120 bytes 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 | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 18 files changed, 59 insertions(+), 59 deletions(-)