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 4f4ce1f34 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] discards 6adc2749b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] discards 9584033d7 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 9605eb067 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 472b12f2a 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards 4dc182b10 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards 52eba0e3e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards c12f44d36 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 51715212c 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards 2936eb565 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards c0155e339 102: force: #1551: 1: Failure after gcc: 306 commits discards 32111668e 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards c4047a368 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 3361ff59a 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 7aa110dbb 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 0945b2e02 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards fe240ae41 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards fe90a6331 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0004c5b73 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 8d1d8448a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b676fc6a1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards d9369df81 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards e2ae5088e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 3acd1a13a 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 03d4cb64c 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards ce48391ce 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards d89f41c07 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards e72499634 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 81c9e25a4 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4d4db5123 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards be5ed259c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards fd4130a58 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d9f216713 80: onsuccess: 7: Successful build after linux: 44 commits discards 995b5a0ac 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 031c5db7e 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards ae9aa2211 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 825f5de57 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 4e11f291e 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 9e90af73a 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards ac4ad7a2d 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c519bb1dd 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a3d609453 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ffa9ae514 70: onsuccess: 7: Successful build after gcc: 4 commits discards 9c22aad57 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7997c3ef7 68: onsuccess: 7: Successful build after linux: 6 commits discards 787d378b7 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards 4a2a52d31 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 61a970129 65: onsuccess: 7: Successful build after binutils: 3 commits discards 7bcb9736b 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 91c2a2618 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 86831fce5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 468496467 61: onsuccess: 4: Successful build after gcc: 5 commits discards bd3f8b0bc 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 7bbe5be7b 59: force: 7: Successful build after gcc: 3 commits discards 018363953 58: onsuccess: 7: Successful build after glibc: 2 commits discards 5b6ed6b08 57: onsuccess: 7: Successful build after gcc: 7 commits discards 1a845c1df 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b4c896b7e 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6ac1646d6 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 042fb2433 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 329fdfec6 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards e05e24bb1 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9c110ed28 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aaa88f1ee 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f79685358 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards c10633c03 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9802ad34c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 96b9ad39b 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7478c2f57 44: onsuccess: 7: Successful build after linux: 34 commits discards ec1461176 43: onsuccess: 7: Successful build after gcc: 2 commits discards b233c5ad3 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 4d927c3a1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c1c882679 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 536b49d90 39: onsuccess: 7: Successful build after gcc: 2 commits discards 397df7e0b 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2c51d8fbf 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 40b0da681 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f42175aff 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3e5dba439 34: onsuccess: 7: Successful build after gcc: 3 commits discards 18f57378b 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1da837a2d 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards aeb62bab2 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b9d75d337 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards cbf620450 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a71b7b49e 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards a98e7e417 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards de0d27d06 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5df73c529 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a2f8f8729 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0c56a836c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e771a52f5 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 25458d4f9 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c50ab5205 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1dfb8efa2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e50e74916 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 576cbe754 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e6427281b 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3cf2ee4a8 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 681af7248 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 52cd81486 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1063c201b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2080a7ca2 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5454c8534 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ec7e78f96 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f24ba31c1 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e0c09f6e4 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b1b0a52cd 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2e77f990c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6e4b30ab8 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e25207410 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4e09b473c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 71af7cfa6 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ec3b5917f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 86ec90ab1 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8fe6e6588 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 53f3c3a52 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 59b5a1e0b 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e5f7661b9 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new d32ad5f4b 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 223c42be2 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 2d91a5c5e 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 4faf66790 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 1f1692cd6 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new be096974e 34: onsuccess: 7: Successful build after gcc: 3 commits new 753f60b55 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7bf8b83ae 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0bde4ae7b 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b030eb9cf 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7bc8925da 39: onsuccess: 7: Successful build after gcc: 2 commits new 5e86b4cb5 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dec145036 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8bf77641a 42: onsuccess: 7: Successful build after baseline build: no n [...] new 6e1ecf8e2 43: onsuccess: 7: Successful build after gcc: 2 commits new 9d1efc500 44: onsuccess: 7: Successful build after linux: 34 commits new 4a36ca571 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 244945714 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new fd697180f 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e4e050491 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 39540f063 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 942757e72 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 75ce00578 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 5b1f9ff2c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new a8bedd154 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 31863e341 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 0753e0d30 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 783f92728 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4b1d02c7a 57: onsuccess: 7: Successful build after gcc: 7 commits new e719908c5 58: onsuccess: 7: Successful build after glibc: 2 commits new 592a82c4e 59: force: 7: Successful build after gcc: 3 commits new 222befe2e 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new c3e212fb6 61: onsuccess: 4: Successful build after gcc: 5 commits new e62bf7202 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new b37c55638 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 4331cdb0f 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 457dd0523 65: onsuccess: 7: Successful build after binutils: 3 commits new e91e45241 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 450b8ae5f 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new ded6747ff 68: onsuccess: 7: Successful build after linux: 6 commits new 666e56cfc 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 996a8dbcf 70: onsuccess: 7: Successful build after gcc: 4 commits new 87563bf48 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 62bc3bce9 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9a15d456f 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e03357f2c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new c19753d46 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 6839069f9 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new d7b8e8833 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8cb83cd00 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 1396a8771 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b1686e413 80: onsuccess: 7: Successful build after linux: 44 commits new 19f6c23d8 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31712b671 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new dbd12b771 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 83c3b4178 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d999937ae 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 36e56c4cb 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 71070a405 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 6d0dc734b 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 157516d33 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b6bb7034a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 7ee120ce3 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new bc997d617 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 77d089f97 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 9e457d5db 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 3d5693572 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 8d84e7fd1 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6720843b9 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 49499b276 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new c195afcf1 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 1dc9a790c 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 7a22a17d9 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 194b478f2 102: force: #1551: 1: Failure after gcc: 306 commits new 863db0191 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 5ea6b56c2 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new dbe71bf65 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new 368208e10 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new 8fa875841 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new 5faca9cc2 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new 18aa5f61f 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 44e1c58b5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 6c2f31466 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] new f434af7fc 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] new 1439094f7 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...]
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 (4f4ce1f34) \ 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 1700 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30328 -> 30144 bytes 05-build_abe-stage1/console.log.xz | Bin 72268 -> 72296 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8564 -> 8588 bytes 08-build_abe-glibc/console.log.xz | Bin 238992 -> 240092 bytes 09-build_abe-stage2/console.log.xz | Bin 202320 -> 202352 bytes 10-build_abe-gdb/console.log.xz | Bin 37504 -> 37720 bytes 11-build_abe-qemu/console.log.xz | Bin 31716 -> 31224 bytes 12-check_regression/console.log.xz | Bin 3444 -> 3416 bytes 13-update_baseline/console.log | 40 ++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++++++++++++------------------ 22 files changed, 50 insertions(+), 50 deletions(-)