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 be22469ea3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 93c9a8b712 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 909886b2ce 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards b447b3fc1d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 180c584964 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards f3242af5c9 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 9e8b035568 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 21a74ea47c 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards c2def89621 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 87653b3735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 2014e9cd8c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards ccd92d4aa9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards eadf6c8eed 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards a64a1e272a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 46488db0ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 949a6c62a1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 6a8f680e3e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ebaaad2962 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards d239fdee81 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 76a32cb3b2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 826e20d11e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 1e01781b70 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards bb62a55664 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e350d9987a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 5903740896 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 578bf3a719 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 2a7855faf8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 2792f465d8 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 8fa8ffe3e3 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 4960880e1f 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 86664e8516 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 219f6065dd 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 144cc3eded 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a981689307 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards d3a23cb3e4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 0153a9a2cb 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 4f30537b55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 54fb90f967 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards e0066dd6f1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards ffba6f748f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 25823e2216 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 95bff9c995 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6283e6ced7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cf590efcdd 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 9a22133d13 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 602fae82cc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards c3bef21ba6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 39adf8cc24 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 14ac9a099b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b2c4262913 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards df67eef8a0 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 7174c5f6f4 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 37a4d92771 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 29429d71f1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 22aeca399b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 533a61f689 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f0a73b0ad5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 5ac05d11c3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards c2600f27af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 528a801d5b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 3ba5601b0f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 184ab19a71 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 556a3b0663 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e3479b08ed 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e8288fc131 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e54f133e71 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards adf05ba43b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards c7d9223c89 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 3364880c6f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6d77c265c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5ddbbff27e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 17d6de449a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 200f42b170 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 76f5b070ee 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 451d7dbe39 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2cbfd1263 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 986e545050 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 53fc1bc285 74: onsuccess: 1: Successful build after linux: 44 commits discards 21215796ef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 74a81fb194 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d7a51559de 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5ef792ad56 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards ed8c9f3ea1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards a53320e710 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 64f4be014b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 02dda90490 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2009a6fc70 65: onsuccess: 1: Successful build after gcc: 4 commits discards af278c90d8 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c4acb4f4b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 315e609fe8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards c8a9710061 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 245aa6b28c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d3aa5d91b0 59: onsuccess: 1: Successful build after glibc: 2 commits discards fd5454f717 58: onsuccess: 1: Successful build after binutils: 2 commits discards 700be9be19 57: onsuccess: 1: Successful build after gcc: 7 commits discards 451f7f1b15 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e2c3245533 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0eed999457 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 7e834a6fef 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b2958b3c3b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fb27844bcd 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dd39213e0b 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 06420c7c7c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0688911fb7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 39172c2e80 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 03eb593d1a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d8748cb2d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 339e4e945e 57: onsuccess: 1: Successful build after gcc: 7 commits new 6e177482ef 58: onsuccess: 1: Successful build after binutils: 2 commits new 65af3c3fea 59: onsuccess: 1: Successful build after glibc: 2 commits new 2d63cc63d6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b2ea7b0380 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9265d5f66 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1c788be814 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2db3a1a7f3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b47ec9fca8 65: onsuccess: 1: Successful build after gcc: 4 commits new 4ab06fdddc 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 12eabb1d94 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new db6032f131 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a0d9f01b1b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 0d8ab57085 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 0e12ff442e 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 155e968124 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb09e1d495 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5d49feac1f 74: onsuccess: 1: Successful build after linux: 44 commits new f7aa18647d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 698245907e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new add019f0ff 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 39228cefdd 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f3b145f502 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 787a2c277f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 3f69ca9ce0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 991676dc99 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f3eb8dc38b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6187bab771 84: onsuccess: 1: Success after gcc/glibc: 9 commits new b073c139a2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e2461ac2cf 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 47515cd280 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 576b82762b 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 37d1a1ae5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9d52fdba53 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9eee0cb5eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 861572f7c4 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 88ccc41a41 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e474484e94 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ab9645916e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 599745eb24 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f4efd47fa9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 03d7a7f7e6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 87c62c8f8e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4244d31dd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 9ae613b91d 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 39b82befcd 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 8cf311e582 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new bc75d391f6 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 15ea730c70 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6884d2ae4c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2ecba69575 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new cb4dc7ea42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 7e97687fb8 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3ebe1593d7 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 356277c100 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2c5cda828f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new ef382abf50 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 4ee84a9b94 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c7c0451111 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new bcf87233c2 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 135ef10d37 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 3a93a2a3f0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new fe49b21234 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3a2992c529 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 13ce89ec29 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ee5cb5f870 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 55037aaa95 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new df0907cf82 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 44e7a26ba7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a7f854a471 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new de42f3f702 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6988545518 128: onsuccess: #1723: 1: Success after linux: 12 commits new d2f395d18d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 6789dc87b5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 8fc0a90ff0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new d4b6c07010 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b34e037cf2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new d9ff36d65e 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 7f05b6169d 135: onsuccess: #1733: 1: Success after binutils: 5 commits new effd140662 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new feffe4ff61 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 6781fbda9e 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 57fbed27c3 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new b61fdb3f75 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 0f77eb2d08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 83fa9c15ba 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new f502d4b80f 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 2370dabc5e 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b0c205f361 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 4a1f0daa06 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new b116803e8f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 8c86bef3f5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new a6fc1ce02f 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b16227dd10 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 1d951e2f2b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new ff621dbcb5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...]
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 (be22469ea3) \ 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 1684 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30040 -> 29916 bytes 04-build_abe-stage1/console.log.xz | Bin 91148 -> 90860 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 234236 -> 234432 bytes 08-build_abe-stage2/console.log.xz | Bin 223816 -> 224160 bytes 09-build_abe-gdb/console.log.xz | Bin 37436 -> 37192 bytes 10-build_abe-qemu/console.log.xz | Bin 31292 -> 31368 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3172 -> 2820 bytes 13-check_regression/console.log.xz | Bin 5316 -> 6464 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 61 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 48 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results | 40 - sumfiles/g++.log.xz | Bin 2667116 -> 2691360 bytes sumfiles/g++.sum | 37 +- sumfiles/gcc.log.xz | Bin 2229916 -> 2202388 bytes sumfiles/gcc.sum | 2401 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 885780 -> 881524 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201444 -> 201600 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425100 -> 422168 bytes sumfiles/libstdc++.sum | 11 +- 43 files changed, 1355 insertions(+), 1509 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