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 dd0d23501f 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 3463f08d46 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards bcbe73e3b4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 7ff5666b6e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 63e3d5c6cd 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 14efe4f21b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 196dcecc16 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 232cedcf27 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards a7ed720694 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 31da5a1cee 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 3284ef3a61 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 2a41917b16 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 27f993db34 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards c4f14e6b68 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 73c2be95a5 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 1f747dea02 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 208dc0de72 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 2891848af1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 0ea851af38 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 3bbcdc52c5 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards f92ecdee0f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards f57fb97a9d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 63859ce7b5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards b0150ca119 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 879c4176fc 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards fa2c401405 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 75afc10d26 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 6b1dcd29f3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 259a028b77 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 52bd9b33e7 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 07b7d46c8c 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards a2a6d8fdad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 4f5210f735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 603ea273ef 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards aef3c811e8 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 27f84ae717 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 8782632382 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 4e54dc4c6c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 45cea36b25 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards e3f81eae0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards e17b009aa2 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b7e7c2c7b2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards cca68c0192 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards e8ba8971e7 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 4d81bebeb5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 633106ddfe 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards bc8cb33f8c 128: onsuccess: #1723: 1: Success after linux: 12 commits discards befd3bd75a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 5db474567c 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 3e596ceaa2 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards dedd557498 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards c555e34276 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 5f413b9275 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 7ed25814b0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 32d493a9cc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 914d5921bc 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 922dd93460 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 653eb54d51 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards da8b5bc6f0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 3fb7eb2bc4 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 56cc21dad1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 37e4d5c427 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 2c15e251b1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 2e871697ef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards e1641919fd 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 4fda817db4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 16e406ea44 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 9aec2fb9af 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 8d8d02f84e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards e4e3ec1268 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards c5fc2bca54 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 7275e5ec37 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 15cf3c3a80 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ad8be835d2 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 0cacf6c55d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards f5e528f9ae 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 5971142123 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards d76a75de48 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 57d41791a3 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 4fa59f29b0 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 8511cc1e25 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards c389d1a58f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b588a1229f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards c7319e6b58 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards e0b3bbb227 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 48b2c1b2d6 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 30f74f3fce 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 460ac12fd9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b6e58d22d6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards dfe161ce9f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 4817adad1a 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 52d0e0e468 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards d1594c5f9f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 68cc75c977 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 886f5d14f2 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 900c18f71d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 56f09a1bf4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0c23e26d6c 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 63916ec43e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 573d2b46fa 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 97e7b8074f 74: onsuccess: 1: Successful build after linux: 44 commits new c3cded44b7 74: onsuccess: 1: Successful build after linux: 44 commits new 25fb1d0b8f 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5478e809d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 08a03e4348 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 57c5f64a35 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9fea54a026 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c74be6cbaa 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 3aefe07f41 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new a9908c54fb 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 338dbcb58d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 24adfad8d5 84: onsuccess: 1: Success after gcc/glibc: 9 commits new d1f946e0ba 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 81447a8a06 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d88684a0a7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new d229a91f03 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 37ffc58ad7 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 49a037f6d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new bbcf96511b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 320aa17bca 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 653102ecf3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new deaf4b12a6 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new f6ec4447c3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 8b1a631ec4 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d569ac16e9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new bc468c62bb 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 495b7d59ba 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 8c627b3fd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new dff3ca3cd7 101: onsuccess: #1693: 1: Success after glibc: 14 commits new a85722f874 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new aade2441c0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new e168b85195 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d63d2fa724 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a7888ce4e3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f6def69b7a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new bde101c967 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 2252f6009a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new e10003f886 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f8c2e1a15d 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new bade21897f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 28318ab1ea 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new b7a4ac3707 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 958bb1e71b 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new c6864c5cf2 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 7f44d21ab7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new fbfd013dd4 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f302455f5e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 4f71af4b6d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new cb68038c99 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 8b8c1ee0b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 3418fa8dcb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 53b710be59 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 181480f244 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new e1aac778ad 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 2c55a5b161 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new fe99fcbe8d 128: onsuccess: #1723: 1: Success after linux: 12 commits new 0fa6edf7d1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 9ceff035c7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e18a6b2a4b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 0ce509e092 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 99e44a0985 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 8ebe72955f 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 8220377e86 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 2fbe25446b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new dc93552753 137: onsuccess: #1736: 1: Success after gcc: 5 commits new ad8ac2003f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new aad2fa8ba8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 5549fdfd82 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 5811dee359 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new c0c503d73c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 746677860e 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new e36fd4ceb3 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 69393bc903 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new d02ba42289 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new c28d73f0ae 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 2889be22d0 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 6fd8e16405 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 798dbb0e26 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 30acc6acc5 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new e836229f3a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new d2e4279c4d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new d3dcffe4a3 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new bd49b2698b 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new caa49a140c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 500748bd8c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 6a92f5f6ac 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 67049d1875 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 61b10fb1ae 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 6f3d7185fc 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 96301a6605 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new c869860f00 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new a13245f5e2 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new b541589f01 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 2827f46425 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new f302ff390f 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 3e4529c428 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new a028935bf2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 9da3e7c582 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 4972d05643 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 551827c2e8 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 119fe18fc1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 8c801045eb 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 3e4d398f24 175: onsuccess: #1776: 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 (dd0d23501f) \ 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 1696 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30028 -> 30552 bytes 04-build_abe-stage1/console.log.xz | Bin 90924 -> 90808 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 236272 -> 234256 bytes 08-build_abe-stage2/console.log.xz | Bin 224160 -> 223800 bytes 09-build_abe-gdb/console.log.xz | Bin 37512 -> 37980 bytes 10-build_abe-qemu/console.log.xz | Bin 32468 -> 31524 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2460 -> 2648 bytes 13-check_regression/console.log.xz | Bin 6592 -> 6116 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 70 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 60 +- 13-check_regression/results.regressions | 30 - 14-update_baseline/console.log | 54 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 72 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 30 - sumfiles/g++.log.xz | Bin 2655948 -> 2656620 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2238232 -> 2208992 bytes sumfiles/gcc.sum | 2158 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 883248 -> 887552 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201488 -> 201500 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426080 -> 432632 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1221 insertions(+), 1383 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions