This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 2569cec8bc 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards 92fdca4930 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 40a3c90acb 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 9f139dcee0 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 26eb4ed769 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 668548977f 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards bf6d8f9ca4 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards dba2d6f1e3 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards a9e4fa6e9a 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 7903dea0d1 152: force: #1605: 7: Success after gcc: 9 commits discards 84f80cb704 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 97b4c4b64d 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 1031d607ed 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards a45ec68590 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards e029137264 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards c600c52c68 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards dcc0796546 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards fcda882e54 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 22676b3481 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 2bf4d4e2a6 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards cebf98c761 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 65c0919e97 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 60d90c5749 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 0206132e59 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 7754cba020 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 3420238807 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 0b0cab4bcb 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 805bae2b6c 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 36eafbf713 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 546ea7e870 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 8f693e6251 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards e01e8f69de 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 4919b7fc4d 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 551a73f31e 128: onsuccess: #1579: 7: Success after linux: 12 commits discards dd6ac2b2a7 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 89bb0ceebf 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 04eff0dfc0 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 08536c162d 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 1a9a721147 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 2f97529abe 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards e4af40a2e0 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 95cca29c8c 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards be0a5a5d30 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards d7e4b73ade 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 45c16e59f5 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 3f16a9f44a 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 88363b7f3e 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 1671c2ab06 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 862e681145 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 63ab325d6c 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 1ed7077eef 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 4d416d1aab 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards e3f33fd4a8 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 0c22ff2537 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards de4e97faba 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards fa37f0df71 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 6edbd49a2b 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards c0eef4895d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 5c360fc30a 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards b3526496bc 102: force: #1551: 1: Failure after gcc: 306 commits discards e4ddde1306 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards fcba73370b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards a4c8ed2184 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards c764e3f4c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 74e3c019a2 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7e468c3447 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5f0ecd9498 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c329db144f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 7ef95d1ddc 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a533e546ab 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 33b090a3ab 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 82bfddca9c 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 5692c179f0 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 36b246a30d 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 7effbd6536 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 9d8dd4d428 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 7c6a08e4e0 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards c09ede404f 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7766f59472 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 31631f8c99 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards e91e6d7cfd 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 446d5f262a 80: onsuccess: 7: Successful build after linux: 44 commits discards 27be917cbc 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards fc7bf22373 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 026c72758a 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f54bab375f 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 17af51ea3b 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e909617504 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 31340586d4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d0b6adccde 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a09f29de0c 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2bfabaab8e 70: onsuccess: 7: Successful build after gcc: 4 commits discards 82b1c3116a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e75bda3c0e 68: onsuccess: 7: Successful build after linux: 6 commits discards cbccbcbea2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards eabd8fc759 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards c3bd17bf35 65: onsuccess: 7: Successful build after binutils: 3 commits discards 53ebfe58c8 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 6f200eca72 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 365308549e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards ff4e9dbb4a 61: onsuccess: 4: Successful build after gcc: 5 commits new 2167b88295 61: onsuccess: 4: Successful build after gcc: 5 commits new 2819d1caff 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 7f969cfb58 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new c34c31dfaa 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 027b310ac0 65: onsuccess: 7: Successful build after binutils: 3 commits new cd34ddc3aa 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 140ed8aac1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new cb33730cfa 68: onsuccess: 7: Successful build after linux: 6 commits new 95a0e7ef2a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 46321c1245 70: onsuccess: 7: Successful build after gcc: 4 commits new 4ac553ad29 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new bd675c5b50 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aa9def9dea 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 00c29dbb2c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 129f67ea97 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 9e668ce861 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new c39054e3a2 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8422891d1f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 3861fbcc3a 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 6c9eb07418 80: onsuccess: 7: Successful build after linux: 44 commits new ffdef53379 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4d3b514afc 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new cd78b52454 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da9210f170 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 39dea4a0ff 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 011c8bf7d5 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 74214679cc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 1a9ae255b1 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new f08b3c8b35 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 147cb7fa1c 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 939c1c065e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 2ff66c1746 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 9cab69657d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new e7d4eeda29 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new b14fb5b49e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d0d89c289a 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 909037423e 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new a033d9a5f7 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new a26a253b08 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new bfb4458317 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new fd6fe55e68 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 49cec6e35e 102: force: #1551: 1: Failure after gcc: 306 commits new 7a25c90872 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 4dc1ec6533 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new c082fe2c0a 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new f289ffe7dc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 6f3f61b2f9 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new ab697edbc1 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 2c26eea556 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 717a15ef98 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 1f75d6912b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new d4d4ef4fa8 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 6d01f75db4 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new b7464dd17d 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new f30f99bc14 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new d0e01bad2f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 05563205e5 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new ddb283f868 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new e48bbf7d53 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new bfcd4427bb 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new eb31235770 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new ca28242a71 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 3ddce552e0 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new d5ad7c6dc8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 014d311eaf 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 28390b5974 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 88d90bd61a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new a84aae6935 128: onsuccess: #1579: 7: Success after linux: 12 commits new e8cb64a19c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 523091a862 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 23eae5a109 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new c65829e150 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 504817e7eb 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 4ac7803a7a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new a4be7379b9 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 62149628e8 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new d6885e41aa 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 307c999730 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 2d23bb7f7f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 1faf284f73 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new f5dd0d34cc 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 912b2a5fcf 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 67e18d8499 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new d92bb00246 144: onsuccess: #1595: 7: Success after glibc: 2 commits new dbae15c79b 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 79fe527a0c 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 4d5d673e75 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new db846c16df 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new dfef8bc399 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 46d8504251 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 1bfa62319e 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 796907be0a 152: force: #1605: 7: Success after gcc: 9 commits new ce05f00387 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 36d3360568 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 1a200cddf0 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 151b91f446 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 3cb7bd48df 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new c49bc70d58 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new dc7c2fb25a 159: onsuccess: #1612: 7: Success after gcc: 4 commits new f4dcf81c1e 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 30552904e7 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 7a5cba4bfe 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits
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 (2569cec8bc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1676 -> 1636 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30292 -> 30456 bytes 05-build_abe-stage1/console.log.xz | Bin 71840 -> 72592 bytes 07-build_abe-linux/console.log.xz | Bin 8272 -> 8268 bytes 08-build_abe-glibc/console.log.xz | Bin 239964 -> 239256 bytes 09-build_abe-stage2/console.log.xz | Bin 202344 -> 202872 bytes 10-build_abe-gdb/console.log.xz | Bin 37528 -> 37540 bytes 11-build_abe-qemu/console.log.xz | Bin 31836 -> 32244 bytes 12-check_regression/console.log.xz | Bin 3552 -> 3548 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- 19 files changed, 56 insertions(+), 56 deletions(-)