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 635b70944 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards e44ad120c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 025cf7099 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards b18b89d0b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards c59276abe 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 8e9a6cfcc 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards d23beeaa8 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 6886c4b42 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 909e397d1 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 5893c8440 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 93fd71660 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 528ac7320 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards d62001c82 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards beb1a3271 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 68fd00e71 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 86b59f414 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards d290ce668 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 37cd6a812 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards ec45d3aef 85: onsuccess: 7: Success after gcc: 9 commits discards f5eb17e81 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 107238895 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards f23d279be 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 53efbc534 81: onsuccess: 7: Successful build after gcc: 2 commits discards a31b5cda0 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 55ed1208f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5bf500d7a 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9359832d9 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards dcaa36168 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7d4728c2b 75: onsuccess: 7: Successful build after linux: 44 commits discards 524389d73 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 9b36b781f 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6d2181267 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 4b811dc47 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 89c9ab1cd 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 7b17f91b0 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards eca3db0ea 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5fd75d74b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4c6f60586 66: onsuccess: 7: Successful build after gcc: 3 commits discards 5113bbf50 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e850a977b 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 18112fb0f 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b24ea8431 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 703c4fbd6 61: onsuccess: 4: Successful build after gcc: 15 commits discards 0256ac75a 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 6663f71b6 59: force: 7: Successful build after gcc: 2 commits discards 3e45a4482 58: onsuccess: 7: Successful build after glibc: 2 commits discards 32e4be7b1 57: onsuccess: 7: Successful build after gcc: 7 commits discards b87f89705 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4b57db78f 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 061c2bab3 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards e491bf4f6 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 97a4e00c4 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards dae14cf99 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 0471e0791 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 83534820b 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3346b4fe9 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 8b707ff40 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fd140e4ca 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards be0f90060 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8b547f243 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards c0976ceca 43: onsuccess: 7: Successful build after gcc: 2 commits discards ee0ecfdf3 42: onsuccess: 7: Successful build after baseline build: no n [...] discards e815a0e86 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9bcec73f1 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0397f1298 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 06ed53ba2 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 283c7bd13 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 34b96f26f 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1f474c17d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9ded68683 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards cfc174b52 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 06a811d7c 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards da0459a86 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f4e0fa5e8 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 705a8489a 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards e78780f90 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 62fd61918 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 0dc634fba 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cd2b11d12 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b4dcde338 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b5ebde92c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1d9c811be 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ca851dd7a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3ff1288f2 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9e7709232 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e2154622e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3edb7b1c8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cda2c4b05 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 93549eae4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7d229fde4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 31ea793d3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c00a9733a 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 02d511a15 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b1b95fc03 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5d437f489 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 359eae453 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3b336a868 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 710186f7d 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 28d2b96e4 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 90decee55 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 867d6b185 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 10f81ce00 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2d46d927b 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 85c3cdc4f 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8b7de3615 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c5ca7b161 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 93180cfa7 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0f5328ffe 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1dd539e27 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 335f52829 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fdfddf4ed 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f7083ee85 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 621211906 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8e3c8a559 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 49e5425a1 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5f3b85a69 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9d387d94e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3839eaca3 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 47ceee116 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 15defad16 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6a875e051 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 37fa78b92 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 40770909d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2af033548 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3934aee9f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ddf897981 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 82013754f 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a24647a75 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 97d318033 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 369c031f8 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 436cd4546 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c7c8b137e 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 67755f245 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9406d8fe7 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 095e6a957 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new cd3631dd1 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b4cd799dd 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new ef719a7d1 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new f7d9eb39f 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5f08beb86 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 49d52040c 42: onsuccess: 7: Successful build after baseline build: no n [...] new d0e4d2ebe 43: onsuccess: 7: Successful build after gcc: 2 commits new 026fb6e9f 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new f5f04e622 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 61af94cae 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new f3cba5a2c 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3c2dfef85 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new c436ed0ef 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 217fae342 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a3c45cf00 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new abe7dda0e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 3c7273ebd 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new d24a1f23c 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new c6ac9f4e3 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fcee47c68 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new cb6df1dce 57: onsuccess: 7: Successful build after gcc: 7 commits new a2b7ba771 58: onsuccess: 7: Successful build after glibc: 2 commits new 759b7d300 59: force: 7: Successful build after gcc: 2 commits new af7c7fd12 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new e2c06bfcd 61: onsuccess: 4: Successful build after gcc: 15 commits new f4d431f59 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 9d57732e0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 37abf7a54 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 6959e6877 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a6990e04a 66: onsuccess: 7: Successful build after gcc: 3 commits new f29c1a50b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b39423ce1 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d4359a59e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new caa63b053 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 63dfbedcc 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new ff0c20380 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 4c6a209bc 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f02ec7157 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 1a4eacbd8 75: onsuccess: 7: Successful build after linux: 44 commits new d92573f78 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 553dc1c3a 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 5e1de8e9d 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 12cdde362 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new faa3abf0c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 1addd5730 81: onsuccess: 7: Successful build after gcc: 2 commits new edf0c514f 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 4a3826d80 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 824fe04ae 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 73816884b 85: onsuccess: 7: Success after gcc: 9 commits new 6a37db530 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 04861319c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 7a7a52d72 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 22e4aaf35 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new ed9984aab 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 3975354f7 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 119c5ae0e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 0f28871c6 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 5cbbd4dbb 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 05944b180 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 1e01bbd88 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 6575c3526 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 37dbb1660 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 08efb625d 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 22ffbcd65 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 0f46baea0 101: onsuccess: #1609: 7: Success after binutils: 78 commits new e380e4842 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 2ffb0dea3 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 5444bf46b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits

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 (635b70944) \ 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 1672 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30348 -> 30276 bytes 05-build_abe-stage1/console.log.xz | Bin 90948 -> 91120 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8608 -> 8560 bytes 08-build_abe-glibc/console.log.xz | Bin 233504 -> 233160 bytes 09-build_abe-stage2/console.log.xz | Bin 223368 -> 224100 bytes 10-build_abe-gdb/console.log.xz | Bin 37608 -> 37804 bytes 11-build_abe-qemu/console.log.xz | Bin 31500 -> 31460 bytes 12-check_regression/console.log.xz | Bin 2092 -> 2272 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 19 files changed, 51 insertions(+), 51 deletions(-)