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 37db4a2a63 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards a03517cd64 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 525d731af4 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards cf7cdd3a38 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards d08238b13c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 0f5af9d551 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 32efe5cb0a 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7540ed7896 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards d0bbb791b6 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 0c35115542 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards b26880c3f5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 2ebb594386 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards e7ffeeeb89 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 5efced6c89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 5e0f2ac750 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 21ded787d4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 2ba6eafa01 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards dea5ad64f9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 6f73568d5c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards daa552e0e6 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards a30e39b47a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8fa6506b97 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 45600e11ed 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9b0b6e57d3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards f520d1a030 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 59a90c74ea 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f27ab951a2 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards c28eaa24ff 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 69c9ab6dd6 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6ec8e2dd37 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards e1b78d3064 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 70b7848663 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 27705bee35 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 85c4fe614f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 56f6717c70 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 166f14763a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 22b9caf9af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 4c731b7f53 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 8436782d4f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d7a03bdc90 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f07314b4d0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e1dde4c011 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 5fbb2d8f16 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 35cbd6f0be 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 0ee8253d90 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 7f7a5f6c00 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 79d271f331 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 77ffa7695b 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6634c8db87 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 2338b2312e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 23b2c87b74 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 18b5aea4f5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7dea4df532 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3286ee1a9c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 88b0840b30 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a626c4e0bc 74: onsuccess: 1: Successful build after linux: 44 commits discards c59076a478 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards c58e923722 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d1e72b9153 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards c7727c1b79 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a427bd0f34 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards cc43c09c2e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e1c4b1ab86 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce64403521 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a9f8b8aee1 65: onsuccess: 1: Successful build after gcc: 4 commits discards 9a0dfa4055 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 19ff1a2ffe 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ec1023d93a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 35903c16ac 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 15810301a3 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 338ded01be 59: onsuccess: 1: Successful build after glibc: 2 commits discards d8d51a08c1 58: onsuccess: 1: Successful build after binutils: 2 commits discards 98752c4499 57: onsuccess: 1: Successful build after gcc: 7 commits discards 0610fe7263 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards da3f3aa9d6 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bbc11f4a1a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e75afee7c7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 3698d80af8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0937ec848d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ec9344bec5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 129ea9a26c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a05212822a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1083841824 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a29596bcb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 90b77665ce 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79a0fb3b02 44: onsuccess: 1: Successful build after linux: 34 commits discards 47db9b9662 43: onsuccess: 1: Successful build after gcc: 2 commits discards e5c618844a 42: onsuccess: 1: Successful build after baseline build: no [...] discards 9e6246f5a1 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5fb21eca5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b930b2afb3 39: onsuccess: 1: Successful build after gcc: 2 commits discards b4f5d81d70 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ae66a5e6c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d26afd014e 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c52e1cab72 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 10c115c98a 34: onsuccess: 1: Successful build after gcc: 3 commits discards 6675b5edee 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ffbe4a2c32 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 9f1ae54a26 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 00456d2217 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 3d157d49be 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad3caf4037 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 410b227e87 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 394268c90b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7a863b7269 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0ee43e11bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2be69d981 34: onsuccess: 1: Successful build after gcc: 3 commits new d30516ef0c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0eacda666f 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d2749e0e0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 092a8d59f9 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9bf61470f 39: onsuccess: 1: Successful build after gcc: 2 commits new 3588de45bc 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0fd014a920 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32ddef2b62 42: onsuccess: 1: Successful build after baseline build: no [...] new 2b05f0c2a5 43: onsuccess: 1: Successful build after gcc: 2 commits new 193c50b5ab 44: onsuccess: 1: Successful build after linux: 34 commits new 3eb48879c6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e07301b0c7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 818ef28b34 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7da76ac15 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b41786864f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 05b547f523 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc08955d4b 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d42c7e5879 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 789e1d5906 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5c85427cac 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 79a1ebd7f3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 024417f60e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebcef19bfc 57: onsuccess: 1: Successful build after gcc: 7 commits new f7b3f02bf7 58: onsuccess: 1: Successful build after binutils: 2 commits new 083fcb7623 59: onsuccess: 1: Successful build after glibc: 2 commits new aacc4e5ae6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b8a7a25760 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c229702f1b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1c9631906c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7a6dc9008 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c6e937f529 65: onsuccess: 1: Successful build after gcc: 4 commits new 6cb0a62fd4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53b4629172 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae56273fe4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fcb355a8e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new e394e875b6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new b2910842b1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 07a7ba7a56 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50fc9d3711 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0905b09dd1 74: onsuccess: 1: Successful build after linux: 44 commits new 03c1389e21 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 60a0431366 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new fb1a281379 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f0bf57047 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fdb33a2186 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 5d2d8edb39 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 6f664ea9f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2daae6b96d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 2677feccab 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e508c0d157 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 0e5fd0c817 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 8c09d960fa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 0c55d6f243 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f0078f3026 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 35af870548 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 273cdf6382 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9a3b5430cd 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7b4dfaf1f8 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 4d3fe9fe4b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 557a183705 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ec98b8653a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new df28a73a4e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 2cc69b080e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new db7c516e4a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new c6c0e8cd5c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4811a72de1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new cffbadc61a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ae231a65f3 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4b2cb79166 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 0e154df4f1 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1ec1f55daa 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8a6b446bf7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new dec8e033e1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 0d5045e104 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new fb83898960 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 84bf42db5e 110: onsuccess: #1703: 1: Success after gcc: 6 commits new e7b7493690 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 7e3adfbcb9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 23e85aff34 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new d65c66311a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 21c52ad36c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new b849b2f44e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 1e656048fc 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a83ddbae52 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 8aa951a37e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 1044c1a0e5 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 72cca13661 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ff50a187d3 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new ad7047889d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 6d0dc37751 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 074ae5a59d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 2da93c514b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4b4c9b7ce8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6697c9623a 128: onsuccess: #1723: 1: Success after linux: 12 commits new 1df35921e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new ecafc414dd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 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 (37db4a2a63) \ 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 1668 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29792 -> 29904 bytes 04-build_abe-stage1/console.log.xz | Bin 90704 -> 91260 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8956 bytes 07-build_abe-glibc/console.log.xz | Bin 233916 -> 234196 bytes 08-build_abe-stage2/console.log.xz | Bin 223848 -> 224268 bytes 09-build_abe-gdb/console.log.xz | Bin 37096 -> 37136 bytes 10-build_abe-qemu/console.log.xz | Bin 31132 -> 31040 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2888 bytes 13-check_regression/console.log.xz | Bin 5492 -> 6924 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 | 25 +- 13-check_regression/results.compare2 | 263 +++- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 - sumfiles/g++.log.xz | Bin 2657752 -> 2659916 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2230424 -> 2213044 bytes sumfiles/gcc.sum | 1986 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888060 -> 882136 bytes sumfiles/gfortran.sum | 234 +++- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201140 -> 201260 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429208 -> 426372 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 1598 insertions(+), 1195 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