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 7a5cba4bfe 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 30552904e7 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards f4dcf81c1e 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards dc7c2fb25a 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards c49bc70d58 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 3cb7bd48df 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 151b91f446 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 1a200cddf0 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 36d3360568 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards ce05f00387 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 796907be0a 152: force: #1605: 7: Success after gcc: 9 commits discards 1bfa62319e 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 46d8504251 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards dfef8bc399 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards db846c16df 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 4d5d673e75 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 79fe527a0c 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards dbae15c79b 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards d92bb00246 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 67e18d8499 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 912b2a5fcf 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards f5dd0d34cc 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 1faf284f73 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 2d23bb7f7f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 307c999730 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards d6885e41aa 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 62149628e8 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards a4be7379b9 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 4ac7803a7a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 504817e7eb 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards c65829e150 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 23eae5a109 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 523091a862 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards e8cb64a19c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards a84aae6935 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 88d90bd61a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 28390b5974 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 014d311eaf 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards d5ad7c6dc8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 3ddce552e0 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards ca28242a71 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards eb31235770 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards bfcd4427bb 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards e48bbf7d53 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards ddb283f868 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 05563205e5 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards d0e01bad2f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards f30f99bc14 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards b7464dd17d 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 6d01f75db4 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards d4d4ef4fa8 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 1f75d6912b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 717a15ef98 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 2c26eea556 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards ab697edbc1 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 6f3f61b2f9 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards f289ffe7dc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards c082fe2c0a 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 4dc1ec6533 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 7a25c90872 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 49cec6e35e 102: force: #1551: 1: Failure after gcc: 306 commits discards fd6fe55e68 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards bfb4458317 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards a26a253b08 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards a033d9a5f7 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 909037423e 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards d0d89c289a 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b14fb5b49e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e7d4eeda29 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 9cab69657d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 2ff66c1746 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 939c1c065e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 147cb7fa1c 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards f08b3c8b35 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 1a9ae255b1 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 74214679cc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 011c8bf7d5 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 39dea4a0ff 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards da9210f170 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cd78b52454 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4d3b514afc 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards ffdef53379 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6c9eb07418 80: onsuccess: 7: Successful build after linux: 44 commits discards 3861fbcc3a 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 8422891d1f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards c39054e3a2 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9e668ce861 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 129f67ea97 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 00c29dbb2c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards aa9def9dea 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bd675c5b50 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4ac553ad29 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 46321c1245 70: onsuccess: 7: Successful build after gcc: 4 commits discards 95a0e7ef2a 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cb33730cfa 68: onsuccess: 7: Successful build after linux: 6 commits discards 140ed8aac1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards cd34ddc3aa 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 027b310ac0 65: onsuccess: 7: Successful build after binutils: 3 commits discards c34c31dfaa 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 7f969cfb58 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 2819d1caff 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 26d8ab4327 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 8de2d2fcf0 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new ff3286c92d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new cc21ec7dfd 65: onsuccess: 7: Successful build after binutils: 3 commits new 6f31e01a62 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new ef5dd2a8b0 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new c5a788b7cb 68: onsuccess: 7: Successful build after linux: 6 commits new 55c18bc1f5 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f1f8ec0229 70: onsuccess: 7: Successful build after gcc: 4 commits new ea58f53728 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 435f44b1d2 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 28be1bf27e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6936470f2e 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new da0a224431 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 645a66fe19 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 7efa4ca533 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e0b19d18c3 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 1e3b91aef3 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 55399abdbc 80: onsuccess: 7: Successful build after linux: 44 commits new af5406996c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b323a4930d 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 4f86288c7c 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 99e7448783 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5b1ab7e3b2 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new b00eb087c1 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 81e5c1627e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new a2991283d1 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 9b90f16d02 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 8f446e58aa 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new a0e21e0c17 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 0bb4f58a21 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 5db119b491 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 457938a40b 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new a98d2bbbd9 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 8c63e34467 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 575a259571 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 134835d496 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 8c6116f42b 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 3d0bfaf6e0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 6d831837c6 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 69faf16028 102: force: #1551: 1: Failure after gcc: 306 commits new 98ecac32f7 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 4f5f539b79 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 3314d0039c 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new e85a3cf1f6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 6211562127 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new f9d8bcbbc3 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 735c7f40c4 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new a66f3afbed 110: onsuccess: #1559: 7: Success after gcc: 4 commits new a54cc830af 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 06b8420b02 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 4961e14658 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new f92288b11a 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new d48b4d9ffb 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 84dce6f6ed 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 76c77653f4 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 57de9eeb64 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 320b723515 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new edc41d2aab 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new de5d01af9e 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 2dc53f17cc 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 39a6a6c08b 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new bb688f3fed 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new c16d0a25b0 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new ae2862953b 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 92d403ad07 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 9b17332793 128: onsuccess: #1579: 7: Success after linux: 12 commits new eac7ff7584 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 55eef66848 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new d15f019b77 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 79166b2278 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new b63601fac8 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 52dc1fe5d7 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 7b3fbd6344 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new de13bc1415 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new e061517633 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 7fe22a0fca 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 388bd18d86 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 029167d634 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 848f45ba27 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 5d1b5d8535 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 47a6a74786 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new b148cc9edb 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 7023d438c9 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new f07605cfdb 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new e9f3903264 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new a802bb3a52 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new a6d8d3ce8c 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 85f4cae681 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new b8fa12a27c 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 3b41fe0de6 152: force: #1605: 7: Success after gcc: 9 commits new 3d3f2c10ba 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new a9433dd5b4 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 0761c0a38b 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 5b142c9672 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 4d5bb10522 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new b2b6b1f18b 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 9dd423570a 159: onsuccess: #1612: 7: Success after gcc: 4 commits new f3a9234546 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 1bde4fd8f7 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new f0c282b111 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new 04d287b658 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...]
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 (7a5cba4bfe) \ 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 1636 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 30456 -> 30396 bytes 05-build_abe-stage1/console.log.xz | Bin 72592 -> 72348 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8268 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 239256 -> 239988 bytes 09-build_abe-stage2/console.log.xz | Bin 202872 -> 203504 bytes 10-build_abe-gdb/console.log.xz | Bin 37540 -> 37476 bytes 11-build_abe-qemu/console.log.xz | Bin 32244 -> 31736 bytes 12-check_regression/console.log.xz | Bin 3548 -> 3736 bytes 13-update_baseline/console.log | 48 +++++++++++++++++------------------ 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 ++++++++++++------------- 20 files changed, 48 insertions(+), 48 deletions(-)