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 66479997e8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards b8a570f22f 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 2d93499990 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards dedc7336ec 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 318312bc9a 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 471876c565 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 8d57bc457f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards c224c99a4f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 888f142d19 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 2d6f01a79d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 9ea27d3939 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 3323f1378d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 876a2b3f23 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 0207880df1 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 5a34220aab 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards f3ff4bdcaf 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 4c35e68ce2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 93113c0e5a 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 007252073d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards aa70d480e2 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards b0ed45a633 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards fc1bdc5483 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 56925f0f38 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards a1981a5982 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards bc830da483 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 6615f26bd0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 2ac24ed81e 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards dbf96cf4e3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards e24dfe7b9b 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 0b7e1f6ebe 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 7cec31b28e 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 6d1eb774c2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards bae66ef2da 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 3dcc71a52b 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards ea4501a145 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6122f62122 128: onsuccess: #1723: 1: Success after linux: 12 commits discards d282f94d09 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 6ce96052e3 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 5f7dc455f1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 10f118bb83 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 5c4e235445 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 8f18d0c02c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards d7b7cce1f2 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 89f150cd07 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 449f7e596e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 010362aadd 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 58962cb019 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards e37bcad012 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards fe87a1c39c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards dd8560f937 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 745a5a7cf0 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards f1acd2c39b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 12f1d23765 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 268b273224 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards f9bfd3f2b9 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards fd22ecc2b2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 45226893fa 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a0391ceb78 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 4eaad04c40 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards a4a722ab95 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 0aa37fd2e3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 13c6bb8fd2 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 0d04182077 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b593271de6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 7470d8d002 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 7e33e43f5c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 3f61daac5a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b46a289250 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 81f57ecc47 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 42b73e9913 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 6822d3b53e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 185db167e6 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 2ea89c9bbb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards afe8d42b52 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ae34d4fca4 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7c1cddb0de 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards c8c6fea90c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 376af32620 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 7b4cdf4cde 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 8c40974b18 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 0763df29c8 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards e5b04453b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6a7a75d8f4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 47ce9f51ef 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 4383b21aae 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 960e5b48fb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0153ace560 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d8eab329b8 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards dc50daccb5 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9cacf00b72 74: onsuccess: 1: Successful build after linux: 44 commits discards c168688c75 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards c03811fd26 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa88400261 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards a1c8cbcace 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards decd4c7ea2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 20945e937c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3da5311298 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a71c2a9a7 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 28d6ef4d06 65: onsuccess: 1: Successful build after gcc: 4 commits discards 21892102e9 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9c338ace4 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cfe3850a61 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 444ceba509 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3d476c5362 65: onsuccess: 1: Successful build after gcc: 4 commits new 9941270645 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d74a3d2fee 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 478af8add7 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8d81ed5110 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new c3501b72dd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new eac7b2b8f0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new d9dffeba62 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f33dbd38fa 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9bf1417551 74: onsuccess: 1: Successful build after linux: 44 commits new 78444ae301 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b2c699948 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 5d35a015f6 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0627b90040 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fcec1814c2 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 4dcffd2c2e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 1689c3d468 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2d3b2cb469 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 253d959aa0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new aafa20102a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new ae68286378 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new ad3242200c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 968326432c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 43c29eb70a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e4cc7e43f1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 32869c1956 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new aeb383503a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 44638ad445 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 0f99751928 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new bf26233056 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 7038229704 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b470bfbc3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 163ce16f60 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 9784a18677 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 9f00223304 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 0a1fe02b36 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 38dbb2acd1 101: onsuccess: #1693: 1: Success after glibc: 14 commits new d2b4976c05 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 57208266ab 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 4489b554a8 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 586ab21c66 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new f695dcf072 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 0cfb705a19 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 6425a8391e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 1177425c3c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new ae0ec6d099 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 9e1138302c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 5b89b729eb 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new de71a8f997 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new d8e8787f17 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9e8b3c2a66 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new bbb7a76b48 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ff312dbbe8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new e2fa023722 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 97531635db 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 4afd045c83 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new cc8f029cb7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 39121bb457 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 52d98df9fa 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 426b74dc4e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 70caa0ecfe 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4dd7a206bb 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 45f8d4f44e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e099c2408b 128: onsuccess: #1723: 1: Success after linux: 12 commits new 39a3371ad9 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new ba429452c8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 2bacb8e1c5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 03175318a1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b9e1076c77 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new ed68f415b2 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 1bdf408fb5 135: onsuccess: #1733: 1: Success after binutils: 5 commits new c9fe0195c6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 421f788183 137: onsuccess: #1736: 1: Success after gcc: 5 commits new e2e1a3c2a9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 9401618ec8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 6deb68fd54 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 88e1401e84 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 840a813c92 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 4eaa9c5730 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 536336db4b 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 1db93cf34c 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new fb9b70e9de 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new c675cbc154 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 8b824eb4f9 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 122e109062 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new afde9137b3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 6e7a3ee799 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 1d6fc392b2 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 87ebda3d91 153: onsuccess: #1754: 1: Success after gcc: 2 commits new d28e17d771 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 3cbe051dc8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 96a52fb236 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f6d252c968 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 738db955d9 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 739f5ebf25 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 4dfdfd64de 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 7935331b89 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new bd63c3f3ac 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 98c83c1291 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new f2c848fffb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...]
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 (66479997e8) \ 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 1708 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 30024 bytes 04-build_abe-stage1/console.log.xz | Bin 90552 -> 90620 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9168 -> 9152 bytes 07-build_abe-glibc/console.log.xz | Bin 234360 -> 233800 bytes 08-build_abe-stage2/console.log.xz | Bin 223052 -> 224084 bytes 09-build_abe-gdb/console.log.xz | Bin 37056 -> 37640 bytes 10-build_abe-qemu/console.log.xz | Bin 31888 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2608 bytes 13-check_regression/console.log.xz | Bin 6156 -> 6412 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 31 +- 13-check_regression/results.compare2 | 195 ++- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 - sumfiles/g++.log.xz | Bin 2665848 -> 2690272 bytes sumfiles/g++.sum | 240 ++- sumfiles/gcc.log.xz | Bin 2232360 -> 2212152 bytes sumfiles/gcc.sum | 2632 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 887284 -> 884764 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201452 -> 201500 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427368 -> 432940 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 1803 insertions(+), 1638 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