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 6061890088 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards b136ddd29c 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards fc64df32c4 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards abc1363011 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 1d8dc5da45 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards f8a6d51130 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards e27aa2a8a2 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards a177ccd465 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards fce563371f 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 8c215694ea 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards af4c53a921 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 653ff96928 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 3c06e0831a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 567720eae9 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 572cc4def5 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 5694537274 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards f30cccaecf 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 4877d23b7c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 191d5d390e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 8551eb25fa 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 4207315217 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards b78e8405e3 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards eb0cc8f43f 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards b02fc82e8f 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards e2d48093be 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 26c5a804d0 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a78991e70f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 805e559d01 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2defd5ce4f 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards b12654b085 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 112268c2ae 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 4665cb4661 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 4e564e35a3 85: onsuccess: 7: Success after gcc: 9 commits discards 427408c104 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a80816f8e7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards f3783f6694 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 97a97c6ea0 81: onsuccess: 7: Successful build after gcc: 2 commits discards 9f334e7c7c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 44712230c0 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7c78aade7e 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e91bf366ff 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards c6c75aab57 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 59b5b2ab3b 75: onsuccess: 7: Successful build after linux: 44 commits discards 4ea596feb0 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards ca321e4fd7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 96d5225ee2 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 74a81d31f9 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 3fe6a43932 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 9706a55833 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 8b5c546eac 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 90918c1c8f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 872e7c3d04 66: onsuccess: 7: Successful build after gcc: 3 commits discards 6bc1dad7e2 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9922feaeb8 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a74e943d57 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 490f4e83f5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards d6762d29f2 61: onsuccess: 4: Successful build after gcc: 15 commits discards 2e85a8640e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 2dce85195e 59: force: 7: Successful build after gcc: 2 commits discards bd4371f4a5 58: onsuccess: 7: Successful build after glibc: 2 commits discards 4f15816227 57: onsuccess: 7: Successful build after gcc: 7 commits discards b0494a6fbd 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a836838fcb 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3a2db54084 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 49780b7569 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 443112a554 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 6724d764cf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards dde70a1a58 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2de8cdbff9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2fed2562e4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 01be214ba8 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ecae886b47 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 9e5f783fc5 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e118b9a4f8 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 36d8bb9c95 43: onsuccess: 7: Successful build after gcc: 2 commits discards c9c92ef661 42: onsuccess: 7: Successful build after baseline build: no [...] discards dcdb078e1f 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5c08d4c9e3 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5436a8dd37 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards a2643bf3a9 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards c8878de4f9 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 25f8dc64b4 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 36401278a5 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 88ed482fae 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 52be1ffee2 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 449ab6b221 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards b0a31a3dd5 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f5c7524295 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards e187f3c3d3 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 7dba3e7861 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 00c5ab0e61 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b0241125c7 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5640080bf1 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 881c0a945d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c5385a7e16 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3458e1044f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 93788e2708 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7530e65eff 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d598cf695c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5de03b5126 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1254b05461 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a815497999 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 78056747ac 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d8f91783c1 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9ee73debb2 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b5f06db531 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9b45862763 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 38b2a1e4a8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new eec8609fdd 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c70ba9b134 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e014c1bdec 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e538cdae95 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 4eec1142e4 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 90de2a3273 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 576cec8a18 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 8e7840ebdd 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8c9f2b2ffe 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 74eb0d6664 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1d96ee5489 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 514be8bf65 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 94f29f6f79 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da18e6907c 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 88c3c08c57 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new d5c6cd19bd 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new c5184977c3 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fb1bde2506 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4c55e024f4 42: onsuccess: 7: Successful build after baseline build: no [...] new e4041c424e 43: onsuccess: 7: Successful build after gcc: 2 commits new 6a0a4d1dab 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 19b9dd800c 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c0a6ca5c75 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new f22b1e1223 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e1d672460e 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new a278cd0bd3 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 139121206d 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 480a1b9948 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 939f200b68 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new f5375fd29d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new ea27599be8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 2a69d2fddc 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6f9c7e6d80 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 023deefeb5 57: onsuccess: 7: Successful build after gcc: 7 commits new c15029a9bb 58: onsuccess: 7: Successful build after glibc: 2 commits new 0526fbc619 59: force: 7: Successful build after gcc: 2 commits new 0ad76fd0cc 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 4d68a83789 61: onsuccess: 4: Successful build after gcc: 15 commits new d59f841c71 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b33de5bd3d 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 9e29e716ae 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b251b31f41 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ac305469a7 66: onsuccess: 7: Successful build after gcc: 3 commits new 91e9c72ffd 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3e53509b06 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a4364cb5d6 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 841a5b5c09 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 64e44c7a1e 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new ed707e9c42 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 18ec9c396c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 719742dc5f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 1cc58e3984 75: onsuccess: 7: Successful build after linux: 44 commits new 4ddefe4d40 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fbf67406d2 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 62cef68a1f 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 023de1aef0 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 54cc6f59f4 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 4f6bdafb6a 81: onsuccess: 7: Successful build after gcc: 2 commits new a735874f88 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 03d4b6fa69 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new f72e4b9b46 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new d513298426 85: onsuccess: 7: Success after gcc: 9 commits new c4b548da78 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new aa04cfba25 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 2297e5e9d4 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2a80d9fb43 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 3cae051acf 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 38ec709767 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new e371d5dd97 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 3304294813 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 10747423d1 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 85527a10f6 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 2463cd39e8 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 7c247da721 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new d10ee60e58 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 24fda42ba9 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 8079498d74 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new d6805b1e81 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 0d545f3f7e 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 821a37271f 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 22b737492b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new a2cd86c8f1 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 89360f7c2d 106: onsuccess: #1617: 7: Success after gcc: 2 commits new ad018ca53b 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 7eb1967a12 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 47c9a6e48c 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new b28b21b989 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new f5ea8245c9 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 6a3a29acf0 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 3a822cd491 113: onsuccess: #1624: 7: Success after gcc: 6 commits new fbaf75c62b 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new b6a1c7b215 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 5b9b71cbb3 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 9d3a248fda 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new f46f9eff3c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...]
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 (6061890088) \ 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30648 -> 30564 bytes 05-build_abe-stage1/console.log.xz | Bin 91040 -> 91268 bytes 07-build_abe-linux/console.log.xz | Bin 8584 -> 8600 bytes 08-build_abe-glibc/console.log.xz | Bin 233308 -> 233992 bytes 09-build_abe-stage2/console.log.xz | Bin 224768 -> 225320 bytes 10-build_abe-gdb/console.log.xz | Bin 38260 -> 38072 bytes 11-build_abe-qemu/console.log.xz | Bin 31288 -> 31076 bytes 12-check_regression/console.log.xz | Bin 2552 -> 2756 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- 19 files changed, 56 insertions(+), 56 deletions(-)