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 5e5e8845ad 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 95def9f5a4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 4fae8108ff 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 20673712b5 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards fb152158e9 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards aefc6fba2b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards b8284aa6ae 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 015c747747 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 7243e1d4b6 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards d22bfe8300 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 6cddd45359 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 6addbf367c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3c365629a6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 23f13027a7 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 63a3637b17 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards adc35eeb4e 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards cd298989ad 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 2c1b4204dc 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards c5799dc35e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 732e72b81c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 1e33ea682e 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards d78e7790eb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards ec1c17bf4e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 62d0de1cab 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 4d9ae1e828 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards a96f220230 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f5741aa80d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards fcf6bca9b3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards be089a9129 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards f4c4e9dd89 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards ab9ce46273 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 942d2db143 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 9b0feb33e2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards a932fc982b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 27ad7e64f8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 6fe2337800 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7c99022ea9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 3950c1ff57 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 33089542a7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 1cb7667aa1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 21be0bc231 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 2ccd73db52 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 4157a52564 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards b30ce978d5 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 83af8f7516 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 771f9e1939 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards e6338fed4e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 6a1a1fcd40 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards a75d12fe00 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 0a19108899 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards af01753e7a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 5319de99f6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5c72ab6b7f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4698e64e49 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 5e7b070e41 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 2376a5ed34 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 23bb51504f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f4f249b027 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 3763b9cf72 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 086bc5cb8c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards bf5cf211c0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 17548048bb 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards c903c87c76 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2c4130bb07 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards dcc466ee9b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fee18781e7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 90d92a77f7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9ef1a81ba 74: onsuccess: 1: Successful build after linux: 44 commits discards 8b98191e1f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9aeffbda60 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 359803b048 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards e26e9fc4b1 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards b989ab86cf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards e8c85f7e1b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 83029860bc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c16bff178 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c8b7e4811a 65: onsuccess: 1: Successful build after gcc: 4 commits discards 876bb81a01 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91c4a82e02 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d179e1a78 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 347dca9737 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e5f719e7e4 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b458c9a610 59: onsuccess: 1: Successful build after glibc: 2 commits discards fc4f003109 58: onsuccess: 1: Successful build after binutils: 2 commits discards 258e9c6fe9 57: onsuccess: 1: Successful build after gcc: 7 commits discards 239133e00f 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2984e5f192 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0755c17e6 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e1caef93e1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 03cae93e16 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 70d9a5b1b3 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cb9bb1b7d2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0e0dd5d2f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0c541d59a9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards f053ecfe21 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8a788cf42 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards e4b3d6eb87 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b8e0fd026 44: onsuccess: 1: Successful build after linux: 34 commits discards e090706c71 43: onsuccess: 1: Successful build after gcc: 2 commits discards 77629f3343 42: onsuccess: 1: Successful build after baseline build: no [...] discards da47c42ed0 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b27f1b336a 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc50c36ae1 42: onsuccess: 1: Successful build after baseline build: no [...] new 567fb6ff7b 43: onsuccess: 1: Successful build after gcc: 2 commits new 663aef4434 44: onsuccess: 1: Successful build after linux: 34 commits new bbd198732e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab2d952eb4 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 6dde03fab9 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9fff1e098 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 4e2b460e45 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b456ff6aa9 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b84b3f987d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 64afe620f9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0f25c9255b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 1604865fde 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new d68343c55a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c74da04346 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b0209b138 57: onsuccess: 1: Successful build after gcc: 7 commits new 5535a1356e 58: onsuccess: 1: Successful build after binutils: 2 commits new 953ca06727 59: onsuccess: 1: Successful build after glibc: 2 commits new b1ca9097af 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8160f0fafe 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new cb61a597cc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new a20d93404a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9e8508788 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e010542225 65: onsuccess: 1: Successful build after gcc: 4 commits new e4c6ccba72 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c46afbca4c 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1c3c77ec31 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new baea4d3d82 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 2b9ef3a981 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 9da6ac3a06 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 8714afe615 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a14c2ab260 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2a5849fd9e 74: onsuccess: 1: Successful build after linux: 44 commits new a7122fb4f4 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 187336acd6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7d81171c45 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3baf148d7 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 00aeef5344 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b60159821a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 04f35fba41 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 575e3f96f3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ebcefb5e88 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6a5b8f9cfc 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 9d9451fed4 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new d03121965c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 790e37c952 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2e2a473757 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new d4259c7aec 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fcb32117c2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 00200af208 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 96240c3b6a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 4ea5c0f1f0 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 1feb64d7c5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new cdd5f384ed 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 7857103ee2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new a45677a7c4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 75aacdd156 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 5de9119f42 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new ca46fbd813 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 01f3f38dd8 101: onsuccess: #1693: 1: Success after glibc: 14 commits new af7cf1074a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new e9560cf21c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 5270923923 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 0d56c0762b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 187a5753f0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7e6518c219 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new c08fdd475a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 5e4ab5b436 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 810e77831f 110: onsuccess: #1703: 1: Success after gcc: 6 commits new d380307723 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 36130c6444 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new f0851fcc71 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 89113aec95 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new d56767c7ee 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 2e7d85f6c0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 093869abaa 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 1e2992e38d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 0872ae4fe5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 49b212fa8a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 43e56ed6f4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 3ecd6a7d90 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 26509ee736 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 197cbb1036 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3c2254bae8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4f70eba9e2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e748fdc42f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7230689084 128: onsuccess: #1723: 1: Success after linux: 12 commits new 3a4cb24a70 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new d67752466c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 09beba1368 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 5a04795456 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 14824d42a9 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c7a59c9144 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 71c6ed8f63 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 959755dc19 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 18448efd20 137: onsuccess: #1736: 1: Success after gcc: 5 commits new c3596228bc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new b7367844d9 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 698d4c14c1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8d10f75a4b 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 8bc9f4b2a0 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/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 (5e5e8845ad) \ 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 1744 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30624 -> 30144 bytes 04-build_abe-stage1/console.log.xz | Bin 91548 -> 91152 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9304 -> 9256 bytes 07-build_abe-glibc/console.log.xz | Bin 234068 -> 234364 bytes 08-build_abe-stage2/console.log.xz | Bin 226196 -> 223344 bytes 09-build_abe-gdb/console.log.xz | Bin 37420 -> 37556 bytes 10-build_abe-qemu/console.log.xz | Bin 31784 -> 31096 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2744 bytes 13-check_regression/console.log.xz | Bin 6692 -> 6036 bytes 13-check_regression/mail-body.txt | 46 - 13-check_regression/results.compare | 70 +- 13-check_regression/results.compare2 | 129 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2687132 -> 2667716 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 2205300 -> 2226364 bytes sumfiles/gcc.sum | 2883 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 884360 -> 881588 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201252 -> 201100 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 419324 -> 422680 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1619 insertions(+), 1865 deletions(-)