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_build/master-arm in repository toolchain/ci/base-artifacts.
discards f091634e20 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 96232dd276 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 2df6582858 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards fbe260be3f 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards b3bf18e4bd 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards e1f8fb38a5 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 2f83878329 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 8b21b265ef 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 93fc19fffb 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 688a0039f3 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards adb89a399c 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 04978b13e0 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards e9cdfb929b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 71d8b8247f 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8972994f60 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards d7d96a87a5 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 551a3915c9 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards e97f12b7de 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 56f3ddb95e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards f9d16c7c4a 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 3d0fd91aad 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 093a70e243 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards c67e6a0262 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards c096af62aa 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards e7ceca9a5e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards d8be92f367 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards ccf3b94862 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 268feada01 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards b883038ab1 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 1bd4d1148a 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 671861afc3 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 775391e388 85: onsuccess: 7: Success after gcc: 9 commits discards bfd7738c65 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b013734f20 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 7157005baa 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 464038a06a 81: onsuccess: 7: Successful build after gcc: 2 commits discards ad488d672b 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 2d4f42578c 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 81a4733b7a 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8c6948f6e9 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 2feed04709 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b9b5d97679 75: onsuccess: 7: Successful build after linux: 44 commits discards 0c32c29e3c 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 136223605e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 141d056fd2 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 1c19a0359b 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards c538015fec 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 734ad015e7 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 3310ab42f1 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8a4a392300 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 14f7a0233b 66: onsuccess: 7: Successful build after gcc: 3 commits discards 61f8167778 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f03a082ab5 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 99b496e5d4 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards f78b41c2be 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards fa20f07981 61: onsuccess: 4: Successful build after gcc: 15 commits discards 55ee607d5b 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards d34269062b 59: force: 7: Successful build after gcc: 2 commits discards 3a65cd9769 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0389445cca 57: onsuccess: 7: Successful build after gcc: 7 commits discards 5d5aec7c5c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 844413e99f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards de9630c1fd 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 35eceb3a0d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 15097da43d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 5574262fde 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c3ef7e399b 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3e553f43ae 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0ce76dcbf2 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards ded977c540 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9c42d4b75c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards c2db8f1743 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fa81608cea 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 125a7834c3 43: onsuccess: 7: Successful build after gcc: 2 commits discards 24ff17dd31 42: onsuccess: 7: Successful build after baseline build: no [...] discards 6d6e8f4cca 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f44146c8f7 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 43e57f515e 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards a749677805 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 32c8b8f633 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 58363825ab 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4237d4f2c4 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 58c97bc4c6 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards bf92671372 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 96bcba2694 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards d467f7f1e3 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0b9826cf87 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards d524001d27 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 3b41984a32 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6d0eddf28f 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d7d1a05c32 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2d97ffcbcf 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 31e198a451 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c640866be7 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 75c031cdd5 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 46847e860b 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7358bc46a1 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6fe1d8816f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 047099385a 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8f122907b3 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6428c23673 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 67602a63cf 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1254b05461 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5de03b5126 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d598cf695c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7530e65eff 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 93788e2708 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3458e1044f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c5385a7e16 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 881c0a945d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5640080bf1 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b0241125c7 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 00c5ab0e61 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7dba3e7861 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e187f3c3d3 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new f5c7524295 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b0a31a3dd5 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 449ab6b221 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 52be1ffee2 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 88ed482fae 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 36401278a5 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 25f8dc64b4 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c8878de4f9 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a2643bf3a9 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 5436a8dd37 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 5c08d4c9e3 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dcdb078e1f 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c9c92ef661 42: onsuccess: 7: Successful build after baseline build: no [...] new 36d8bb9c95 43: onsuccess: 7: Successful build after gcc: 2 commits new e118b9a4f8 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 9e5f783fc5 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ecae886b47 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 01be214ba8 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2fed2562e4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 2de8cdbff9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new dde70a1a58 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6724d764cf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 443112a554 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 49780b7569 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 3a2db54084 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new a836838fcb 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b0494a6fbd 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4f15816227 57: onsuccess: 7: Successful build after gcc: 7 commits new bd4371f4a5 58: onsuccess: 7: Successful build after glibc: 2 commits new 2dce85195e 59: force: 7: Successful build after gcc: 2 commits new 2e85a8640e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new d6762d29f2 61: onsuccess: 4: Successful build after gcc: 15 commits new 490f4e83f5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a74e943d57 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 9922feaeb8 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6bc1dad7e2 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 872e7c3d04 66: onsuccess: 7: Successful build after gcc: 3 commits new 90918c1c8f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8b5c546eac 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9706a55833 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3fe6a43932 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 74a81d31f9 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 96d5225ee2 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new ca321e4fd7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4ea596feb0 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 59b5b2ab3b 75: onsuccess: 7: Successful build after linux: 44 commits new c6c75aab57 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e91bf366ff 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 7c78aade7e 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 44712230c0 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9f334e7c7c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 97a97c6ea0 81: onsuccess: 7: Successful build after gcc: 2 commits new f3783f6694 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new a80816f8e7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 427408c104 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 4e564e35a3 85: onsuccess: 7: Success after gcc: 9 commits new 4665cb4661 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 112268c2ae 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new b12654b085 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2defd5ce4f 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 805e559d01 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a78991e70f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 26c5a804d0 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new e2d48093be 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new b02fc82e8f 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new eb0cc8f43f 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new b78e8405e3 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 4207315217 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 8551eb25fa 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 191d5d390e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 4877d23b7c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new f30cccaecf 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 5694537274 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 572cc4def5 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 567720eae9 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 3c06e0831a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 653ff96928 106: onsuccess: #1617: 7: Success after gcc: 2 commits new af4c53a921 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 8c215694ea 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new fce563371f 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new a177ccd465 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new e27aa2a8a2 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new f8a6d51130 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 1d8dc5da45 113: onsuccess: #1624: 7: Success after gcc: 6 commits new abc1363011 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new fc64df32c4 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new b136ddd29c 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 6061890088 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...]
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 (f091634e20) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1720 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 29664 -> 30648 bytes 05-build_abe-stage1/console.log.xz | Bin 90936 -> 91040 bytes 07-build_abe-linux/console.log.xz | Bin 8624 -> 8584 bytes 08-build_abe-glibc/console.log.xz | Bin 233668 -> 233308 bytes 09-build_abe-stage2/console.log.xz | Bin 222904 -> 224768 bytes 10-build_abe-gdb/console.log.xz | Bin 37240 -> 38260 bytes 11-build_abe-qemu/console.log.xz | Bin 30708 -> 31288 bytes 12-check_regression/console.log.xz | Bin 3356 -> 2552 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++------------- 19 files changed, 42 insertions(+), 42 deletions(-)