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 a882f4e730 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 58774adb1f 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards fc5fc48993 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 48d55df16a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards e034c5f96b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards f6d7e2e8a2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 41139d194c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards eb2b668a42 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 54efb27810 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 889681194d 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 6633c37870 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards fce064f1db 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards c439c4a94c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards b9a391e3a7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 93ee7abe0f 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 0c27b588d9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 111319437a 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 7ebf9d5804 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards f4cbabb336 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 4708f044b9 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 75b55f826f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 4db58376ea 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2549c671f5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a36c47fb82 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 02633937aa 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards ba372532b3 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 4bbb3f79a1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a51d539072 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ca65df3b26 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 4c78fc981d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 8fce5a14c7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7f98c1bfa7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 6de80566d0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards b7653d7340 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f339e3633c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 5414124dc7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1678eb05fd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 02bd0b232e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards ecef0c6c2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards da6660e8a1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 8ecda5ecfa 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 19dab87b43 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards abdaea57f8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 037e6acccb 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards a2d0a8b2f5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards ee67e17f28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 238d385e60 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards d6f4f738d1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 0b919f121c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 886c27a001 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6dbb07463d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 14da978944 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 8e6e936e42 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f698ec0705 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 6c9117c315 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards f106b3cd1d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards fae1611214 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 88683acb7d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a56fe2dfd8 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards ddde8d07d5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 13dadffb3d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b6f1b90a08 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 8fa2fe3666 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 54a74a99d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 644d99e5cf 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 25d3bffd77 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e08367dd1a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 698cd6dde8 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d4daa9a413 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards b3d6bb1a3d 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 6e936d87cd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards d62c49152e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 23e897cf8b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c3a01f6120 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 77b85d12d0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fa8c8ae89f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d66e1c4d9 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2fb8c62346 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b96f696f82 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a1a47f8568 74: onsuccess: 1: Successful build after linux: 44 commits discards 9627f29912 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards de43a37264 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd5af60c44 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 46d80d9643 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 30d11270a7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 51156f628e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0ffa6796b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a242ea9424 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 45dcfc6a49 65: onsuccess: 1: Successful build after gcc: 4 commits discards 7f682b3b4c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d57abef12b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9c2019cf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards bbcb2ad845 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8984294400 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 39dba10390 59: onsuccess: 1: Successful build after glibc: 2 commits discards 57d05c5b00 58: onsuccess: 1: Successful build after binutils: 2 commits discards a355157ce4 57: onsuccess: 1: Successful build after gcc: 7 commits discards 5c6f11b0c2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9d5b309c6d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb8e007954 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 8ba4b2067a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 18179e6695 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a45dedba1c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 8fcf491a1c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37c3ea4edb 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad3a9801b1 57: onsuccess: 1: Successful build after gcc: 7 commits new 0874c56cb1 58: onsuccess: 1: Successful build after binutils: 2 commits new 5120701f95 59: onsuccess: 1: Successful build after glibc: 2 commits new ccd590fb0b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 18a606131e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 419b3979cb 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 46f21e916f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d789aa4f6b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 553521013b 65: onsuccess: 1: Successful build after gcc: 4 commits new 877d0960b6 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a465020cbc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 992f51b0ba 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 547233f33a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new b171334fb3 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 24ea50fb85 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 21091188d3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d18e092599 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 152d9d9c66 74: onsuccess: 1: Successful build after linux: 44 commits new f8115df2ff 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a2b05392fc 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7d906ec025 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac4902beca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 869e43cf97 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6bde732342 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 7ed49d5088 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ef667b98c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new acfcfccd6b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 7240ad26ad 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 22c8849d64 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 698b16abd6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d7f40d2ffe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new a89e17ebba 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ae85b4b02f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 20006fb903 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9a50fc47c4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 417841b2f0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 96bf0c9a77 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 86cebe779f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 5c6b895a28 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new e5eb880b3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new db9a4126df 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new f18d52e2db 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 855e449b99 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new e294f9b8db 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 572b4166a4 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 5b0356bcfe 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 78d8007739 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 7940fea132 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 731d4d2da1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a345543f24 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new b078445d22 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ae312d931c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 5048094191 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 62d2a3628a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 1b5152c93e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a0ab6a3ad0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new cd9cfc7051 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new ad21ac19a6 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 0257429e1e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4a97e580f7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ce3d5ca4ec 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new c0a3db4c85 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 18aae24cec 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 7097a4cae0 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 0df8f7472c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 0b05186668 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new bc0d1b5253 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new f73aec0706 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new e3693f1d49 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 0235de1faf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 32c5636dc5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 9310bfa850 128: onsuccess: #1723: 1: Success after linux: 12 commits new d761ce5e29 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a5ba3cd9d1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 790ab8fe09 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a99f3a8bb3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 3ba26c6a09 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 3b6b94d805 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 8c7c1e6a95 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 9cbeb95bc2 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new fa886ceab0 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 485a62a95d 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new d982bc4ffc 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 07530500c9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new ed3c943398 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 49c1b608d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 2dfbc043e5 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 26b7b9040b 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b8fcb121ff 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 4dd8f075bc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 5dce5766a3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new bd764c03b5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 9dad1db68e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new d8f0723963 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 7ee5182049 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 20a59418bf 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new d9df8af538 153: onsuccess: #1754: 1: Success after gcc: 2 commits new e983bf3e9c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 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 (a882f4e730) \ 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 1676 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29860 -> 30000 bytes 04-build_abe-stage1/console.log.xz | Bin 90276 -> 90828 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8920 bytes 07-build_abe-glibc/console.log.xz | Bin 233840 -> 234904 bytes 08-build_abe-stage2/console.log.xz | Bin 224272 -> 224020 bytes 09-build_abe-gdb/console.log.xz | Bin 36944 -> 37184 bytes 10-build_abe-qemu/console.log.xz | Bin 31776 -> 31400 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2816 -> 2736 bytes 13-check_regression/console.log.xz | Bin 5392 -> 5916 bytes 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 57 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2668044 -> 2650704 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2231760 -> 2201416 bytes sumfiles/gcc.sum | 2606 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 890340 -> 893568 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201416 -> 201520 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432600 -> 427764 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 1541 insertions(+), 1499 deletions(-)