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 5cc4a42866 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 6d7c51705a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 2020d6b6cc 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 4985c945c9 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards ee2514b636 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 2b6b27dc82 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards b84b64af94 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 16d2ff07d3 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 74c0282f80 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 6138182850 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards ce60da1416 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 8b2129e649 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards d5630a4e42 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 2232a341a4 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 5b12d4888e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 893b97fbe4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 51a59a295e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards f301720494 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards d4acab8067 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 1309d1a375 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 2b253f3dfe 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 3edea7447f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 648462a680 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards f67ca43360 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards a85c63fedd 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards ee35eff544 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 447706bb15 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards cd8dac096e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 532a135fd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 1028bd6fde 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 0163ef994f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 57befabf0b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c1ba9e8e3c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 3a8697c41b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 6db89bd44d 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 3d56a53bed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 6c65bad239 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 51404cadc4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards f3222f7de9 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 86d31e7626 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 18aabd7bb3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 1cc5f85ac7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards a824549f32 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 52b194e4d9 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 04c8bb4449 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards e7ab4a1ddb 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards b5f2094f72 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5763dfda30 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c7ed24386b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards c5c93f6a08 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 45592c10b6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 838a4382ca 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f5f320ab25 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 8a5caba931 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fac00beb8f 74: onsuccess: 1: Successful build after linux: 44 commits discards 2a51c77ecd 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ecf2b4b412 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 02bfb76451 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5a410a7f25 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 2e8819bfa0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards c8cb704576 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 557c0753d9 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a2351a207c 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e0fb252f04 65: onsuccess: 1: Successful build after gcc: 4 commits discards 27e0d7e79f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8ccff6dfa9 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 28d5e7898c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 14bd26d71c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 03e95fcc34 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f63db6bc32 59: onsuccess: 1: Successful build after glibc: 2 commits discards 7fc5f373a3 58: onsuccess: 1: Successful build after binutils: 2 commits discards 5e62ac9c32 57: onsuccess: 1: Successful build after gcc: 7 commits discards 06d4020fcf 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 626874885b 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 145563ce54 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards a9ea0d6c23 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 7a20bebe69 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards de7d074047 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 993d707b5b 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be42703e69 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ee8b19e835 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1f60623190 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6799c97025 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 76cbee0612 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6908a8774c 44: onsuccess: 1: Successful build after linux: 34 commits discards 8849e22e87 43: onsuccess: 1: Successful build after gcc: 2 commits discards 760764439d 42: onsuccess: 1: Successful build after baseline build: no [...] discards 5aa9de4d27 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 81ae7f401a 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c1a8b03c4 39: onsuccess: 1: Successful build after gcc: 2 commits discards 740d76c402 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ead2336932 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 030d80f722 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ab5899e228 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4af2f02758 34: onsuccess: 1: Successful build after gcc: 3 commits discards dc03d175ab 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7918fc1fa5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards c9273e486a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 255d2efd67 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 038bcb008b 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ae6872550 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8982155a03 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3d157d49be 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 00456d2217 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 9f1ae54a26 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ffbe4a2c32 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 6675b5edee 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10c115c98a 34: onsuccess: 1: Successful build after gcc: 3 commits new c52e1cab72 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d26afd014e 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ae66a5e6c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b4f5d81d70 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b930b2afb3 39: onsuccess: 1: Successful build after gcc: 2 commits new b5fb21eca5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e6246f5a1 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e5c618844a 42: onsuccess: 1: Successful build after baseline build: no [...] new 47db9b9662 43: onsuccess: 1: Successful build after gcc: 2 commits new 79a0fb3b02 44: onsuccess: 1: Successful build after linux: 34 commits new 90b77665ce 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6a29596bcb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 1083841824 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a05212822a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 129ea9a26c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ec9344bec5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0937ec848d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3698d80af8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e75afee7c7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new bbc11f4a1a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new da3f3aa9d6 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0610fe7263 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 98752c4499 57: onsuccess: 1: Successful build after gcc: 7 commits new d8d51a08c1 58: onsuccess: 1: Successful build after binutils: 2 commits new 338ded01be 59: onsuccess: 1: Successful build after glibc: 2 commits new 15810301a3 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 35903c16ac 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ec1023d93a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 19ff1a2ffe 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9a0dfa4055 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a9f8b8aee1 65: onsuccess: 1: Successful build after gcc: 4 commits new ce64403521 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e1c4b1ab86 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc43c09c2e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a427bd0f34 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new c7727c1b79 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new d1e72b9153 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new c58e923722 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c59076a478 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a626c4e0bc 74: onsuccess: 1: Successful build after linux: 44 commits new 88b0840b30 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3286ee1a9c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7dea4df532 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18b5aea4f5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 23b2c87b74 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2338b2312e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 6634c8db87 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 77ffa7695b 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 79d271f331 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 7f7a5f6c00 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 0ee8253d90 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 35cbd6f0be 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 5fbb2d8f16 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e1dde4c011 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new f07314b4d0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d7a03bdc90 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8436782d4f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 4c731b7f53 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 22b9caf9af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 166f14763a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 56f6717c70 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 85c4fe614f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 27705bee35 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 70b7848663 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new e1b78d3064 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 6ec8e2dd37 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 69c9ab6dd6 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c28eaa24ff 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f27ab951a2 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 59a90c74ea 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f520d1a030 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9b0b6e57d3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 45600e11ed 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 8fa6506b97 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new a30e39b47a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new daa552e0e6 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 6f73568d5c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new dea5ad64f9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 2ba6eafa01 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 21ded787d4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 5e0f2ac750 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 5efced6c89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new e7ffeeeb89 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 2ebb594386 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new b26880c3f5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 0c35115542 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new d0bbb791b6 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 7540ed7896 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 32efe5cb0a 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 0f5af9d551 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new d08238b13c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new cf7cdd3a38 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 525d731af4 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new a03517cd64 128: onsuccess: #1723: 1: Success after linux: 12 commits new 37db4a2a63 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...]
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 (5cc4a42866) \ 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 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30500 -> 29792 bytes 04-build_abe-stage1/console.log.xz | Bin 91540 -> 90704 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 235660 -> 233916 bytes 08-build_abe-stage2/console.log.xz | Bin 224876 -> 223848 bytes 09-build_abe-gdb/console.log.xz | Bin 37648 -> 37096 bytes 10-build_abe-qemu/console.log.xz | Bin 32032 -> 31132 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2592 bytes 13-check_regression/console.log.xz | Bin 5820 -> 5492 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 25 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 26 + sumfiles/g++.log.xz | Bin 2658052 -> 2657752 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2241116 -> 2230424 bytes sumfiles/gcc.sum | 2270 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 885908 -> 888060 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201108 -> 201140 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429572 -> 429208 bytes sumfiles/libstdc++.sum | 20 +- 41 files changed, 1428 insertions(+), 1317 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions