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 e2e2fcfd96a0 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...] discards 120b3c525a96 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] discards 7e88f768e055 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] discards 5c72f237e7a6 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] discards d24ca39d1531 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] discards 080d1e57f0a0 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] discards c9aba1550b67 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] discards cdb37f801c1b 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] discards e28e4242871c 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] discards f3bd9ca0f09d 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] discards 3449a9d133a1 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] discards ca28d8036837 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] discards 08d7dea27450 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] discards 14007b01cc48 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 63e14631f22f 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] discards 2d033a5e5cf0 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] discards 606e3ead8837 131: onsuccess: #540: 6: Success after binutils/gcc/linux/ [...] discards fab9f03a138d 130: onsuccess: #539: 6: Success after binutils/gcc/linux/ [...] discards 4f6713d457fa 129: onsuccess: #538: 6: Success after binutils/gcc/linux/ [...] discards c181e40bea89 128: onsuccess: #537: 6: Success after binutils/gcc/linux/ [...] discards 23e7211849bf 127: onsuccess: #536: 6: Success after binutils/gcc/linux/ [...] discards df9f036b32d6 126: onsuccess: #535: 6: Success after binutils/gcc/linux/ [...] discards 8e593a6c5de5 125: onsuccess: #534: 6: Success after binutils/gcc/linux/ [...] discards 71c0345972ab 124: onsuccess: #533: 6: Success after binutils/gcc/linux/ [...] discards a4e9aa0b18a3 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 6 [...] discards ec90b9120b67 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 5 [...] discards b9feeb23f3e1 121: onsuccess: #530: 6: Success after binutils/gcc/linux/ [...] discards 45a566e990fe 120: onsuccess: #529: 6: Success after binutils/gcc/linux/ [...] discards ad62f990e061 119: onsuccess: #528: 6: Success after binutils/gcc/linux/ [...] discards ca8920b96186 118: onsuccess: #527: 6: Success after binutils/gcc/linux/ [...] discards ea6c1c9f412c 117: onsuccess: #526: 6: Success after binutils/gcc/linux/ [...] discards 3b2d9270a276 116: onsuccess: #525: 6: Success after binutils/gcc/linux/ [...] discards 4cd35a2246fe 115: onsuccess: #524: 6: Success after binutils/gcc/linux/ [...] discards c72a2f228489 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 1926c832bb79 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 152c3e2a2bad 112: force: #521: 1: Failure after basepoints/gcc-13-3918- [...] discards dedb9d497d5f 111: force: #520: 6: Success after gcc: 9 commits discards 2c727b0750c3 110: onsuccess: #518: 6: Success after binutils: 5 commits discards b846077a29ea 109: onsuccess: #516: 6: Success after binutils/gcc/linux/ [...] discards 284a66d4251b 108: onsuccess: #514: 6: Success after binutils/gcc/linux/ [...] discards 10573204c289 107: onsuccess: #513: 6: Success after binutils/gcc/linux/ [...] discards ddb98da8c69a 106: onsuccess: #512: 6: Success after binutils/gcc/linux/ [...] discards 5a53c196ed26 105: onsuccess: #511: 6: Success after binutils/gcc/linux/ [...] discards d2a41764d7a9 104: onsuccess: #510: 6: Success after binutils/gcc/linux/ [...] discards 9b59e8926a04 103: onsuccess: #509: 6: Success after binutils/gcc/linux/ [...] discards 4782eff0dd15 102: onsuccess: #508: 6: Success after binutils/gcc/linux/ [...] discards 29691072c8c0 101: onsuccess: #507: 4: Success after binutils/gcc/linux/ [...] discards 6e3745a18b31 100: onsuccess: #506: 4: Success after baseline build: no [...] discards a6025b09e7ab 99: force: #505: 4: Failure after basepoints/gcc-13-3596-g [...] discards 883abf2a3f02 98: force: #504: 6: Success after gcc: 18 commits discards 970274ddf4ac 97: onsuccess: #503: 6: Success after linux: 11 commits discards 4fd55816dc51 96: onsuccess: #502: 6: Success after glibc: 10 commits discards a3b79be133c4 95: onsuccess: #500: 6: Success after binutils: 8 commits discards e047fa619927 94: onsuccess: #498: 6: Success after binutils/gcc/linux/g [...] discards 8cbe14d352e2 93: onsuccess: #497: 6: Success after binutils/gcc/linux/g [...] discards e6ebd105a1ef 92: onsuccess: #496: 6: Success after binutils/gcc/linux/g [...] discards 2e6a99c952a6 91: onsuccess: #495: 6: Success after binutils/gcc/linux/g [...] discards aeff345310c1 90: onsuccess: #494: 6: Success after binutils/gcc/linux/g [...] discards cb9e2beeb10e 89: onsuccess: #492: 6: Success after binutils/gcc/linux/g [...] discards 879017bd283e 88: onsuccess: #491: 6: Success after binutils/gcc/linux/g [...] discards ae448f119376 87: onsuccess: #490: 6: Success after binutils/gcc/linux/g [...] discards a9871fb0cade 86: onsuccess: #489: 6: Success after binutils/gcc/linux/g [...] discards dfe13cb9ea64 85: onsuccess: #488: 6: Success after binutils/gcc/linux/g [...] discards 8630d33b4cb8 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/g [...] discards d95cd834d806 83: onsuccess: #486: 6: Success after binutils/gcc/linux/g [...] discards 7012d9fbe1f1 82: onsuccess: #485: 6: Success after binutils/gcc/linux/g [...] discards 5e5435c5cf29 81: onsuccess: #484: 6: Success after binutils/gcc/linux/g [...] discards a103959186c1 80: onsuccess: #483: 6: Success after binutils/gcc/linux/g [...] discards fae214b709ed 79: onsuccess: #482: 6: Success after binutils/gcc/linux/g [...] discards 07aff758daaa 78: onsuccess: #481: 6: Success after binutils/gcc/linux/g [...] discards 93920dd719bf 77: onsuccess: #480: 6: Success after binutils/gcc/linux/g [...] discards 85789c0710b6 76: onsuccess: #479: 6: Success after binutils/gcc/linux/g [...] discards d290d15b4821 75: onsuccess: #478: 6: Success after binutils/gcc/linux/g [...] discards fd50079c22da 74: onsuccess: #477: 6: Success after binutils/gcc/linux/g [...] discards 807834c28113 73: onsuccess: #476: 6: Success after binutils/gcc/linux/g [...] discards 4d4768d8246d 72: onsuccess: #475: 6: Success after binutils/gcc/linux/g [...] discards 7fe30ab8dcf2 71: onsuccess: #474: 6: Success after binutils/gcc/linux/g [...] discards d31b854d9e67 70: onsuccess: #473: 6: Success after binutils/gcc/linux/g [...] discards 5b8c50c9ff0e 69: onsuccess: #472: 6: Success after binutils/gcc/linux/g [...] discards ff5659e79952 68: onsuccess: #471: 6: Success after binutils/gcc/linux/g [...] discards f4b519662ac9 67: onsuccess: #470: 6: Success after binutils/gcc/linux/g [...] discards c2e8c7cb2581 66: onsuccess: #469: 6: Success after binutils/gcc/linux/g [...] discards 70030b49feb5 65: onsuccess: #468: 6: Success after binutils/gcc/linux/g [...] discards 641625edfcce 64: onsuccess: #467: 6: Success after binutils/gcc/linux/g [...] discards 08e684a56ea4 63: onsuccess: #466: 6: Success after binutils/gcc/linux/g [...] discards 9c51bae5492e 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards b12467a9c5d0 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 83fb17a90d1e 60: onsuccess: #463: 1: Success after gcc: 10 commits discards 69f83cb43c7c 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g [...] discards 6ce9480eb8e1 58: force: #461: 6: Success after gcc: 29 commits discards 744581f4190d 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 195aed212859 56: onsuccess: #457: 6: Success after binutils/gcc/linux/g [...] discards 7c2bcb049ea2 55: onsuccess: #456: 6: Success after binutils/gcc/linux/g [...] discards 49e8198d2e8a 54: onsuccess: #455: 6: Success after binutils/gcc/linux/g [...] discards fcbc3f1c26e8 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/g [...] discards 585e78b56006 52: onsuccess: #453: 6: Success after binutils/gcc/linux/g [...] discards 034a830a41b1 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/g [...] discards 512c1c89d3d1 50: onsuccess: #451: 6: Success after binutils/gcc/linux/g [...] discards 6990b7fea21a 49: onsuccess: #450: 6: Success after binutils/gcc/linux/g [...] discards e01fe4432ba4 48: onsuccess: #449: 6: Success after binutils/gcc/linux/g [...] discards b3bde94377e2 47: onsuccess: #448: 4: Success after binutils/gcc/linux/g [...] new f4e45a0af26f 47: onsuccess: #448: 4: Success after binutils/gcc/linux/g [...] new e992f0da745c 48: onsuccess: #449: 6: Success after binutils/gcc/linux/g [...] new 692a7d71c7a1 49: onsuccess: #450: 6: Success after binutils/gcc/linux/g [...] new 9a6f8890c798 50: onsuccess: #451: 6: Success after binutils/gcc/linux/g [...] new a83e1243dfd8 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/g [...] new 37e48688be2f 52: onsuccess: #453: 6: Success after binutils/gcc/linux/g [...] new 35887271d079 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/g [...] new 1bc099b5b98c 54: onsuccess: #455: 6: Success after binutils/gcc/linux/g [...] new 0b60c027e256 55: onsuccess: #456: 6: Success after binutils/gcc/linux/g [...] new 08d1582f3aa5 56: onsuccess: #457: 6: Success after binutils/gcc/linux/g [...] new 0bcd2a25187b 57: onsuccess: #459: 6: Success after binutils: 8 commits new b2b185852cd3 58: force: #461: 6: Success after gcc: 29 commits new d1d6977426a8 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g [...] new 756665f37179 60: onsuccess: #463: 1: Success after gcc: 10 commits new 00a4534e5904 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new cabb5e530828 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 3edd5d3ee4f8 63: onsuccess: #466: 6: Success after binutils/gcc/linux/g [...] new cfbee2f96fd7 64: onsuccess: #467: 6: Success after binutils/gcc/linux/g [...] new e842436eb791 65: onsuccess: #468: 6: Success after binutils/gcc/linux/g [...] new 5ca6db1616b7 66: onsuccess: #469: 6: Success after binutils/gcc/linux/g [...] new 385d5d32d076 67: onsuccess: #470: 6: Success after binutils/gcc/linux/g [...] new 7f4a38c723f9 68: onsuccess: #471: 6: Success after binutils/gcc/linux/g [...] new c88cb2bc7485 69: onsuccess: #472: 6: Success after binutils/gcc/linux/g [...] new 411fc17b54b5 70: onsuccess: #473: 6: Success after binutils/gcc/linux/g [...] new 0ffd9486da34 71: onsuccess: #474: 6: Success after binutils/gcc/linux/g [...] new 708d9139e5ac 72: onsuccess: #475: 6: Success after binutils/gcc/linux/g [...] new e437f736b720 73: onsuccess: #476: 6: Success after binutils/gcc/linux/g [...] new 047a30a9e7e9 74: onsuccess: #477: 6: Success after binutils/gcc/linux/g [...] new 0a7c26ee73bf 75: onsuccess: #478: 6: Success after binutils/gcc/linux/g [...] new ae16874ffad4 76: onsuccess: #479: 6: Success after binutils/gcc/linux/g [...] new ef0ab7223646 77: onsuccess: #480: 6: Success after binutils/gcc/linux/g [...] new dc3198712030 78: onsuccess: #481: 6: Success after binutils/gcc/linux/g [...] new acd54e57b7f1 79: onsuccess: #482: 6: Success after binutils/gcc/linux/g [...] new 36b79f5eb9c4 80: onsuccess: #483: 6: Success after binutils/gcc/linux/g [...] new 90ba198d5b4e 81: onsuccess: #484: 6: Success after binutils/gcc/linux/g [...] new 287c71c87098 82: onsuccess: #485: 6: Success after binutils/gcc/linux/g [...] new 1cc9cc98a048 83: onsuccess: #486: 6: Success after binutils/gcc/linux/g [...] new 556a40c6a179 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/g [...] new 4468296f0254 85: onsuccess: #488: 6: Success after binutils/gcc/linux/g [...] new 73eccf2cad03 86: onsuccess: #489: 6: Success after binutils/gcc/linux/g [...] new 37076660f999 87: onsuccess: #490: 6: Success after binutils/gcc/linux/g [...] new 56412716bb47 88: onsuccess: #491: 6: Success after binutils/gcc/linux/g [...] new 3932a5072737 89: onsuccess: #492: 6: Success after binutils/gcc/linux/g [...] new 178e7678c25d 90: onsuccess: #494: 6: Success after binutils/gcc/linux/g [...] new 34fd3e6e313d 91: onsuccess: #495: 6: Success after binutils/gcc/linux/g [...] new 012741f19698 92: onsuccess: #496: 6: Success after binutils/gcc/linux/g [...] new ab55df33d39c 93: onsuccess: #497: 6: Success after binutils/gcc/linux/g [...] new d866cc8b04c5 94: onsuccess: #498: 6: Success after binutils/gcc/linux/g [...] new 5f4f29e23178 95: onsuccess: #500: 6: Success after binutils: 8 commits new e28e7c3c636a 96: onsuccess: #502: 6: Success after glibc: 10 commits new 531d51cc2e04 97: onsuccess: #503: 6: Success after linux: 11 commits new 0c052c70b03c 98: force: #504: 6: Success after gcc: 18 commits new 94e7a36848e9 99: force: #505: 4: Failure after basepoints/gcc-13-3596-g [...] new d19d22c975b6 100: onsuccess: #506: 4: Success after baseline build: no [...] new 9451ac548ba8 101: onsuccess: #507: 4: Success after binutils/gcc/linux/ [...] new a022046cbe98 102: onsuccess: #508: 6: Success after binutils/gcc/linux/ [...] new f4dc47c998d9 103: onsuccess: #509: 6: Success after binutils/gcc/linux/ [...] new 2b0e68a217da 104: onsuccess: #510: 6: Success after binutils/gcc/linux/ [...] new fce6449b145d 105: onsuccess: #511: 6: Success after binutils/gcc/linux/ [...] new ba468295b023 106: onsuccess: #512: 6: Success after binutils/gcc/linux/ [...] new 89341a6c85fd 107: onsuccess: #513: 6: Success after binutils/gcc/linux/ [...] new 6b0f64757572 108: onsuccess: #514: 6: Success after binutils/gcc/linux/ [...] new 6524a13b9237 109: onsuccess: #516: 6: Success after binutils/gcc/linux/ [...] new 7c134eceb480 110: onsuccess: #518: 6: Success after binutils: 5 commits new 0ef6811bca5b 111: force: #520: 6: Success after gcc: 9 commits new 24009b0b3d45 112: force: #521: 1: Failure after basepoints/gcc-13-3918- [...] new 35691d3d5bad 113: onsuccess: #522: 1: Success after gcc: 12 commits new 0e85f1d82180 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 49a6891b80e7 115: onsuccess: #524: 6: Success after binutils/gcc/linux/ [...] new c2dc03123765 116: onsuccess: #525: 6: Success after binutils/gcc/linux/ [...] new 8492b0cf5578 117: onsuccess: #526: 6: Success after binutils/gcc/linux/ [...] new 8e0082838eb7 118: onsuccess: #527: 6: Success after binutils/gcc/linux/ [...] new 186efe541a4a 119: onsuccess: #528: 6: Success after binutils/gcc/linux/ [...] new bb4e90606fcd 120: onsuccess: #529: 6: Success after binutils/gcc/linux/ [...] new a83eb1d4d8d4 121: onsuccess: #530: 6: Success after binutils/gcc/linux/ [...] new be3057462c8f 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 5 [...] new 5f9cfd8a3f9a 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 6 [...] new f1ff6e682e05 124: onsuccess: #533: 6: Success after binutils/gcc/linux/ [...] new 3970e3b9ecc9 125: onsuccess: #534: 6: Success after binutils/gcc/linux/ [...] new d5287946bf9d 126: onsuccess: #535: 6: Success after binutils/gcc/linux/ [...] new 2d41be2fe1f3 127: onsuccess: #536: 6: Success after binutils/gcc/linux/ [...] new 99f10685aefb 128: onsuccess: #537: 6: Success after binutils/gcc/linux/ [...] new 493bd0a94233 129: onsuccess: #538: 6: Success after binutils/gcc/linux/ [...] new 7b93ed7d4fe0 130: onsuccess: #539: 6: Success after binutils/gcc/linux/ [...] new d0f2d6c1003c 131: onsuccess: #540: 6: Success after binutils/gcc/linux/ [...] new 8a60f49aaed8 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] new 2e19c5ed3dec 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] new 7ba0089de9a7 134: onsuccess: #544: 6: Success after binutils: 18 commits new 2e4d284e23c2 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] new 024dbf48813a 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] new 3eab4e26881d 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] new 426465c12e14 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] new 99dec225a0ac 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] new b5278dab7645 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] new b1331d646061 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] new 68c6c389f3d1 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] new 6df066ce94cf 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] new 0e5472b358f7 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] new 36ba84f8d3db 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] new 47e7ad8e2aa1 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] new 828f6c85e0ee 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...] new 430ecdc05d00 148: onsuccess: #564: 6: Success after binutils/gcc/linux/ [...]
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 (e2e2fcfd96a0) \ 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 1732 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 53556 -> 54504 bytes 05-build_abe-gcc/console.log.xz | Bin 235212 -> 235668 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 9076 -> 8516 bytes 08-build_abe-glibc/console.log.xz | Bin 236736 -> 236152 bytes 09-build_abe-gdb/console.log.xz | Bin 52196 -> 52096 bytes 10-check_regression/console.log.xz | Bin 4456 -> 4480 bytes 11-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 | 36 ++++++++++---------- 20 files changed, 59 insertions(+), 59 deletions(-)