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 d4ed76a481 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards b19a8407af 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 93f6ac200f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 4aafb94753 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards f79c13cb5f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 5727e2b134 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards ded68b1816 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards f32b7bade0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards b304b06d55 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards ba9768e7b3 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 02276f5366 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 0691db29d5 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 208db90fe7 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards e7d5175ad7 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards fb67a5c4c9 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards cb7eb47a87 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 688d27a904 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards ab2859e67c 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 9ced80fb44 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 847d9ef930 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 93c49adcc4 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 7e37c67f49 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards c90e197fe8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards a713b3b013 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 794e1fc435 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 3ad8de7fce 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 0d13f2f602 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 741748cf55 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards cf5e80b8cb 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 1cb33122a1 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 613404b329 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards a027479d16 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards d138936f90 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards e23a923714 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 16cd6fd090 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards c70648bd24 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 93a12ed089 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 6d1c2811e3 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 56fec30a91 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 00e9df0b24 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 7091149e0c 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards ffe5651393 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 46686e4541 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards d5f3f207d9 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards a5ad978b94 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 885c50f1c8 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b9e9319881 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 411e92ec70 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards a179289b32 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards cf77f39e79 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 57a5dcbdf2 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 0be7c1799d 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 8a261fe6dd 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 22af60c451 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards a472126e2b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 67bca389b7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 699aaa0a91 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 0bfb13c497 128: onsuccess: #1723: 1: Success after linux: 12 commits discards fbcbfab9ff 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 165644e062 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 14ff950b96 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards a89d79a41e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 1efdca47f1 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 26bbc4744d 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 0514b672bc 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 56fdbf39fd 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 076606c4cd 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 45e30be725 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 34651097c2 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards e000e6d38f 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 706f307e62 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 850aaa535f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 96ff8e7e3c 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards bf47709be7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards c429f6fee9 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 819affbf42 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards a7ca8ebc36 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards bc91c52f07 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6f0d6dc58d 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards b83cc71559 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 06854fde79 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards ffeec20801 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 9bfdef22db 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 4ef5cc1f99 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 85005e16e7 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 553de08973 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards da8cc93880 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 05b20f296f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 805294dcee 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 546998c95e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 73684ae443 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 27546774d2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 7bae0147d3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 40e18e46dd 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 2c924cf532 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 1884ca281f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ea595cb384 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9d7022b306 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d42552b408 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b40dda09e4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9a95d734a4 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 31e75708c6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b2a3b10572 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 1b696f76d1 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f791c94ed0 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new c0dc52e236 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0f7868e2ff 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 103707a1f3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 80d7564126 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 19ef7e587e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new b13436c0a3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new b9b9da8328 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new f29fa64d52 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 40ed485da7 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new da324a753d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 34c4573000 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new f7a1edcddc 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 4bf64cd189 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 95e6ff4f4b 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 6c27421d17 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new c5ee389a35 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 889b296241 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new fbde990aaa 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 3f3f71082f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 2748b00deb 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new dc1899ee7f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 01ba00329d 110: onsuccess: #1703: 1: Success after gcc: 6 commits new e2e0b0a7d8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 21df94c4f1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new a3ca87e5b9 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 312d345a29 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 3ad3300f5e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new faaa928a7e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 23a3587101 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new db7ea6d868 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 583106c754 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 46da7dce3e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a643cc97d3 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 99d498cf38 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new d54f8cb763 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 286c72034c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ccd068da41 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new f2ece2683a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 95fe51c09a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 04d431b1a0 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6693f9e0b6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 8138c15f01 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new f1e3436a62 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 7a193b91d6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 8daf7c1b01 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new b95e6a9d67 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 80ce78bfd5 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e2e97f1264 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new ebe14038e4 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 73fa78b878 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 83b2e8ef6e 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 245424f950 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 4adbd37fc9 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new c2a4ff1380 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 875b5345d9 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new b323ed6d09 144: onsuccess: #1743: 1: Success after glibc: 2 commits new e13f739edd 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 594f5054f3 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 8bc875d64c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new cd55045002 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 184a1bf3d3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 85712e9660 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 039df30ba3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 4e907a8098 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new ce09d5c888 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 8625241494 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new fbecfc4027 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 34454eecd7 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 050eac35ab 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 9731031140 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 8320575c27 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 5502a3687f 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 5322a1e25d 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 43c40a54f1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 0667d10d5a 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 9abeef02d6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 13f5663148 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 7f43621126 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 6305f84854 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new ed93148c95 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 2bda414c3b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 695ab731ae 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 5af76b02b4 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 46c826b411 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 88bca61b2f 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new d2af138953 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 3d7848664d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 9daf17ae73 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 9adecd34a8 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 78723b7fe3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 1a1955dbd8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 64dfdc85aa 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new b6c38e7be7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new e533ff2de5 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 65ed999f12 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 22ab9aed14 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 087f998172 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 5f4429155c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...]
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 (d4ed76a481) \ 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 1736 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30424 -> 30132 bytes 04-build_abe-stage1/console.log.xz | Bin 90064 -> 90840 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8860 -> 8888 bytes 07-build_abe-glibc/console.log.xz | Bin 235680 -> 235988 bytes 08-build_abe-stage2/console.log.xz | Bin 223152 -> 223472 bytes 09-build_abe-gdb/console.log.xz | Bin 37560 -> 37540 bytes 10-build_abe-qemu/console.log.xz | Bin 30996 -> 31228 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2516 -> 3052 bytes 13-check_regression/console.log.xz | Bin 8324 -> 5628 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 171 +-- 14-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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2711796 -> 2712664 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 2216292 -> 2224116 bytes sumfiles/gcc.sum | 2513 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890780 -> 892076 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212884 -> 212968 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427608 -> 438384 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 1445 insertions(+), 1647 deletions(-)