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-aarch64 in repository toolchain/ci/base-artifacts.
discards 1439094f7f 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards f434af7fc8 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 6c2f314667 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 44e1c58b5a 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 18aa5f61f1 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 5faca9cc2c 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 8fa875841b 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 368208e109 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards dbe71bf654 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 5ea6b56c2b 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 863db01914 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 194b478f25 102: force: #1551: 1: Failure after gcc: 306 commits discards 7a22a17d97 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 1dc9a790c9 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards c195afcf16 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 49499b276d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 6720843b9f 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 8d84e7fd1e 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3d5693572d 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9e457d5db9 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 77d089f974 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards bc997d6179 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 7ee120ce33 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards b6bb7034af 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 157516d33d 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 6d0dc734bf 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 71070a4053 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 36e56c4cb9 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards d999937ae7 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 83c3b4178c 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards dbd12b771d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 31712b6714 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 19f6c23d8e 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b1686e413a 80: onsuccess: 7: Successful build after linux: 44 commits discards 1396a87710 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 8cb83cd00a 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards d7b8e88335 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6839069f9b 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards c19753d465 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e03357f2cd 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 9a15d456fc 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 62bc3bce98 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 87563bf489 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 996a8dbcff 70: onsuccess: 7: Successful build after gcc: 4 commits discards 666e56cfce 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ded6747ff4 68: onsuccess: 7: Successful build after linux: 6 commits discards 450b8ae5ff 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards e91e452412 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 457dd0523c 65: onsuccess: 7: Successful build after binutils: 3 commits discards 4331cdb0f2 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b37c556386 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards e62bf7202b 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards c3e212fb6e 61: onsuccess: 4: Successful build after gcc: 5 commits discards 222befe2e0 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 592a82c4e8 59: force: 7: Successful build after gcc: 3 commits discards e719908c50 58: onsuccess: 7: Successful build after glibc: 2 commits discards 4b1d02c7ac 57: onsuccess: 7: Successful build after gcc: 7 commits discards 783f927286 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0753e0d30b 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 31863e3412 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards a8bedd1548 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 5b1f9ff2c3 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 75ce00578e 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 942757e727 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 39540f0635 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e4e0504916 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards fd697180fd 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2449457141 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 4a36ca5712 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9d1efc5009 44: onsuccess: 7: Successful build after linux: 34 commits discards 6e1ecf8e26 43: onsuccess: 7: Successful build after gcc: 2 commits discards 8bf77641ae 42: onsuccess: 7: Successful build after baseline build: no [...] discards dec1450362 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5e86b4cb54 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7bc8925da2 39: onsuccess: 7: Successful build after gcc: 2 commits discards b030eb9cfe 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0bde4ae7b0 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7bf8b83ae9 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 753f60b555 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards be096974ed 34: onsuccess: 7: Successful build after gcc: 3 commits discards 1f1692cd6a 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4faf667901 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 2d91a5c5ee 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 223c42be2d 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards d32ad5f4b6 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e5f7661b9d 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 59b5a1e0b4 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 53f3c3a52c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8fe6e65881 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 86ec90ab18 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ec3b5917fa 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 71af7cfa6c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4e09b473c5 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e252074103 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6e4b30ab86 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2e77f990cb 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b1b0a52cd5 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e0c09f6e4f 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f24ba31c1a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ec7e78f964 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5454c8534e 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1b7afe90f4 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d9f0911d70 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6504e75248 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 94cf853d6e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6c6902742a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c5886a3828 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9d3b9060ee 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 52eb628ef9 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1515b3a082 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3f1fa71001 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ac3e0710fc 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4337a4dfb3 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9ca5e97d28 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7d5350bf10 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 62a314fe77 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b060841480 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 79436166d1 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f253dee8d1 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new c02f0d1b67 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2629b92817 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new f68b774786 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9be500faa4 34: onsuccess: 7: Successful build after gcc: 3 commits new 63d3f0c707 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9ce6419325 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9e7a6c9540 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f3dbbb293d 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7c9df312f1 39: onsuccess: 7: Successful build after gcc: 2 commits new 1ecc718a38 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 164f2460e1 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f0c8037864 42: onsuccess: 7: Successful build after baseline build: no [...] new a53eb87fdc 43: onsuccess: 7: Successful build after gcc: 2 commits new 62d490537f 44: onsuccess: 7: Successful build after linux: 34 commits new 1bfa131c29 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 18c95745bc 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new bb5df39f10 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f331f404aa 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 09496d33b8 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a8231f4a37 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7cd48224b4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3c91d41c2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 65eb3b3383 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new f18317181a 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new b7aa11b704 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 84d7ac994e 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3e1c57f0a1 57: onsuccess: 7: Successful build after gcc: 7 commits new 620eedef16 58: onsuccess: 7: Successful build after glibc: 2 commits new ef6b193bec 59: force: 7: Successful build after gcc: 3 commits new 95ee83d851 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 0ba637c968 61: onsuccess: 4: Successful build after gcc: 5 commits new b70a93f04e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 264c566632 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 258a0abe27 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new f8e57bc134 65: onsuccess: 7: Successful build after binutils: 3 commits new 3686e5495a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 8d98a37d9e 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 96437fd373 68: onsuccess: 7: Successful build after linux: 6 commits new a1b5dabd06 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5e9b0e58af 70: onsuccess: 7: Successful build after gcc: 4 commits new 0d7351bad0 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new cb3617bd4e 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 554e317c8d 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 18750d56e4 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new ce77a14678 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 132097c294 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 9d6673a81c 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ac6d91ad9a 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 43e499613a 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 5f69821b75 80: onsuccess: 7: Successful build after linux: 44 commits new 8013931622 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cb30ed799e 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 9e4c9fae61 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 263393cdfb 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 59151d13a8 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 16ec9a5a0a 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 306acfbbcb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 0eedc0ad53 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 6a0d8568d3 89: onsuccess: 7: Success after gcc/glibc: 8 commits new f2aae716b2 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new b6eb8e3d5c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 3c314a59a1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 76c19256c0 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new f2deb1f297 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 421d62ffe1 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f630447787 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new db98d0f1b1 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 1bb0906a29 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new babc03de4e 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 65809a0727 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 3ffa4bdcd6 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 46771c688d 102: force: #1551: 1: Failure after gcc: 306 commits new f73ce01c7d 103: onsuccess: #1552: 1: Success after gcc: 5 commits new dc4d733e72 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 7edd79686b 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 0d08b6184c 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 6bf8dabaf5 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 3c015ec421 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 61848fec97 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new f7183d505b 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 62f89a3d7c 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new ec87750226 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 6a0dbf17de 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 2a84063aa6 114: onsuccess: #1563: 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 (1439094f7f) \ 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 1688 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30144 -> 30800 bytes 05-build_abe-stage1/console.log.xz | Bin 72296 -> 72072 bytes 07-build_abe-linux/console.log.xz | Bin 8588 -> 8572 bytes 08-build_abe-glibc/console.log.xz | Bin 240092 -> 240392 bytes 09-build_abe-stage2/console.log.xz | Bin 202352 -> 203252 bytes 10-build_abe-gdb/console.log.xz | Bin 37720 -> 38020 bytes 11-build_abe-qemu/console.log.xz | Bin 31224 -> 32012 bytes 12-check_regression/console.log.xz | Bin 3416 -> 2668 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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, 55 insertions(+), 55 deletions(-)