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 8137b6f327 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards ae9812ca57 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 631b24b5dc 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 9a7b823c1a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 76532c662e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards c0def47d20 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards b0f4a3d321 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards de3103bf83 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards a2a9864319 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 37ba7fed54 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 647ee7e200 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 785c74633b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 460d175bcc 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 7a996415c3 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 5e5eec0567 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards b369ed77ae 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 7fdb73e3ab 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 8de14d13ff 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards e075de8774 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards f58cba90cb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards bead610f8d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards bd3bc27ee2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards cd439b3897 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 8332d34a21 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards c1e4fc8010 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards e0c7bc2ea7 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards f384185dfc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 8190c9a461 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 5dc8e6ef37 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards e7c7f098d4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b8de0db5d5 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards bfaea73764 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 329bd39db3 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b6194a10b3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 0e9916d340 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ca848a71eb 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 2ca5e50566 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards dcb65185ca 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2aeb5c7de4 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 898ab7d27c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 1c5867f07c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6432dde9f9 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 4572c6524e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 071a777f2f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards af538db943 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 35a702499c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards c188093154 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 4bd248615d 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 5065b8bbcc 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 7c6e10c67c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards bcb6fcad40 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 8abe7f1161 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 2be41df45a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 8242806ab1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 31f1b4f15f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 842fdecb1e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 6b28f24b5a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 53585de4f5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 24a3f85f02 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards e857659642 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 43ca4f163a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards afe8279768 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6bccb3ae0f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 13878c2740 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 9b7b4c3365 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 376834c8ed 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards c715e4aaee 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards a5be2b251f 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 727a7e317e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c021adfef1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 32359849cc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 5099f3c8fc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 0e3d8b7ca1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 1f83c51b82 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 85e6e0a0d6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 0fb7e85f93 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 050a821d23 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 92d8959c04 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 01e5e38865 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b3b8d483d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards bfd306470d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fe29b25800 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 4db0776e68 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 25972003ba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards c357521399 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 9a8a491692 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ab892e2449 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 03284eb26a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 669d35aab3 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 58312ac168 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 20e6017871 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7a97d4847f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0342d908bd 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0133d9adbf 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b65780ff29 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80249ac8b2 74: onsuccess: 1: Successful build after linux: 44 commits discards 46464c489d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f097abeebe 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2dce08d5d6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards ecfd1ac11e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 226d3676b6 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new d881a1a4de 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new ee7eee072a 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 6dd9925856 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new df03267033 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 742716f8f8 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5c2d629dda 74: onsuccess: 1: Successful build after linux: 44 commits new 5176d55e26 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ff239a90b 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 729fa7e6f7 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7bdb4d47b0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 74a6082763 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 036d47bb85 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a2810c343e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new e88aeddad6 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 9dd2fd7ac4 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 607d534205 84: onsuccess: 1: Success after gcc/glibc: 9 commits new a94c072b28 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 70df3f47c5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 4f3837b9ec 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 7c802303b8 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 453ffc7f31 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3225db095a 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a16ec1f9f5 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 2c414ad820 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 958bb21c1d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 538291e92f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 92f15a6442 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new acdec19ff5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 2f95420a7a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 642cdb1e23 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new c2d31752a9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 9d6a0775a6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new d1bd46388e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 565fa77325 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 09e373775a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new b8ad3673e1 104: onsuccess: #1697: 1: Success after gcc: 4 commits new fd6a4b9e71 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new ed10149d64 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 69cf712136 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 857df69a61 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 53e7028c2d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3f7ed7cbcb 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 8f94d8ac9c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new adab2221b5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new d29ed8ef52 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 6bb093d54e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 0eba20908c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new a7d58f2332 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 7202f15589 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new caa6aad7ef 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 48c92326ca 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 8d589dee80 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 51ff909c2d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new e3f8ed8b30 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 516495b73e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new d3aea42fd4 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new f8001fdf47 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 7f1698c806 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 8ede979455 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7f3fca22c8 128: onsuccess: #1723: 1: Success after linux: 12 commits new e4edf976a6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new fb0d671ad3 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 787eea4c60 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 0cd2d329de 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 59ad04d915 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 496e982184 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 4fe03acc0e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new a2a3058327 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 47a85dc888 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 90b235c904 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new fb1c355d7f 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 1b0fbc656b 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 53f3b25745 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 270c0f53f4 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 2da2bedc07 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 32a05a500a 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 69f8dc2b40 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 2d0e3a0f51 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 91b88500cd 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new cc9a776d3f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 68be7a05b1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 09d01fdc7f 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new deac3b8cbf 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new f793f34367 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 3e268b3f97 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 4ec8ea61d8 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new e2f9a3ec3c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 8c068b5f09 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 34aa551492 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new aad7977295 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 754b98ab5b 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new d25bd64fc2 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 2fc1439a40 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new fe796bbbee 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 45947666dc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new dda1399c7e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 837ab0ab9d 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 7e3aec2b21 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new d0505f6236 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 9405bc67f9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new d91177fa53 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new afb7f6f254 170: onsuccess: #1771: 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 (8137b6f327) \ 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 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30456 -> 29992 bytes 04-build_abe-stage1/console.log.xz | Bin 91028 -> 90804 bytes 06-build_abe-linux/console.log.xz | Bin 11260 -> 9464 bytes 07-build_abe-glibc/console.log.xz | Bin 233956 -> 233872 bytes 08-build_abe-stage2/console.log.xz | Bin 225252 -> 223668 bytes 09-build_abe-gdb/console.log.xz | Bin 37660 -> 37312 bytes 10-build_abe-qemu/console.log.xz | Bin 30888 -> 30900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2760 -> 2436 bytes 13-check_regression/console.log.xz | Bin 7268 -> 6508 bytes 13-check_regression/results.compare2 | 285 +---- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2691960 -> 2656676 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2202304 -> 2235312 bytes sumfiles/gcc.sum | 1950 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 885164 -> 891028 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201472 -> 201504 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427180 -> 425220 bytes sumfiles/libstdc++.sum | 6 +- 38 files changed, 1065 insertions(+), 1316 deletions(-)