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_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards b74d39392 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/gl [...] discards 82895fac5 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 commits discards 27ef7952c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 87011e139 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/gd [...] discards ab5e303ca 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/gd [...] discards 124d728b8 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 4c297dba4 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/gd [...] discards 5b721136b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards a239c2a75 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 242c1b21a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 612c7de96 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-20 [...] discards 14ebd4dea 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/gl [...] discards b93cfc7a2 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 commits discards e493704e4 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/gd [...] discards d6dd8a4f1 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/gd [...] discards e5ad7a917 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/gd [...] discards 740364c92 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 commits discards 0ce2d2272 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards e59420cfe 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/gl [...] discards b98141647 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/gd [...] discards a51a71179 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6650631b8 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards c38fc7a11 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/gl [...] discards 38ab38b6a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...] discards c1d671b4d 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 4b9c64e43 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] discards a05ba5fea 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards be6d05cc2 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards bae3f1ce4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits discards ebd3206a5 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits discards 79b683ff6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] discards 395690f20 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 9260f645f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] discards 01d34e72d 128: onsuccess: #1723: 1: Success after linux: 12 commits discards c79e2cf4b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 84b082ba0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 451bba2ee 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 53ad23e56 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 2059f1cea 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 011079a9b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards 0c715d9d9 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 60f94800d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards aaa719dbc 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards c1588f9fe 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 44aed818e 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 4687c5e83 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards a523e7c38 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 7409c6387 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 9046782d5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 4a99a5b9f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 53f68b475 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards c043aaf87 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 23fb3f119 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards c318e95af 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 61b51e626 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 987407ff2 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards e0316cbff 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 776f90f8e 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards fd37af66b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 99b7f4773 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards b7f6298f4 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 33d6e9da2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 7f4e24d03 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards eae63ebe7 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 437fbd4bd 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 3f9a9c82d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c06cf3f0f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 09d171965 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 30a364596 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 66585fda8 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 89b28dc0b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 1b84f1b6d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d8a7d91e8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 781775bb0 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d00ca8749 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 020510213 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d2d3b61c3 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f7f3babd3 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards e13b0bc9d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 3f3bd064a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3d3243099 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards e7946da9e 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards af4d0eb2b 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards cac6a60ae 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d9a118a6d 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 93e80a4ab 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards ab25b8b20 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 808ac298b 74: onsuccess: 1: Successful build after linux: 44 commits discards 89cdf6873 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e0a932e7f 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1214b9d36 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3ca985185 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 87e8698cb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 303f7166a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d0a797552 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 42d5634fe 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6afa6e50c 65: onsuccess: 1: Successful build after gcc: 4 commits discards 31e00f93a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 11272b5b9 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b8e2af196 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards e0eca1309 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 80c7ae608 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a57a3312f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 020b1609d 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7309b681a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0aa8496de 65: onsuccess: 1: Successful build after gcc: 4 commits new 3ee619260 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3932d7964 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d843aeda5 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 07720536b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 025c06a9b 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new ca130957d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new bdf0798d6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c71f78692 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5f9d22e3e 74: onsuccess: 1: Successful build after linux: 44 commits new 7667a238f 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a5baac5fb 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 5926ea552 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f7ece26da 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a0e9b4c0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new a25f985d2 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 9321d8493 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0ee0d7292 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ae00fa420 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new f6792a08a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 4d60bc3f9 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 4ea909002 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 86cbd6a9a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e1eef48c9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 336401f9a 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 72551749f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 992ce7e3e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new fe60781a4 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 562c5b8fc 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 87761395f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 173090420 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new c2562eddf 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b3ae8a9b2 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new df6a0a652 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 48b3d93ff 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 8e3f8f8ac 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new ab2ad20e7 101: onsuccess: #1693: 1: Success after glibc: 14 commits new bc99d97d1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new c02670224 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 031e6eb0c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 51b172553 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 91381dadb 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new c9e8c38af 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 9f2b051e3 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6041ae469 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 1f3d43f67 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 0fbd499e3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 372da95bc 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new d2f351270 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new d07bf19e3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 6fb1ac766 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 13a95c827 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 9b9d032c4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new 91c0e514c 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 2d454f75c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new bdf41074d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new c195caf4f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new 7212fed5a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new 65925a19e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new de1749134 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 1c69d0d51 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 60bb9db1f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new bdfce0e94 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 60b2c2afc 128: onsuccess: #1723: 1: Success after linux: 12 commits new d36f149b2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] new 2fcdfe63f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new bcbac98e9 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] new c48e2bf52 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits new 4fabfd359 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits new c2dd1cff4 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 810206989 135: onsuccess: #1733: 1: Success after binutils: 5 commits new f686d503b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] new 3d847f5e4 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 4e9200cf7 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...] new 8f68d325b 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/gl [...] new cc3dc1ef7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b4507beb6 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 13a94d557 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/gd [...] new a2ebcec63 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/gl [...] new f1995ad5d 144: onsuccess: #1743: 1: Success after glibc: 2 commits new a892add55 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 commits new fa0253125 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/gd [...] new 858c0fd28 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/gd [...] new f1bb16938 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/gd [...] new dd9b57b70 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 commits new d9d5dc595 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/gl [...] new b36030f1c 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-20 [...] new 7890eac7a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 9dead4f25 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 6fc190c61 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new d46784894 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/gd [...] new e7535d5f6 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 992dca57e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/gd [...] new 02f6d1a1d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/gd [...] new 4d7b8ccbe 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 1ed832791 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 commits new d0240683a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/gl [...] new 448523c6b 162: onsuccess: #1763: 1: 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 (b74d39392) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30700 -> 30104 bytes 04-build_abe-stage1/console.log.xz | Bin 91184 -> 90592 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9188 -> 9956 bytes 07-build_abe-glibc/console.log.xz | Bin 235876 -> 234052 bytes 08-build_abe-stage2/console.log.xz | Bin 225680 -> 223476 bytes 09-build_abe-gdb/console.log.xz | Bin 37648 -> 37136 bytes 10-build_abe-qemu/console.log.xz | Bin 31604 -> 31632 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2704 -> 2420 bytes 13-check_regression/console.log.xz | Bin 8316 -> 6876 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 275 +--- 14-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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- sumfiles/g++.log.xz | Bin 2652712 -> 2669836 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2228744 -> 2193148 bytes sumfiles/gcc.sum | 2572 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 886832 -> 880740 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201464 -> 201484 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424796 -> 428120 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 1477 insertions(+), 1786 deletions(-)