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 e15e88bf49 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 25f2164948 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards c59556df9c 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 9d1dc356fe 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 925a8a560b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 2a5e57ea64 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards fe48e7c890 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 4aff865394 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 8ad02e3b94 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 5cd0b2f450 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 75f83f74b4 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards aa99bfc610 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 0dc460b26c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 35caa48fcd 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 72fe913677 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards b2a329cfb2 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 8475f08899 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 819fb1c12d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 7bafe31115 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 76126432a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 3d7f91d9f3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards c5cefc6e94 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards bc1ec4c257 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 6ac4a37f71 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 56144f788d 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 2d18f90967 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards d38afdd9d1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 4e5335cf78 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards d7f2ee2c71 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards b7d055c6f5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 22d1c5eec8 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 2567b2ca5b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 5b452361ba 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 03f3473f00 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 50bc5185c7 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 36f8fb7497 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards f3a0b8b8b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 23c24cc36e 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards a5e88d6eb2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards c27b385a25 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 4285f47b30 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 12ee00998f 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards f928a27599 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 730a1ce55e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards e36111d369 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 44ff92f8c6 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 0fbdb67eed 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 41f6fa258f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 57e5f85fb7 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards ba11a374a0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 66b5a9f6f2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards a4f70a0634 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a7a46cacdd 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards a7f8531766 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 5291ee5c0b 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 30de8ab6fc 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 31855f1630 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 87ffb2d6ca 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f51e82156c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 94a2e2a826 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards b3a2bc3dc4 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 4f3721f78e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards cc561b533c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 275b39ece5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 3552225678 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 10ebe55e36 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 286de4b607 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards d3f385a531 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 0d0cbbe0db 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0c16a7ff32 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards dd062f5b07 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0e736ffff5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards f160579397 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2f0c757c49 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 073a7652f4 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 2f35e4f77e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 984ca5fb8c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6b354ef39b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards dafe4eb5a4 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards cd702b528b 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 82819dc76a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d2a98f0fc3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bedd8bcc18 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards faac05f0f4 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards edaabc8925 74: onsuccess: 1: Successful build after linux: 44 commits discards f9241ce0d6 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 28cd5942dd 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee5858bb4c 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 1d1408cfff 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards e666bc676a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards b38479dac8 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a488f28b8 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 260296f590 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 55a0eb4f62 65: onsuccess: 1: Successful build after gcc: 4 commits discards 51b7aeb704 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards df657412f9 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b26aea5b43 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards ad5d390a5c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b0ee4d416e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 02c6301c06 59: onsuccess: 1: Successful build after glibc: 2 commits discards 404b50d6e5 58: onsuccess: 1: Successful build after binutils: 2 commits new f3e6a9f700 58: onsuccess: 1: Successful build after binutils: 2 commits new 70a9c09306 59: onsuccess: 1: Successful build after glibc: 2 commits new c6b3e4d39a 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b0b3e05670 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new a9641cb4a6 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f9e37a679a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 22081ddc61 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 90993edc03 65: onsuccess: 1: Successful build after gcc: 4 commits new f1195d6b66 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4cc05c2a6e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8e8d0d088e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 169d0eb5ef 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 2452a1aea4 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 5f7dceff80 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 32d8906bde 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 610b36eab7 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7034cd1fd4 74: onsuccess: 1: Successful build after linux: 44 commits new e5e97be36d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65f7838c73 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 4633a41a03 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5071cd1da2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9c86f60d07 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 06469062ff 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 59a33b3ac2 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 488cd429b2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0f34f0c64e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 0fdc820a1e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 5877ab06ae 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b2b14ef501 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 107df4093b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 16e9b61638 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new fe4090ac83 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 991f6ec6ff 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c3f7ef0c0d 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b4db25a8b3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 49a7c55995 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 14c5960623 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 92289b5f5f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 29f865ff7a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ce1114733a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new d38a5af1c6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 31b427d2dc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b1ed3b0b61 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new fb3f7ad00a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c4d790673c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new dd044e7a36 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 709351081b 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d31dcb32f7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a7e1c1fd5b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new e3aeba8184 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 7e16e613bc 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 177575c95e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fed6e0763d 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 5114f12ccf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 82d67016e9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 4feedf520a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 69c036eb9d 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 6a83afe4e1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 910405a806 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b51f649b13 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 2f2abbe83b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new b4be7a77bf 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 529c5b1075 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 96a8c734fc 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new bdaa81022a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 9eb56a1e38 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 0f78343226 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 4742e7e4b9 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new d777dd5035 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 206e10aebd 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e2ea50de6a 128: onsuccess: #1723: 1: Success after linux: 12 commits new d43d8954b9 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 19499d893d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new cbe5af6c39 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a1d9e01b9f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 9beb51d3a8 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 43d315af10 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 3c65758f80 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 68c18d080e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new c9a5979380 137: onsuccess: #1736: 1: Success after gcc: 5 commits new befcf4ccf3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 116a01a3ec 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new a92b7e36cc 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new cc02d95ab9 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 72cd0010d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 889baf0cc0 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new a706b24f99 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c900e456e9 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new cb8ce74e84 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 714500a00f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 99d3d2bf2d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 280078f9e1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new a97fccb798 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 514e56f611 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new eae6c43256 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 9039197c8d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 782c79aa42 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 7428eca236 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 155e291c7e 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2e792b60f5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 1d79899b66 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 5561dc107c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 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 (e15e88bf49) \ 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 1680 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30012 -> 30328 bytes 04-build_abe-stage1/console.log.xz | Bin 90668 -> 91120 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 234208 -> 233868 bytes 08-build_abe-stage2/console.log.xz | Bin 223748 -> 224956 bytes 09-build_abe-gdb/console.log.xz | Bin 37144 -> 37380 bytes 10-build_abe-qemu/console.log.xz | Bin 31576 -> 31256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2420 -> 2996 bytes 13-check_regression/console.log.xz | Bin 5564 -> 5296 bytes 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 20 +- 14-update_baseline/console.log | 36 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2675652 -> 2692488 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 2222920 -> 2203488 bytes sumfiles/gcc.sum | 1924 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891784 -> 883916 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201596 -> 201460 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429304 -> 425872 bytes sumfiles/libstdc++.sum | 2 +- 37 files changed, 1032 insertions(+), 1054 deletions(-)