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 d6f3b5301 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards 737c95ce5 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards b14b8b059 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 756954b61 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards b37b32de1 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 3e8a5e1de 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 431e280e9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 34ad8cd6a 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards e11ee6bcf 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards e3e2cb7b8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 791dd3706 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards bb4c9def6 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 370fe0e1c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 0c92f296c 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards fd2df6bb0 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 5edbcdd25 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards f68362186 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 6bee9eb09 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards af77af94e 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards b399900b3 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 0771b704e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards ca8b33979 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards ce984a828 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 5708f5350 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards a30c7f8c1 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8fb66aeaa 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards cbe7363eb 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 71f83176c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 563abe39a 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 1d5d2e1de 85: onsuccess: 7: Success after gcc: 9 commits discards e8db8aa62 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 11e8a7fd1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 629c596a3 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 1a1595b0b 81: onsuccess: 7: Successful build after gcc: 2 commits discards 480ac6be6 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 2c9dd5293 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b19d7202a 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 109520990 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 498ed215e 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8409a646a 75: onsuccess: 7: Successful build after linux: 44 commits discards 3a1ffe441 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5ebe101a8 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 39802aa66 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 0616e22e4 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 224b393c4 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 839ff9037 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 435a54d14 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8210d0534 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 918ce1e37 66: onsuccess: 7: Successful build after gcc: 3 commits discards a37ad283b 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a8a24fe20 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4b5458752 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards f6642075f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards e9f1904f1 61: onsuccess: 4: Successful build after gcc: 15 commits discards 8a4b0e46a 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards e4f13860c 59: force: 7: Successful build after gcc: 2 commits discards aa73300d3 58: onsuccess: 7: Successful build after glibc: 2 commits discards ae1a2b9df 57: onsuccess: 7: Successful build after gcc: 7 commits discards 77cde0ab6 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards eaec67c9f 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7b5de7f97 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 27721c913 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards d84bad93c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 32347b2a4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 94951948a 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 541e9086e 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c8dc1449f 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 4437f5a2f 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8101eaa7a 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 6dd8524de 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c8a33f2db 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 3af162baa 43: onsuccess: 7: Successful build after gcc: 2 commits discards 26b317ca2 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 50c78b0c7 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 62ebf4349 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a54fa4a1e 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 11c23a5da 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 7a6632791 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 33997eaa7 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ca51e453d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 844d6656b 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 28106abdc 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 71ff3ded2 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 29d5b2ef1 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 79c9876c8 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 07121b88d 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 6a6f01746 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f0bd206c7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 868ed81e9 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 676f367b2 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 46e94f470 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 415399c13 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 62c4ba60b 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1014aba48 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards aac68958c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b154a86a3 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7cc9e7888 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0fc4bd519 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 295c0dc7e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards eaebb0ed3 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0f094705b 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b8fb2ed9c 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4c243edb7 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2b4b50fbc 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c3f86e6c2 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e2946b528 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 06986fe09 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9e7e44c6d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 68305011b 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 62a4128df 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f56059745 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 37fc66b32 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 779831608 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a717d724d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d83395ebf 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new bba983589 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 824d1931c 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new e7ad33b1e 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 428b57f03 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7167d2f80 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 01e2059ef 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 047730488 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 5029d2cc6 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ef87ead6c 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0085d8b7e 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d51db150d 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new f2ad597ef 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 48ccf83a2 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 01bdf6fb7 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8c85d03de 42: onsuccess: 7: Successful build after baseline build: no n [...] new d9d73a54c 43: onsuccess: 7: Successful build after gcc: 2 commits new f1a6d0213 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 929a5655d 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5608814a0 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 51dfa94a7 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 053e7be4a 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 3c31b11e8 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ff522f520 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8af8830da 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e7651e2a3 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 59aa14172 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new fcfa668dd 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new dbd4b3822 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 34f87eba6 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3514ed960 57: onsuccess: 7: Successful build after gcc: 7 commits new 300c93107 58: onsuccess: 7: Successful build after glibc: 2 commits new 37bbf64bd 59: force: 7: Successful build after gcc: 2 commits new 7c489a96e 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 9c16a4d04 61: onsuccess: 4: Successful build after gcc: 15 commits new b78f19894 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 80d40c2d8 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new c87237831 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c31f33afd 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 550d5547c 66: onsuccess: 7: Successful build after gcc: 3 commits new 7c61232b8 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 2f1ea5005 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0ea20b862 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e283f4203 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new dcd4ba57f 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 42cbee5c6 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 6e237c5c5 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9843b7db0 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b4cbaaf91 75: onsuccess: 7: Successful build after linux: 44 commits new 647639a71 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a33e79068 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 110408494 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 43f5480f3 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 674813c11 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 996fa9a49 81: onsuccess: 7: Successful build after gcc: 2 commits new 083804ea8 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new b6392c386 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new a18527cd0 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new ecbc7ce61 85: onsuccess: 7: Success after gcc: 9 commits new 97646155a 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 4920312bb 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 9f1a54dd7 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 44bda230e 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 8b721255b 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c33217c3e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b5bfdb05e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new b724c61af 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new ec2dbd801 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new e0d2e53a1 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 3c7fd4dd7 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 847432e36 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new eb7811a7f 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 401273a17 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 01c32f27c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new b944af961 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 32f2f686a 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 48da79e25 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 29f09c2c9 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 7dd1ad3bf 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new edd8c7474 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 6e7a64fb5 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 5853977d2 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 152dce113 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new fc45b931c 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new 2e549130d 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 17ca09d33 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new a752dcc54 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 45a22afe9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new 354dfb253 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...]
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 (d6f3b5301) \ 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 1680 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 29828 -> 29868 bytes 05-build_abe-stage1/console.log.xz | Bin 90728 -> 90376 bytes 07-build_abe-linux/console.log.xz | Bin 8304 -> 8576 bytes 08-build_abe-glibc/console.log.xz | Bin 233460 -> 233444 bytes 09-build_abe-stage2/console.log.xz | Bin 224628 -> 223544 bytes 10-build_abe-gdb/console.log.xz | Bin 37100 -> 37168 bytes 11-build_abe-qemu/console.log.xz | Bin 31332 -> 31288 bytes 12-check_regression/console.log.xz | Bin 3080 -> 3316 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++---------- 21 files changed, 61 insertions(+), 61 deletions(-)