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 5ff743c5b3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards c4f36cb77c 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards b89ad94942 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 7f1fcb1aa4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 45da3cd9b8 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 7d001a576d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 5d927d71c6 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 30313766d4 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 054b1d2182 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 2a722f4fca 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 5f5063c716 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards f2b648fb9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards bb829aac99 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 0095cbf25f 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards d05b4eaca9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 793b025dc5 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c9da380fd6 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 91eec19290 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 1403e301ba 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards e57bff34f6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards c8163e6e46 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6b0db4273c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6dca6aaacb 128: onsuccess: #1723: 1: Success after linux: 12 commits discards de9111dd1a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards efdc0c5110 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1ab787969e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 5d8d8d8b1d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 0176eb0cab 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7b1e4c33bb 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards b153967597 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards f6499222e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards e9d6b24a7c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a6e086d4f8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7c7e41e0c9 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 99e70b99d1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 73096b6c9a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 65c40aea67 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 7a4c8af082 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 1639a573d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards ab2848b45c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 07dc331bec 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 92af2765eb 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 6cd8175017 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6fdbc67ca5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c0fd022f11 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards ecda3331fd 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards e51dce9c94 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f292704a0f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 9db737ff43 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 2eb5875d9e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards cff1b9c2f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d2b827105f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 33b39abf66 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards d37f0b758c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c3fb8eaba5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 193935ddb9 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards c48b015212 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 88c1b85c0e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f47b979cbc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards de72ecea99 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b372f347f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 79154a537c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2e25d0c796 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards ab1b248fdb 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 63da97653a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 26bd683491 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 90e0996b88 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 8fe15a0c0c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2933b505b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e6bd18213c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6fc45e3aa3 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 54d07d776e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d5ff1c9d97 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6ddc1c5fc3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa4a4f9eda 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 2d15305894 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards afc0e77016 74: onsuccess: 1: Successful build after linux: 44 commits discards b2b20b42ad 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b5aaf16e02 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59b01a7130 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 6ceecb7518 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6958d48eca 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards cc1bb61150 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b9fb74467 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 564cd633ed 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 642609f3c6 65: onsuccess: 1: Successful build after gcc: 4 commits discards 51b2bf706c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bddac867c7 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc85d10525 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 835d31095d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e074ff7971 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 51e36cc1bd 59: onsuccess: 1: Successful build after glibc: 2 commits discards a0ab07e12f 58: onsuccess: 1: Successful build after binutils: 2 commits discards 818bba84e3 57: onsuccess: 1: Successful build after gcc: 7 commits discards bb06c17286 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2fffe0681f 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c6fd883a5 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 59c29b850a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 00099e56ea 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 6c4851d9c5 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b34a4ff93c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb025feb3e 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fb27844bcd 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b2958b3c3b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 7e834a6fef 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0eed999457 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new e2c3245533 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 451f7f1b15 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 700be9be19 57: onsuccess: 1: Successful build after gcc: 7 commits new fd5454f717 58: onsuccess: 1: Successful build after binutils: 2 commits new d3aa5d91b0 59: onsuccess: 1: Successful build after glibc: 2 commits new 245aa6b28c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c8a9710061 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 315e609fe8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 4c4acb4f4b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af278c90d8 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2009a6fc70 65: onsuccess: 1: Successful build after gcc: 4 commits new 02dda90490 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 64f4be014b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a53320e710 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ed8c9f3ea1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5ef792ad56 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new d7a51559de 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 74a81fb194 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21215796ef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 53fc1bc285 74: onsuccess: 1: Successful build after linux: 44 commits new 986e545050 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2cbfd1263 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 451d7dbe39 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 76f5b070ee 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 200f42b170 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 17d6de449a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 5ddbbff27e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6d77c265c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3364880c6f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new c7d9223c89 84: onsuccess: 1: Success after gcc/glibc: 9 commits new adf05ba43b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e54f133e71 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e8288fc131 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e3479b08ed 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 556a3b0663 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 184ab19a71 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3ba5601b0f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 528a801d5b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new c2600f27af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 5ac05d11c3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new f0a73b0ad5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 533a61f689 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 22aeca399b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 29429d71f1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 37a4d92771 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 7174c5f6f4 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new df67eef8a0 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b2c4262913 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 14ac9a099b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 39adf8cc24 104: onsuccess: #1697: 1: Success after gcc: 4 commits new c3bef21ba6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 602fae82cc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 9a22133d13 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new cf590efcdd 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6283e6ced7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 95bff9c995 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 25823e2216 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new ffba6f748f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e0066dd6f1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 54fb90f967 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 4f30537b55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 0153a9a2cb 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new d3a23cb3e4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a981689307 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 144cc3eded 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 219f6065dd 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 86664e8516 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 4960880e1f 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 8fa8ffe3e3 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 2792f465d8 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 2a7855faf8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 578bf3a719 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 5903740896 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e350d9987a 128: onsuccess: #1723: 1: Success after linux: 12 commits new bb62a55664 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 1e01781b70 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 826e20d11e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 76a32cb3b2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new d239fdee81 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new ebaaad2962 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 6a8f680e3e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 949a6c62a1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 46488db0ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a64a1e272a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new eadf6c8eed 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new ccd92d4aa9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 2014e9cd8c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 87653b3735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new c2def89621 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 21a74ea47c 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 9e8b035568 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new f3242af5c9 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 180c584964 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new b447b3fc1d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 909886b2ce 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 93c9a8b712 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new be22469ea3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...]

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 (5ff743c5b3) \ 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 1688 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 30040 bytes 04-build_abe-stage1/console.log.xz | Bin 91196 -> 91148 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 233600 -> 234236 bytes 08-build_abe-stage2/console.log.xz | Bin 225056 -> 223816 bytes 09-build_abe-gdb/console.log.xz | Bin 37416 -> 37436 bytes 10-build_abe-qemu/console.log.xz | Bin 31468 -> 31292 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3148 -> 3172 bytes 13-check_regression/console.log.xz | Bin 7736 -> 5316 bytes 13-check_regression/fails.sum | 3 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 21 +- 13-check_regression/results.compare2 | 217 +-- 13-check_regression/results.regressions | 21 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +- results | 21 +- sumfiles/g++.log.xz | Bin 2658932 -> 2667116 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2203868 -> 2229916 bytes sumfiles/gcc.sum | 2538 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 887140 -> 885780 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201608 -> 201444 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429464 -> 425100 bytes sumfiles/libstdc++.sum | 6 +- 39 files changed, 1451 insertions(+), 1627 deletions(-)