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 e0f67d0547f 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards 029aac08011 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards f53d22f113d 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards ab0476a76c4 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] discards acfb06df867 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 8968705f1fd 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] discards 16edecddc86 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards 9c594500c67 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 5cd944100cd 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] discards 0a0e8c42fbc 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] discards e687d28ee4e 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] discards 226e29b6581 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] discards dcdce533c4b 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards ce4ddf3e14a 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards 032907c1914 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] discards 2a46c70cf7a 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards 34b56781d43 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards 19c82a8f593 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards b1b107984f9 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards e4bf65d8fd4 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards 4180118efd6 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] discards a9a90a95b90 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 9406412e6d0 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards 2085465a765 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards 07af58eed84 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards 595f5dcbd37 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards 22ee3f440e2 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards acfcd9306df 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards f9477849c4a 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards 357b5870edb 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 37cac5623ab 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards ffd3e1acc69 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards 9a1cd32c813 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards fd003f0e824 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] discards 9b9fb0310a2 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards b4ed5bbeb2f 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards 4d5737025ce 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards 8a52b1f974e 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards 51fcf23b039 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] discards 9dd31ec6171 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] discards a39863d5619 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] discards d2a799cdac3 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] discards 17d2a44be9d 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] discards da179ebf25a 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] discards 383c9f82752 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] discards 5bfffc4bc8c 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] discards 30a601897ea 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] discards baf0ed6143e 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] discards d82e2632bd4 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards b2ee12dd475 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 30c0f84d3fc 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 03960508800 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 7c96f1b155d 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards 0d9b4d8cc39 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 9e41ec2fb43 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards ca846979e45 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] discards 0b883356e58 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] discards 30df85ac37a 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards a2b61d48a18 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] discards 5daf243b288 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards fab7537b853 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] discards 3e50b5df2be 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] discards 3057dd01379 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] discards 16c65e4004f 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] discards 410001ac528 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] discards be30caa11ea 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] discards a7fa2726664 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] discards 48f1a742115 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] discards b70e500d57b 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards 0bfec181f29 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 38f999bf48d 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards c76b462739b 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 304fa8c6e17 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards d48d00e149c 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 4141c1d3447 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards 5c18bc8a012 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards a669318a6a6 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 87c1bf2ead2 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 5e7d09d42fb 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 1ae4fa7a70f 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 5f0990edfbf 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 436524ff437 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 6a011a35dce 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards d7a47449a43 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards ddea85ffddf 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 5aeeea40bf0 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] discards dc93f18b418 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] discards 3eb748f6452 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 95e5a69ff3c 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] discards 4ee4237a93c 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] discards c2e8d216490 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 400188dcfdc 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards c0171362ab5 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] discards 231bee2cd16 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 1ebc7d3a018 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards 07a0d2d7739 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] discards 7d7c70cd0e2 115: onsuccess: #524: 6: Success after binutils/gcc/linux/g [...] discards 0af8a91f9e9 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards e74bc0e1735 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 643725604d8 112: force: #521: 1: Failure after basepoints/gcc-13-3918-g [...] discards 6d9b4304c9a 111: force: #520: 6: Success after gcc: 9 commits new a02ab5da7fd 111: force: #520: 6: Success after gcc: 9 commits new 2cc1ba1fae9 112: force: #521: 1: Failure after basepoints/gcc-13-3918-g [...] new 89638af2766 113: onsuccess: #522: 1: Success after gcc: 12 commits new 7eb89d2296f 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 324133ba67b 115: onsuccess: #524: 6: Success after binutils/gcc/linux/g [...] new 444d6f73672 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] new b504ed82856 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 99831224f63 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new 8a65ebf1dbe 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] new a16c0599dd9 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 060b80ea75d 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 1acc55170d4 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] new 3926ed11310 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new b8fbe1f304f 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new b4c8db8a4d3 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] new d4a248b086f 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] new 4474672ab6a 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 2bab3fed920 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new ae2921ca82b 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 8fb075875c5 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 631fedad5d0 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 9bc97a6ecb9 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new cb5fb8d8eb5 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new a92e259522d 134: onsuccess: #544: 6: Success after binutils: 18 commits new 2ef2bb0daab 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new 61684c45daf 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new 0a67f7b5db3 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new 05dfbc6ae96 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 2c8895f6b0b 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 86530795757 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 43f639d7243 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 92c5029e371 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 7f193c4e098 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 51b4806d88b 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] new 596de9651d6 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] new 18ceff22a03 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] new c31bf78c580 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] new 2fcf766dd03 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] new ec9bd6fe79a 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] new 398dec09e22 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] new 85c00edd79e 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] new d4cb1618054 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new 7a02c94e272 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] new c8e61ad1e2b 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new 974fe7c6797 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] new c87be1ea2a3 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] new d6d864c8b46 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new 35e20613fc1 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 5937ce7a797 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new a59024fdc1c 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new 9ad730f149f 161: onsuccess: #578: 6: Success after binutils: 15 commits new c8ade20f359 162: onsuccess: #579: 6: Success after gcc: 11 commits new b5ae3b7d347 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new d7b9666ef54 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] new 62d52094c3b 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] new d5ac20397a6 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] new 8553517f487 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] new 911f61a20bb 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] new d70e198b69d 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] new 06471c63f35 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] new b2d2a06f5b8 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] new fe462225bd7 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] new 0fa2388db25 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] new 5d761d24412 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new 64e10a1b470 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new d9af16779b7 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 5ba2504dfc0 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new ced985be6a0 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] new 1e1153c662c 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 610c3575dd1 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 5b9239e2ca2 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new 825f6e5edd6 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new f74a74e2f94 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 41b6a1d176f 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new 724ee0f9f3b 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new 02a3e283f6a 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new 6987ec50a72 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new d1f6e93529b 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new 3d239e13051 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new 9aa4810633f 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new 5bafb736ff8 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] new af9ca462d44 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new fd72222ee0d 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new 3463dac3074 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new 70311c687ba 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new 48423896f4d 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new 019dd080e66 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] new 7769e0807c9 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new 758b0adb4bb 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new 06aa1a75f6b 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] new fa2a13663b3 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] new ad9fb5974af 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] new b39ed0267f4 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] new 80fcb160591 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new f73ecdfef91 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new d62a3e3962d 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] new dd485ea8546 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 1e9058881d3 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] new 3dcdc7cfc46 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new d446e10c218 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new 76e4626d6da 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 0670a0ab243 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...]

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 (e0f67d0547f) \ 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 1736 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 53124 -> 53084 bytes 05-build_abe-gcc/console.log.xz | Bin 238532 -> 239704 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8384 -> 10180 bytes 08-build_abe-glibc/console.log.xz | Bin 237952 -> 236812 bytes 09-build_abe-gdb/console.log.xz | Bin 50164 -> 51208 bytes 10-check_regression/console.log.xz | Bin 4304 -> 4356 bytes 11-update_baseline/console.log | 60 ++++++++++++++++++----------------- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++----------- 20 files changed, 59 insertions(+), 57 deletions(-)