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 11a6acb864 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards ccb31be952 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 3fae5e1ec9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 53364f304a 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 5e2fc0330d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 60926a7f6f 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 22e502d1d5 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards cd217258b2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards ba01608552 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 383b3961de 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 3c33a8d422 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 780cbb3bad 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 2afa7b5b35 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 6096f4593e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards c8da2d8f5a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 28cb8ca259 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 7791e7f5fc 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards b922365cb4 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards b19df5c513 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 899cea9910 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 0da6989d6b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 9f1a9148bb 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 69073bf3f5 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards eaf2d444f5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 4dbf74e179 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 0259bae3cd 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 8d356d823e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 0b3abe612a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 0bebcbe3d3 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards bf1f8dadf8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards d8e97695e0 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 63b58754c3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 87bfe63fe0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards d53919b4a2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 49bcf2b16b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards b5c5530c80 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8419a90bd1 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6dd493a90e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 939d8d35b1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards a57fbaa51a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 7366a21d15 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards e11835e128 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards d9a08227d2 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ac02ba651b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards ffee6f3fdc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 0dea98c2ea 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards c369fa1e37 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 026a6f2351 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards ae606a81f1 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 962f8cf3a0 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b266305685 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f5ff5ebc92 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4c3d4769f9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 1157af0f51 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards c2726ca53e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards aa96468e44 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards b0ab24af11 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 3547d6ea80 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 5205ee1dd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e18048507d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 9e3b924c9a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 0d9f14d77d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards f232784a1c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d6f8afd6d0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2dcd0bc190 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 676430d9aa 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ffb48cad6c 74: onsuccess: 1: Successful build after linux: 44 commits discards cf408bda7a 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 06c78be3e0 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ec1836e1f 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5b9b5840dc 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 61c4dd3867 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards bce4b9acdd 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2d3f05ce2 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3d1654a860 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 20b9dd90be 65: onsuccess: 1: Successful build after gcc: 4 commits discards d7b09ccb7f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 345d390c5c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3c28b20584 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards c01854ba70 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 70fd01f8c0 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1d64d36c4d 59: onsuccess: 1: Successful build after glibc: 2 commits discards 5723c03b9e 58: onsuccess: 1: Successful build after binutils: 2 commits discards 6ede81134d 57: onsuccess: 1: Successful build after gcc: 7 commits discards 87594c0f96 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2d57596b3d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92ea8b779e 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 75894393de 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 69b18c878d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 702c2b4be7 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2dd370379f 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a26103810a 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards afb1de8d40 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 0c9af7dc14 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b2bda828f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards a29484542a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 04272e0d28 44: onsuccess: 1: Successful build after linux: 34 commits discards 067c2e17bd 43: onsuccess: 1: Successful build after gcc: 2 commits discards f11efd137c 42: onsuccess: 1: Successful build after baseline build: no [...] discards b0a6ffba7b 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 85e24cf9ab 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e284b0208d 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da47c42ed0 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 77629f3343 42: onsuccess: 1: Successful build after baseline build: no [...] new e090706c71 43: onsuccess: 1: Successful build after gcc: 2 commits new 5b8e0fd026 44: onsuccess: 1: Successful build after linux: 34 commits new e4b3d6eb87 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8a788cf42 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new f053ecfe21 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0c541d59a9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new f0e0dd5d2f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cb9bb1b7d2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 70d9a5b1b3 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 03cae93e16 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e1caef93e1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f0755c17e6 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2984e5f192 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 239133e00f 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 258e9c6fe9 57: onsuccess: 1: Successful build after gcc: 7 commits new fc4f003109 58: onsuccess: 1: Successful build after binutils: 2 commits new b458c9a610 59: onsuccess: 1: Successful build after glibc: 2 commits new e5f719e7e4 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 347dca9737 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6d179e1a78 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 91c4a82e02 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 876bb81a01 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8b7e4811a 65: onsuccess: 1: Successful build after gcc: 4 commits new 0c16bff178 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 83029860bc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e8c85f7e1b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b989ab86cf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new e26e9fc4b1 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 359803b048 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 9aeffbda60 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8b98191e1f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b9ef1a81ba 74: onsuccess: 1: Successful build after linux: 44 commits new 90d92a77f7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fee18781e7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new dcc466ee9b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2c4130bb07 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c903c87c76 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 17548048bb 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new bf5cf211c0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 086bc5cb8c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3763b9cf72 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new f4f249b027 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 23bb51504f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 2376a5ed34 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 5e7b070e41 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 4698e64e49 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 5c72ab6b7f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 5319de99f6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new af01753e7a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 0a19108899 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new a75d12fe00 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 6a1a1fcd40 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new e6338fed4e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 771f9e1939 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 83af8f7516 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new b30ce978d5 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 4157a52564 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 2ccd73db52 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 21be0bc231 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 1cb7667aa1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 33089542a7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 3950c1ff57 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7c99022ea9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6fe2337800 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 27ad7e64f8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new a932fc982b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 9b0feb33e2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 942d2db143 110: onsuccess: #1703: 1: Success after gcc: 6 commits new ab9ce46273 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new f4c4e9dd89 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new be089a9129 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new fcf6bca9b3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f5741aa80d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new a96f220230 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 4d9ae1e828 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 62d0de1cab 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new ec1c17bf4e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new d78e7790eb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 1e33ea682e 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 732e72b81c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new c5799dc35e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 2c1b4204dc 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new cd298989ad 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new adc35eeb4e 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 63a3637b17 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 23f13027a7 128: onsuccess: #1723: 1: Success after linux: 12 commits new 3c365629a6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 6addbf367c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 6cddd45359 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new d22bfe8300 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 7243e1d4b6 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 015c747747 134: onsuccess: #1730: 1: Success after binutils: 2 commits new b8284aa6ae 135: onsuccess: #1733: 1: Success after binutils: 5 commits new aefc6fba2b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new fb152158e9 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 20673712b5 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 4fae8108ff 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 95def9f5a4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 5e5e8845ad 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 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 (11a6acb864) \ 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 1708 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30436 -> 30624 bytes 04-build_abe-stage1/console.log.xz | Bin 90724 -> 91548 bytes 06-build_abe-linux/console.log.xz | Bin 9272 -> 9304 bytes 07-build_abe-glibc/console.log.xz | Bin 235260 -> 234068 bytes 08-build_abe-stage2/console.log.xz | Bin 225352 -> 226196 bytes 09-build_abe-gdb/console.log.xz | Bin 37824 -> 37420 bytes 10-build_abe-qemu/console.log.xz | Bin 31080 -> 31784 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2800 bytes 13-check_regression/console.log.xz | Bin 5972 -> 6692 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 12 - 13-check_regression/mail-body.txt | 86 +- 13-check_regression/results.compare | 55 +- 13-check_regression/results.compare2 | 150 +- 13-check_regression/results.regressions | 46 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 88 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 46 - sumfiles/g++.log.xz | Bin 2688184 -> 2687132 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2210948 -> 2205300 bytes sumfiles/gcc.sum | 2411 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895240 -> 884360 bytes sumfiles/gfortran.sum | 13 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201088 -> 201252 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427332 -> 419324 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1463 insertions(+), 1589 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