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 ff621dbcb5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 1d951e2f2b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b16227dd10 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards a6fc1ce02f 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 8c86bef3f5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards b116803e8f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 4a1f0daa06 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards b0c205f361 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 2370dabc5e 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards f502d4b80f 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 83fa9c15ba 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 0f77eb2d08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards b61fdb3f75 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 57fbed27c3 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 6781fbda9e 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards feffe4ff61 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards effd140662 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 7f05b6169d 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d9ff36d65e 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b34e037cf2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards d4b6c07010 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 8fc0a90ff0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 6789dc87b5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d2f395d18d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6988545518 128: onsuccess: #1723: 1: Success after linux: 12 commits discards de42f3f702 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a7f854a471 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 44e7a26ba7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards df0907cf82 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 55037aaa95 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ee5cb5f870 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 13ce89ec29 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 3a2992c529 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards fe49b21234 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 3a93a2a3f0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 135ef10d37 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards bcf87233c2 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c7c0451111 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 4ee84a9b94 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ef382abf50 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 2c5cda828f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 356277c100 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3ebe1593d7 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 7e97687fb8 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cb4dc7ea42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 2ecba69575 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 6884d2ae4c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 15ea730c70 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards bc75d391f6 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 8cf311e582 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 39b82befcd 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 9ae613b91d 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4244d31dd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 87c62c8f8e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 03d7a7f7e6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f4efd47fa9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 599745eb24 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ab9645916e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards e474484e94 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 88ccc41a41 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 861572f7c4 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9eee0cb5eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 9d52fdba53 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 37d1a1ae5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 576b82762b 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 47515cd280 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e2461ac2cf 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b073c139a2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6187bab771 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards f3eb8dc38b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 991676dc99 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3f69ca9ce0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 787a2c277f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards f3b145f502 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 39228cefdd 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards add019f0ff 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 698245907e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards f7aa18647d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5d49feac1f 74: onsuccess: 1: Successful build after linux: 44 commits discards bb09e1d495 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 155e968124 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e12ff442e 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 0d8ab57085 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a0d9f01b1b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards db6032f131 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 12eabb1d94 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4ab06fdddc 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b47ec9fca8 65: onsuccess: 1: Successful build after gcc: 4 commits discards 2db3a1a7f3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c788be814 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9265d5f66 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b2ea7b0380 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 2d63cc63d6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 65af3c3fea 59: onsuccess: 1: Successful build after glibc: 2 commits discards 6e177482ef 58: onsuccess: 1: Successful build after binutils: 2 commits discards 339e4e945e 57: onsuccess: 1: Successful build after gcc: 7 commits discards 5d8748cb2d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03eb593d1a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 39172c2e80 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 0688911fb7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 06420c7c7c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e8551f24e9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 8ba4b2067a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new eb8e007954 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 9d5b309c6d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c6f11b0c2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a355157ce4 57: onsuccess: 1: Successful build after gcc: 7 commits new 57d05c5b00 58: onsuccess: 1: Successful build after binutils: 2 commits new 39dba10390 59: onsuccess: 1: Successful build after glibc: 2 commits new 8984294400 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new bbcb2ad845 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9c2019cf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new d57abef12b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f682b3b4c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45dcfc6a49 65: onsuccess: 1: Successful build after gcc: 4 commits new a242ea9424 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c0ffa6796b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51156f628e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30d11270a7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 46d80d9643 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new dd5af60c44 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new de43a37264 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9627f29912 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a1a47f8568 74: onsuccess: 1: Successful build after linux: 44 commits new b96f696f82 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fb8c62346 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7d66e1c4d9 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa8c8ae89f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 77b85d12d0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c3a01f6120 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 23e897cf8b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d62c49152e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 6e936d87cd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new b3d6bb1a3d 84: onsuccess: 1: Success after gcc/glibc: 9 commits new d4daa9a413 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 698cd6dde8 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e08367dd1a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 25d3bffd77 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 644d99e5cf 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 54a74a99d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8fa2fe3666 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b6f1b90a08 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 13dadffb3d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new ddde8d07d5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new a56fe2dfd8 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 88683acb7d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new fae1611214 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new f106b3cd1d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 6c9117c315 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new f698ec0705 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 8e6e936e42 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 14da978944 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 6dbb07463d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 886c27a001 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 0b919f121c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new d6f4f738d1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 238d385e60 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ee67e17f28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new a2d0a8b2f5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 037e6acccb 110: onsuccess: #1703: 1: Success after gcc: 6 commits new abdaea57f8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 19dab87b43 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 8ecda5ecfa 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new da6660e8a1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new ecef0c6c2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 02bd0b232e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 1678eb05fd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 5414124dc7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f339e3633c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new b7653d7340 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 6de80566d0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 7f98c1bfa7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 8fce5a14c7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 4c78fc981d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ca65df3b26 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a51d539072 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4bbb3f79a1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new ba372532b3 128: onsuccess: #1723: 1: Success after linux: 12 commits new 02633937aa 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a36c47fb82 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 2549c671f5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 4db58376ea 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 75b55f826f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 4708f044b9 134: onsuccess: #1730: 1: Success after binutils: 2 commits new f4cbabb336 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 7ebf9d5804 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 111319437a 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 0c27b588d9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 93ee7abe0f 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new b9a391e3a7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new c439c4a94c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new fce064f1db 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 6633c37870 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 889681194d 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 54efb27810 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new eb2b668a42 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 41139d194c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new f6d7e2e8a2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new e034c5f96b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 48d55df16a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new fc5fc48993 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 58774adb1f 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new a882f4e730 153: onsuccess: #1754: 1: Success after gcc: 2 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 (ff621dbcb5) \ 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 1920 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29916 -> 29860 bytes 04-build_abe-stage1/console.log.xz | Bin 90860 -> 90276 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 234432 -> 233840 bytes 08-build_abe-stage2/console.log.xz | Bin 224160 -> 224272 bytes 09-build_abe-gdb/console.log.xz | Bin 37192 -> 36944 bytes 10-build_abe-qemu/console.log.xz | Bin 31368 -> 31776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2820 -> 2816 bytes 13-check_regression/console.log.xz | Bin 6464 -> 5392 bytes 13-check_regression/mail-body.txt | 40 - 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 48 +- 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 2691360 -> 2668044 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2202388 -> 2231760 bytes sumfiles/gcc.sum | 2166 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 881524 -> 890340 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201600 -> 201416 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422168 -> 432600 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 1259 insertions(+), 1344 deletions(-)