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 1155375e33 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards d84842ffb2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 8e9f122d9f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 0ef74d37f1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 1fff1edcca 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 86be48dfd6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 5e8355e07a 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 6384e614e1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 90326e0df3 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 55cd045042 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 735cf761b8 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 4ede5ad5bb 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 5fa1ad7db8 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 3f808193c3 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards cce3957603 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 72ca984f87 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 8ee903730c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards d01de6b8ef 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards d2d027dfdf 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards a79f42a46e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 761cce069e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards b70e8c90ba 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 72a36a73d5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ad0d2562dc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f89ae8bff3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards a95961bea2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b5fd8ce0dd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 957f067ba5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards dfbe87c3fe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 2b3ab2ccac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3f07325dd2 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards b4d07fc103 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 115e6368ab 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 46bff33771 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 511613434d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards b0f610cc28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards fa52745e8c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards b4faf1b0df 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 9c35157fe6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards bfb0cda74f 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards a17a27f051 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 0cb3043888 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 9446f87e4d 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 1e7abf4226 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 9fa73e78d9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 0522d50fde 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 808036a27c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 6ffc90b82b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards e00333a2fa 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards d9f51fe9e2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 1a0693d7c9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 587803dc31 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards fdcd3375d6 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 8dd6e783ec 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 837583a321 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 80fd37c361 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards f59d1ca4a9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards d007fadd65 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 406e4fbbba 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards a46331671e 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 249a195244 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 947cac56d9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e15cfe5826 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 495d84916a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 024ca2c347 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 54b24ebdd2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 03d2789538 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b08a957d18 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards bcc28740cc 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 16966c8eb9 74: onsuccess: 1: Successful build after linux: 44 commits discards c69d9d4217 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ad937ef61f 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c1e2c17f91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 80006d5437 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 2e6ed8f72d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 718023b7fa 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f5d34ea6f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 53b58771d9 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 433d8537f4 65: onsuccess: 1: Successful build after gcc: 4 commits discards 3a3f0847ad 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 26892c2857 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 756f49d247 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards c312dc9e78 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 51bf2c82b6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9ec2520582 59: onsuccess: 1: Successful build after glibc: 2 commits discards f36302c6df 58: onsuccess: 1: Successful build after binutils: 2 commits discards 785f320823 57: onsuccess: 1: Successful build after gcc: 7 commits discards eefba6ef73 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 356ca6c51a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2d36feb04 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 64b0125917 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 97d780c50e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards d23c0b0746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c4782dc76a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59c476ec46 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a9e88f0e72 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards dd9f31d122 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 842a080e62 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards b6e0c900cf 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 31b783c80a 44: onsuccess: 1: Successful build after linux: 34 commits discards 874a1325c1 43: onsuccess: 1: Successful build after gcc: 2 commits new 686def63af 43: onsuccess: 1: Successful build after gcc: 2 commits new d2d281ad8b 44: onsuccess: 1: Successful build after linux: 34 commits new 2e71989c2b 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 554f22c21b 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 0220b075c2 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b35490f38b 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 0ba2e9e9ec 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 694635dd55 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 76f85c34a9 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 544e84aabe 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 5e2f7eacd0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new b72b8a190c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 943dae5422 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 63acfad8e2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f26877a37 57: onsuccess: 1: Successful build after gcc: 7 commits new 89cfa01365 58: onsuccess: 1: Successful build after binutils: 2 commits new 0cedca4746 59: onsuccess: 1: Successful build after glibc: 2 commits new b0a4cf828c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 9d0884c8fa 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new f0f5b3b4c8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 91df097aa8 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 507147954a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2f7cb3b3ef 65: onsuccess: 1: Successful build after gcc: 4 commits new f63fb509da 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 60a24b5f50 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 041a5ce933 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 42892ec333 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 90433f65c6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new e3486a7870 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 98fd3995e7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9349784b2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 92128c097f 74: onsuccess: 1: Successful build after linux: 44 commits new 9b340b71e9 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d7151ff46f 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 2020e67970 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 373f42b739 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new be06f36853 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 03c0446036 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 5e28550051 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 12a022585a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a1c6a74bbd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 215f852926 84: onsuccess: 1: Success after gcc/glibc: 9 commits new d89313c804 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 53151de7f2 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 72e536a5e6 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new a0fa58a3d4 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 0c43d5dc4c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 78563de238 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f41b4ee6bc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c109b84786 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 8a251fcaed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new b661267529 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 0ec5dda0d4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new a708f21d00 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new a54dbe5655 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 0fe6f1395d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 71d9cb2fb1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new c5619311d7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new fbd01253f9 101: onsuccess: #1693: 1: Success after glibc: 14 commits new faffd6ae1a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 88ee46ad07 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 5e8f5447f0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f77a9b92ad 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 63b0fbbfd9 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 98eb215c0a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new e11aeb06fe 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new c315f8eac1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a7855cdba0 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3c88a53a57 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new b6061acb2c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 41126571a4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 6d85b2fc45 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new d47cdf8ccd 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 5484c39d43 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b466195bda 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 9bbe76e978 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 6e2493710e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new e24f858d82 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 54a61dbdbe 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 0579d8a661 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new aebdf38b4d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 4a14d4b46d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 0f9d9b1723 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4a37007b09 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 334d891da9 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 9b0b1126ab 128: onsuccess: #1723: 1: Success after linux: 12 commits new 5ca3ee394e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 866dbb0d68 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 671003c5c2 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 0e23b05463 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 0da1a44124 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new ca4d6a6510 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 8ed8d32624 135: onsuccess: #1733: 1: Success after binutils: 5 commits new b9632f663a 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 158071ea41 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 39f72b6698 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 80aa576bab 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 9d218c2a3d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 3b5f35ecd7 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new bc891b5142 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 463c766e66 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 1139d8ac3b 144: onsuccess: #1743: 1: Success after glibc: 2 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 (1155375e33) \ 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 1728 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 29876 -> 30072 bytes 04-build_abe-stage1/console.log.xz | Bin 90612 -> 90416 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 234572 -> 233824 bytes 08-build_abe-stage2/console.log.xz | Bin 222608 -> 223580 bytes 09-build_abe-gdb/console.log.xz | Bin 37240 -> 37208 bytes 10-build_abe-qemu/console.log.xz | Bin 30776 -> 31400 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2444 bytes 13-check_regression/console.log.xz | Bin 6944 -> 5344 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 | 26 +- 13-check_regression/results.compare2 | 69 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 26 - sumfiles/g++.log.xz | Bin 2651552 -> 2656996 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2219996 -> 2191892 bytes sumfiles/gcc.sum | 2214 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882784 -> 881792 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201320 -> 201280 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423668 -> 427888 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1230 insertions(+), 1324 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