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 f47c7e9ff 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 06be796e3 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 63a3a19a2 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards caf6b602e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 28a75a81c 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards d7b8a1aaf 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 13f667726 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards f388a0de8 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 1a28034a3 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards fee503032 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards db0b7f06b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 1a13f383f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 506e5a7e7 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 673bece96 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 2126bfc89 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 885a68e79 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards dd96cb12a 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 1e75f5058 85: onsuccess: 7: Success after gcc: 9 commits discards d1cafda9a 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards c3b95b7c4 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 11ef80ea6 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards c0ceee19f 81: onsuccess: 7: Successful build after gcc: 2 commits discards 40a43c8ac 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 621681050 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8443619e8 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b283891f6 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards e6328bded 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 39760d717 75: onsuccess: 7: Successful build after linux: 44 commits discards b646bbc8f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 897bf4f7e 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ac2e482ac 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 8fd5ec87e 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards e27cbeb61 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 9fed18732 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 846347186 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0d75ba733 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards cbd17a977 66: onsuccess: 7: Successful build after gcc: 3 commits discards b5f6a8a59 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5b414af24 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards bb08c7b76 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 246b945b9 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards c2d7f2b7d 61: onsuccess: 4: Successful build after gcc: 15 commits discards 95d38ef69 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 742c0102a 59: force: 7: Successful build after gcc: 2 commits discards 5125944a8 58: onsuccess: 7: Successful build after glibc: 2 commits discards f65642ec0 57: onsuccess: 7: Successful build after gcc: 7 commits discards ec9fe5df7 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2f4064c4b 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cb3e78563 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards bac6c1266 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 562a1736d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 1b24e8f3f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7903a495b 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3337edaa4 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 72bd36903 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 3a72a95a2 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aae7e784f 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 4502e1655 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8b40328c6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards e24db7c3b 43: onsuccess: 7: Successful build after gcc: 2 commits discards c461ec0f6 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 007793680 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f1988a66b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 344e07ff6 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 1ea6488f0 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 21f659882 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3f6c311df 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards acffa98de 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a66301045 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 32e15bf37 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b4e40d64c 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 176e7c9f3 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards fec0872b9 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 46a096a55 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 7d9f3a5d0 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f5f99a1e5 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a98044d2e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards eae4f29b7 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 486f7a4d1 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 54fd38f0e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4c9fea56e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards eea4e3e9d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d7a57da03 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1a312afe6 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a4c64bbf6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f976ba20f 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d7867f81e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b453da3c4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3730e536f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3dac5c6bd 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4c0f4ac17 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d19be793d 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 065235265 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 549f1a9b9 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 88cfed7fc 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 81ad01c8e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards acb473494 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 27b7cd926 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 87d82daba 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 29418bb98 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards edbfc4ec7 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1c0e7dec8 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 867d6b185 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 90decee55 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 28d2b96e4 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 710186f7d 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3b336a868 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 359eae453 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5d437f489 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b1b95fc03 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 02d511a15 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c00a9733a 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 31ea793d3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7d229fde4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 93549eae4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cda2c4b05 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3edb7b1c8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e2154622e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9e7709232 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3ff1288f2 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ca851dd7a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1d9c811be 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b5ebde92c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b4dcde338 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cd2b11d12 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0dc634fba 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 62fd61918 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e78780f90 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 705a8489a 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new f4e0fa5e8 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new da0459a86 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 06a811d7c 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new cfc174b52 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9ded68683 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1f474c17d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 34b96f26f 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 283c7bd13 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 06ed53ba2 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 0397f1298 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 9bcec73f1 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e815a0e86 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ee0ecfdf3 42: onsuccess: 7: Successful build after baseline build: no n [...] new c0976ceca 43: onsuccess: 7: Successful build after gcc: 2 commits new 8b547f243 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new be0f90060 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fd140e4ca 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 8b707ff40 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3346b4fe9 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 83534820b 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 0471e0791 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dae14cf99 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 97a4e00c4 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new e491bf4f6 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 061c2bab3 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 4b57db78f 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b87f89705 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 32e4be7b1 57: onsuccess: 7: Successful build after gcc: 7 commits new 3e45a4482 58: onsuccess: 7: Successful build after glibc: 2 commits new 6663f71b6 59: force: 7: Successful build after gcc: 2 commits new 0256ac75a 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 703c4fbd6 61: onsuccess: 4: Successful build after gcc: 15 commits new b24ea8431 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 18112fb0f 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new e850a977b 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5113bbf50 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4c6f60586 66: onsuccess: 7: Successful build after gcc: 3 commits new 5fd75d74b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new eca3db0ea 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7b17f91b0 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 89c9ab1cd 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 4b811dc47 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 6d2181267 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 9b36b781f 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 524389d73 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 7d4728c2b 75: onsuccess: 7: Successful build after linux: 44 commits new dcaa36168 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9359832d9 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 5bf500d7a 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 55ed1208f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a31b5cda0 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 53efbc534 81: onsuccess: 7: Successful build after gcc: 2 commits new f23d279be 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 107238895 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new f5eb17e81 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new ec45d3aef 85: onsuccess: 7: Success after gcc: 9 commits new 37cd6a812 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new d290ce668 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 86b59f414 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 68fd00e71 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new beb1a3271 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d62001c82 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 528ac7320 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 93fd71660 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 5893c8440 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 909e397d1 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 6886c4b42 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new d23beeaa8 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 8e9a6cfcc 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new c59276abe 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new b18b89d0b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 025cf7099 101: onsuccess: #1609: 7: Success after binutils: 78 commits new e44ad120c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 635b70944 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...]
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 (f47c7e9ff) \ 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 1668 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30860 -> 30348 bytes 05-build_abe-stage1/console.log.xz | Bin 92312 -> 90948 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8700 -> 8608 bytes 08-build_abe-glibc/console.log.xz | Bin 235704 -> 233504 bytes 09-build_abe-stage2/console.log.xz | Bin 224172 -> 223368 bytes 10-build_abe-gdb/console.log.xz | Bin 37432 -> 37608 bytes 11-build_abe-qemu/console.log.xz | Bin 31760 -> 31500 bytes 12-check_regression/console.log.xz | Bin 3980 -> 2092 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++------ 18 files changed, 50 insertions(+), 50 deletions(-)