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 5f4429155c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 087f998172 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 22ab9aed14 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 65ed999f12 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards e533ff2de5 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards b6c38e7be7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 64dfdc85aa 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 1a1955dbd8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 78723b7fe3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 9adecd34a8 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 9daf17ae73 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 3d7848664d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards d2af138953 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 88bca61b2f 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 46c826b411 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 5af76b02b4 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 695ab731ae 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 2bda414c3b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards ed93148c95 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 6305f84854 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 7f43621126 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 13f5663148 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 9abeef02d6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 0667d10d5a 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 43c40a54f1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 5322a1e25d 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 5502a3687f 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 8320575c27 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 9731031140 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 050eac35ab 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 34454eecd7 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards fbecfc4027 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 8625241494 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards ce09d5c888 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 4e907a8098 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 039df30ba3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 85712e9660 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 184a1bf3d3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards cd55045002 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 8bc875d64c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 594f5054f3 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards e13f739edd 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards b323ed6d09 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 875b5345d9 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards c2a4ff1380 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 4adbd37fc9 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 245424f950 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 83b2e8ef6e 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 73fa78b878 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards ebe14038e4 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e2e97f1264 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 80ce78bfd5 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards b95e6a9d67 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 8daf7c1b01 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 7a193b91d6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards f1e3436a62 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 8138c15f01 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6693f9e0b6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 04d431b1a0 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 95fe51c09a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards f2ece2683a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ccd068da41 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 286c72034c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards d54f8cb763 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 99d498cf38 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards a643cc97d3 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 46da7dce3e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 583106c754 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards db7ea6d868 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 23a3587101 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards faaa928a7e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 3ad3300f5e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 312d345a29 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards a3ca87e5b9 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 21df94c4f1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards e2e0b0a7d8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 01ba00329d 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards dc1899ee7f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 2748b00deb 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 3f3f71082f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards fbde990aaa 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 889b296241 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards c5ee389a35 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6c27421d17 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 95e6ff4f4b 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 4bf64cd189 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f7a1edcddc 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 34c4573000 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards da324a753d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 40ed485da7 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards f29fa64d52 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b9b9da8328 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards b13436c0a3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 19ef7e587e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 80d7564126 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 103707a1f3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 0f7868e2ff 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c0dc52e236 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f791c94ed0 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 1b696f76d1 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b2a3b10572 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 519cc71007 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new f9b1c3e21d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3514b29ec5 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new c80c091f78 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 547ea3a930 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 194f8e41f8 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 068bae8daa 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 548493e65c 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new ed273ec620 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 1161d8e826 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 50b454fcee 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new dbff8141b1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 9f2f579802 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 6c17fc009e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 679d337125 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 811fe0a660 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 385450af47 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 1314833421 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new ad7b11748f 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 101ec23ae2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7d70cf049e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 92231f7225 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 700ebc4c32 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 3745d06f97 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 971e0bf560 110: onsuccess: #1703: 1: Success after gcc: 6 commits new a7049a2236 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 5141d5f5c4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e1bdbf9934 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f1f9a2acac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9c6b9e62fc 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 021e8a6668 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 510b489766 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 40cdb26619 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 5f3202e499 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new f4eb5fbf23 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new c0628e5c62 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 95bd507c31 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 1f0295995f 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 85434af9dd 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a1ea377a90 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 3b16ec2059 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new f2d096e0e9 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 801d366941 128: onsuccess: #1723: 1: Success after linux: 12 commits new 9590874ca8 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new ad2bb1e7fe 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 2407e69ccf 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 533d99d93e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 16b40a4100 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c3120f4c1d 134: onsuccess: #1730: 1: Success after binutils: 2 commits new a5934a33a5 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e459357635 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 781713ea85 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 5a73fcf87d 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new bc7ec49323 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 2207ed02aa 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 03d2f3fcd7 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 85d95f1c11 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 8bb1b7cca7 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 697dacdf75 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 57106d76ef 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 065c10358b 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 4c92249006 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 02f73d183a 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new cd2597dd6e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new ff0e1871c0 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new f12c9754af 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 93100ecb7f 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new eecb54ae41 153: onsuccess: #1754: 1: Success after gcc: 2 commits new ac52d2959f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new be6ab438fe 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 332b7d61a1 156: onsuccess: #1757: 1: Success after gcc: 4 commits new ddd6801d0b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 44fbe0e01c 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 6efbbd6137 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new f26a2f7ca6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 561fc5cfb1 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 488070ab21 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new b4b93e8abb 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 6a4d8d4442 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 732fdf6a6e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new aa17949e42 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 90b9b5d14b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new a4b5168c08 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 6bc3473cab 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new cbe7b7ecc4 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new e208f19f46 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 99b3b0a589 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new ebc16cb24b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new d56a646123 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new f3f181d85e 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new f15562d1ad 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 00dcf90b31 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new e6a8ce4fee 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 8e1165bcc7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 75dc5da15e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 0413a6ccd9 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 6bb7f056a8 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 340e75ec45 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 30d819b243 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new b4b1df9e9d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new fda657209f 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 36e6249b2d 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...]
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 (5f4429155c) \ 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 1744 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30132 -> 30104 bytes 04-build_abe-stage1/console.log.xz | Bin 90840 -> 91256 bytes 06-build_abe-linux/console.log.xz | Bin 8888 -> 8860 bytes 07-build_abe-glibc/console.log.xz | Bin 235988 -> 236172 bytes 08-build_abe-stage2/console.log.xz | Bin 223472 -> 223784 bytes 09-build_abe-gdb/console.log.xz | Bin 37540 -> 37708 bytes 10-build_abe-qemu/console.log.xz | Bin 31228 -> 31200 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3052 -> 3980 bytes 13-check_regression/console.log.xz | Bin 5628 -> 6908 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 94 +- 14-update_baseline/console.log | 42 +- 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 | 42 +- sumfiles/g++.log.xz | Bin 2712664 -> 2672344 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 2224116 -> 2249848 bytes sumfiles/gcc.sum | 2250 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892076 -> 889940 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 212968 -> 212896 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438384 -> 427112 bytes sumfiles/libstdc++.sum | 2 +- 39 files changed, 1319 insertions(+), 1195 deletions(-)