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 5444bf46b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 2ffb0dea3 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards e380e4842 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 0f46baea0 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 22ffbcd65 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 08efb625d 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 37dbb1660 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 6575c3526 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 1e01bbd88 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 05944b180 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 5cbbd4dbb 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 0f28871c6 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 119c5ae0e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 3975354f7 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards ed9984aab 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 22e4aaf35 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 7a7a52d72 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 04861319c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 6a37db530 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 73816884b 85: onsuccess: 7: Success after gcc: 9 commits discards 824fe04ae 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4a3826d80 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards edf0c514f 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 1addd5730 81: onsuccess: 7: Successful build after gcc: 2 commits discards faa3abf0c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 12cdde362 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5e1de8e9d 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 553dc1c3a 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards d92573f78 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1a4eacbd8 75: onsuccess: 7: Successful build after linux: 44 commits discards f02ec7157 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 4c6a209bc 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ff0c20380 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 63dfbedcc 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards caa63b053 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards d4359a59e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b39423ce1 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f29c1a50b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a6990e04a 66: onsuccess: 7: Successful build after gcc: 3 commits discards 6959e6877 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 37abf7a54 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9d57732e0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards f4d431f59 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards e2c06bfcd 61: onsuccess: 4: Successful build after gcc: 15 commits discards af7c7fd12 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 759b7d300 59: force: 7: Successful build after gcc: 2 commits discards a2b7ba771 58: onsuccess: 7: Successful build after glibc: 2 commits discards cb6df1dce 57: onsuccess: 7: Successful build after gcc: 7 commits discards fcee47c68 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c6ac9f4e3 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d24a1f23c 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 3c7273ebd 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards abe7dda0e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards a3c45cf00 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 217fae342 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c436ed0ef 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3c2dfef85 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards f3cba5a2c 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 61af94cae 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards f5f04e622 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 026fb6e9f 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards d0e4d2ebe 43: onsuccess: 7: Successful build after gcc: 2 commits discards 49d52040c 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 5f08beb86 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f7d9eb39f 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ef719a7d1 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards b4cd799dd 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards cd3631dd1 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 095e6a957 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9406d8fe7 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 67755f245 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c7c8b137e 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 436cd4546 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 369c031f8 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 97d318033 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards a24647a75 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 82013754f 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ddf897981 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3934aee9f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2af033548 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 40770909d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 37fa78b92 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6a875e051 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 15defad16 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 47ceee116 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3839eaca3 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9d387d94e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5f3b85a69 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 49e5425a1 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8e3c8a559 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 621211906 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f7083ee85 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fdfddf4ed 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 335f52829 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1dd539e27 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0f5328ffe 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 93180cfa7 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c5ca7b161 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8b7de3615 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 85c3cdc4f 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2d46d927b 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 32375bf6d 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c11b441d7 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a549abe11 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e5f65f494 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 31bb0edff 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b8ac956aa 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b8aa3abe6 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dfafced03 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 459a93879 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d89a9ecfa 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f18138d4e 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dd331f4fe 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 260c2f1c1 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b554b8da1 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a9c86a7f8 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2e1cefd82 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 44ab862b4 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4aafdc89f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e5c4957d9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e82a5b5ac 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 90ea719ec 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 70e2c8978 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5333a3747 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e8ba87e82 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 0b11c2810 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 27febcb7e 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 3b3653b3e 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 88ac57897 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 019c0155d 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 77a824950 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 63f907220 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new eb7dc2835 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 166afeecd 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new bc61c349c 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 20bc7d07e 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 63c017413 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new eb26b3c63 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0c4f95be4 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 871361c24 42: onsuccess: 7: Successful build after baseline build: no n [...] new be00a48a9 43: onsuccess: 7: Successful build after gcc: 2 commits new 39130dffc 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 6dc1273b0 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d0aed12b4 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new d00a37ffd 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7721daa49 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 4fb0fd04a 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 20f38bab4 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 36cc20c6a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e85b38b65 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new a85b3a7f9 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new ec40ec2db 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new cea63ad8a 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 77790b6e7 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8b6213b7b 57: onsuccess: 7: Successful build after gcc: 7 commits new 5276868ca 58: onsuccess: 7: Successful build after glibc: 2 commits new 8770cdb3e 59: force: 7: Successful build after gcc: 2 commits new ad71a8475 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 3419dea37 61: onsuccess: 4: Successful build after gcc: 15 commits new cc9efabd1 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 0a90f29f3 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 7caf189b8 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4a3a5d51a 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 50d0dc70f 66: onsuccess: 7: Successful build after gcc: 3 commits new 680208587 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9d0346d67 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new cb74f06fb 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 967aaccec 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new bd0658f5b 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 1c314314a 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 66ebead03 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e9c21300f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 5af753f6b 75: onsuccess: 7: Successful build after linux: 44 commits new 3d90437c8 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f32d7a003 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new ac0782e99 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8dbd144b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 53fc33733 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 0f1fcb807 81: onsuccess: 7: Successful build after gcc: 2 commits new f0f67ee8d 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new d7bb8a2f7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 290ff7886 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 6efb034e5 85: onsuccess: 7: Success after gcc: 9 commits new 8ba4913d0 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new d7627a86b 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 24449e352 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new b88797d72 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 9249e429f 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fff10a8d1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 44398c713 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 9d883ff27 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 04d44a072 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new fbaa0583c 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 57622faf6 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new f03f178c0 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new a82c3e358 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 52d73af54 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 2294bbe0b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new c13d7468f 101: onsuccess: #1609: 7: Success after binutils: 78 commits new dcadd47b5 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new d5d09a8dc 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 13986491e 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 41d31b635 105: onsuccess: #1616: 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 (5444bf46b) \ 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30276 -> 29944 bytes 05-build_abe-stage1/console.log.xz | Bin 91120 -> 90364 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8560 -> 8644 bytes 08-build_abe-glibc/console.log.xz | Bin 233160 -> 234132 bytes 09-build_abe-stage2/console.log.xz | Bin 224100 -> 222860 bytes 10-build_abe-gdb/console.log.xz | Bin 37804 -> 36936 bytes 11-build_abe-qemu/console.log.xz | Bin 31460 -> 31728 bytes 12-check_regression/console.log.xz | Bin 2272 -> 2696 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ 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 | 40 +++++++++++----------- 22 files changed, 60 insertions(+), 60 deletions(-)