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 448523c6b8 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards d0240683ad 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 1ed8327915 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 4d7b8ccbe7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 02f6d1a1de 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 992dca57e9 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards e7535d5f6a 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards d467848945 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 6fc190c61b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 9dead4f250 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 7890eac7ac 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards b36030f1cc 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards d9d5dc595c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards dd9b57b70d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards f1bb16938e 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 858c0fd280 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards fa02531254 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards a892add553 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards f1995ad5df 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards a2ebcec634 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 13a94d557f 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards b4507beb6c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards cc3dc1ef7a 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 8f68d325bd 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 4e9200cf7c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 3d847f5e4b 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards f686d503b0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8102069899 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c2dd1cff4c 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 4fabfd359d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards c48e2bf526 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards bcbac98e94 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 2fcdfe63fa 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d36f149b23 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 60b2c2afca 128: onsuccess: #1723: 1: Success after linux: 12 commits discards bdfce0e94b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 60bb9db1f2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1c69d0d515 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards de1749134e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 65925a19e7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7212fed5ae 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards c195caf4f0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards bdf41074de 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 2d454f75c8 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 91c0e514c3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9b9d032c49 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 13a95c827d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 6fb1ac7666 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d07bf19e3f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards d2f351270d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 372da95bc1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 0fbd499e32 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 1f3d43f67a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6041ae469e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 9f2b051e37 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards c9e8c38aff 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 91381dadb1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 51b1725535 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 031e6eb0ca 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards c026702245 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards bc99d97d11 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ab2ad20e78 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 8e3f8f8acf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 48b3d93ff7 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards df6a0a652e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards b3ae8a9b2b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c2562eddfa 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 1730904208 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 87761395f6 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 562c5b8fce 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards fe60781a45 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 992ce7e3e7 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 72551749f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 336401f9a8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e1eef48c90 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 86cbd6a9a2 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 4ea9090020 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 4d60bc3f92 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f6792a08a2 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ae00fa4204 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0ee0d72923 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9321d8493d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a25f985d26 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards a0e9b4c0a8 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards f7ece26da6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5926ea5527 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a5baac5fb9 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 7667a238fc 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f9d22e3e9 74: onsuccess: 1: Successful build after linux: 44 commits discards c71f786923 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards bdf0798d67 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca130957de 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 025c06a9b3 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 07720536bb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards d843aeda52 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3932d7964f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3ee6192608 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0aa8496de0 65: onsuccess: 1: Successful build after gcc: 4 commits discards 7309b681a4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 020b1609dd 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a57a3312fa 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c4843acb61 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b9c338ace4 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21892102e9 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28d6ef4d06 65: onsuccess: 1: Successful build after gcc: 4 commits new 7a71c2a9a7 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3da5311298 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20945e937c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new decd4c7ea2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new a1c8cbcace 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new aa88400261 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new c03811fd26 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c168688c75 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9cacf00b72 74: onsuccess: 1: Successful build after linux: 44 commits new dc50daccb5 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d8eab329b8 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 0153ace560 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 960e5b48fb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4383b21aae 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 47ce9f51ef 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 6a7a75d8f4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new e5b04453b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0763df29c8 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 8c40974b18 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 7b4cdf4cde 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 376af32620 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new c8c6fea90c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 7c1cddb0de 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ae34d4fca4 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new afe8d42b52 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2ea89c9bbb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 185db167e6 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 6822d3b53e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 42b73e9913 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 81f57ecc47 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b46a289250 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3f61daac5a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 7e33e43f5c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 7470d8d002 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b593271de6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 0d04182077 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 13c6bb8fd2 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 0aa37fd2e3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a4a722ab95 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 4eaad04c40 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a0391ceb78 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 45226893fa 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new fd22ecc2b2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new f9bfd3f2b9 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 268b273224 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 12f1d23765 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new f1acd2c39b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 745a5a7cf0 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new dd8560f937 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new fe87a1c39c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new e37bcad012 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 58962cb019 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 010362aadd 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 449f7e596e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 89f150cd07 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new d7b7cce1f2 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 8f18d0c02c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 5c4e235445 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 10f118bb83 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 5f7dc455f1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 6ce96052e3 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d282f94d09 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6122f62122 128: onsuccess: #1723: 1: Success after linux: 12 commits new ea4501a145 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3dcc71a52b 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new bae66ef2da 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 6d1eb774c2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 7cec31b28e 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 0b7e1f6ebe 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e24dfe7b9b 135: onsuccess: #1733: 1: Success after binutils: 5 commits new dbf96cf4e3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 2ac24ed81e 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 6615f26bd0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new bc830da483 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new a1981a5982 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 56925f0f38 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new fc1bdc5483 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new b0ed45a633 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new aa70d480e2 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 007252073d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 93113c0e5a 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 4c35e68ce2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new f3ff4bdcaf 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 5a34220aab 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 0207880df1 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 876a2b3f23 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 3323f1378d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 9ea27d3939 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 2d6f01a79d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 888f142d19 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new c224c99a4f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8d57bc457f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 471876c565 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 318312bc9a 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new dedc7336ec 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 2d93499990 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new b8a570f22f 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 66479997e8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits
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 (448523c6b8) \ 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 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 30156 bytes 04-build_abe-stage1/console.log.xz | Bin 90592 -> 90552 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9956 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 234052 -> 234360 bytes 08-build_abe-stage2/console.log.xz | Bin 223476 -> 223052 bytes 09-build_abe-gdb/console.log.xz | Bin 37136 -> 37056 bytes 10-build_abe-qemu/console.log.xz | Bin 31632 -> 31888 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2420 -> 2708 bytes 13-check_regression/console.log.xz | Bin 6876 -> 6156 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 63 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 26 + sumfiles/g++.log.xz | Bin 2669836 -> 2665848 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 2193148 -> 2232360 bytes sumfiles/gcc.sum | 2435 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 880740 -> 887284 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201484 -> 201452 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428120 -> 427368 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 1563 insertions(+), 1397 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions