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-aarch64 in repository toolchain/ci/base-artifacts.

discards c442def5bd 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 3fe671781a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 2fef1fc7a4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 682b782901 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 9b6fa3a6cf 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 323826ccef 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 4b0c758fe8 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 8a1754f096 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards d230d59e0d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards add3ea7f3b 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 4fb38c0b23 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 2fc3dc0461 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards cc959c885c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 573680e9b0 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 975b621ad5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards c722363c99 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 45b31cc70e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 6ed8075f06 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 1fa089f82d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards c637b56341 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards d9df3583a8 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6a4f88fd58 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3ce7c1eb3c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 322da15a62 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9b28626055 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 3f88e98f8d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 5a2f0bd63c 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 39a26278ae 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 862e388aff 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards c0217f4cd7 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 090ee3e0d8 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 4aef93afa1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards f07b8dc491 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 68205b758a 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 7f3d8ded6f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards ab039daf81 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 787a1e738e 124: onsuccess: #2159: 1: Success after linux: 23 commits discards fe1f5aa3a2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards d3b0ce1ce6 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 6f91294897 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 920326fa15 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 96f7962da2 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards e7b6a23e40 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 978dd35d71 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 7181622db5 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards b75992bafa 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 956d858e4b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 84c74ac3b3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4e6a8f14bb 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards e2e2290d30 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards afbee1974e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards a779b9688e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3fd9b52003 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 238bd162e7 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0279553308 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 39e2cb6ccd 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 65d5b4a91b 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards f58f41871b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c0b47de672 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards b6f80185fd 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards da8db58a06 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 2d50f7734d 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 3a0bac66e2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 7600bff5cd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards f20f278116 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 6d998cba59 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards f487a792c8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 70cc0bb7fa 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards b57f3e2bd3 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3962e00529 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 55e3a19a54 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards a8365efa7d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4a7c87f2a2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards aa832e433f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards d442ea2c59 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 89a6a009de 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 981cdfd2d0 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 79fedd0efa 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 4689f1ce5b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 622c670e5d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 9706a65791 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8c1c2e1610 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d2eae8b86f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards a2859fa0f7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 0e1651feaf 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 816673056e 75: onsuccess: 1: Successful build after linux: 44 commits discards 4c90bcec29 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8c13f87155 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cc37705cd3 72: onsuccess: 1: Successful build after linux: 12 commits discards be5513f361 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards de2707e5f1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 348273cff9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e508011355 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 06a2f3db43 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 398de58161 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards f276fc61f0 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 97be036919 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a819207dfc 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards eed9ab1673 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 27be399276 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 37a8f6d7cd 60: onsuccess: 1: Successful build after glibc: 2 commits new 88e1ccd907 60: onsuccess: 1: Successful build after glibc: 2 commits new d7cc25685f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ed5a03dbb1 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 9b2793d8e8 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new f758833964 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 798562e08d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4a7ff5ea78 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 9377b2520e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new cba03fe747 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 643aeb00bb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new aa005e2f7f 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0e9460140c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 5124322d32 72: onsuccess: 1: Successful build after linux: 12 commits new b258056614 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b40fa33f81 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f2bb02755c 75: onsuccess: 1: Successful build after linux: 44 commits new 3afb87c3d8 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a378427a3 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new fd1ee418a7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new beb3820d2e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b84aace20c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9fc572bb9d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 2cbfce75ad 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 748c941fbd 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 4175e92d4e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3ab4dabe03 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new aa2cb47570 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new dc3d36a4a8 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new da54384812 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 51cce2d23e 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 8b10bca901 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new bf7f9673e4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 78d9d3d0e2 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 007980e550 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 9f5649adbe 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new e0d40bd5f8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 4f78b4054e 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new dd7ebd4c26 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 3e70405cf5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 41957ac0f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 7a3b54387b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new aacf9ed127 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 6d93fb465f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 85233ae10a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 5bc0bf5bbc 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 4380ca8291 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new a8d7270a26 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 5263df3c13 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new c76ae132e5 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5a68dcbe73 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 09c6da24d3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new cda02b0319 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new e6be03c3cc 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 68baa6fc42 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 5283b6b757 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new e6f94ad21f 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new a50c535052 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 732e02c413 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 60bca1c67f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 57c5baff4b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3b3b1d1929 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new ea094c39f6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a9eb3cb786 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new c5be307b4f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c13a1f86b8 124: onsuccess: #2159: 1: Success after linux: 23 commits new 0163e05bed 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 77fc9a899c 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new da75d4e3cf 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 659e999505 128: onsuccess: #2163: 1: Success after linux: 23 commits new a4f5b8db54 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 21e9f9996d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 5126ab4a47 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 53c8da7675 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new f24112118b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 17e900ee6b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 8eb01bd2c2 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 021c4a029e 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 9f49f4c6b1 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 647966ffcf 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 2b8249a732 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new ec5ffbfae0 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 49d3a10e83 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 9765cdd7bd 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 9b8581b3d9 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 5968df5418 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 09e7c53dce 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new bd7a8f6ee5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 6246007d36 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new df659b9c00 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new ed0f65e2f8 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e9eea594e9 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 5b65a8f44f 151: onsuccess: #2186: 1: Success after gcc: 2 commits new cf09d9bd2a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 61d23cddcf 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 8fb969cc2d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 55da16576d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f951a8bde5 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new c468e24706 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new f4493dbf46 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3556fcd221 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 40fcca45b8 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 286763cb3f 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...]

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 (c442def5bd) \ 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 1720 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30148 -> 30272 bytes 04-build_abe-stage1/console.log.xz | Bin 72356 -> 73696 bytes 06-build_abe-linux/console.log.xz | Bin 9996 -> 9132 bytes 07-build_abe-glibc/console.log.xz | Bin 239960 -> 239780 bytes 08-build_abe-stage2/console.log.xz | Bin 203060 -> 204460 bytes 09-build_abe-gdb/console.log.xz | Bin 37480 -> 37440 bytes 10-build_abe-qemu/console.log.xz | Bin 32160 -> 31920 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2608 -> 3968 bytes 13-check_regression/console.log.xz | Bin 16404 -> 7180 bytes 13-check_regression/mail-body.txt | 101 - 13-check_regression/results.compare | 51 +- 13-check_regression/results.compare2 | 2555 ++----------------- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 3410472 -> 3414740 bytes sumfiles/g++.sum | 191 +- sumfiles/gcc.log.xz | Bin 3031732 -> 3028540 bytes sumfiles/gcc.sum | 4536 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1030564 -> 1029576 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202232 -> 202396 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 419844 -> 422936 bytes sumfiles/libstdc++.sum | 8 +- 39 files changed, 2657 insertions(+), 5014 deletions(-)