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 7188413ff 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 417500e15 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 1c5c05d4d 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards fd42eac8e 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards cdfe277e6 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards c4d4ec1ce 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 2a6d182ed 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 821279c40 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards d41d0125d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 1b68590f6 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards d25afb705 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 93942c1bf 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards a9495eb7e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 584db62d3 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards ac3c28b67 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards f232efbca 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 982b1150e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 8ce688d90 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards c75486ca2 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards fa93f7352 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c2fde2634 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2b5d739fd 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 7aa2a35ce 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards cda37812b 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards f025ce448 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 7db50040b 85: onsuccess: 7: Success after gcc: 9 commits discards ca5d1f2d4 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards f65dea1e5 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 7302bee70 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 297e1cf04 81: onsuccess: 7: Successful build after gcc: 2 commits discards 903f3cd15 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 5a6fdb29f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3717cc0f0 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b5e99dfa8 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards a7e3a6e08 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d0c152775 75: onsuccess: 7: Successful build after linux: 44 commits discards b99cb1212 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 0236b1863 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 82cd4d6b8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 5dd20c0ee 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards a68a512de 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 261865bb2 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 28333c1a3 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7af80d88b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4e43b6ce8 66: onsuccess: 7: Successful build after gcc: 3 commits discards 7bf946650 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d9563e16b 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a6787642a 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 5a454856e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards dc890bbf5 61: onsuccess: 4: Successful build after gcc: 15 commits discards b63d1a926 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 36a8940d5 59: force: 7: Successful build after gcc: 2 commits discards 3de990cd0 58: onsuccess: 7: Successful build after glibc: 2 commits discards 1c0e9be12 57: onsuccess: 7: Successful build after gcc: 7 commits discards 76a2285f5 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 24c4d21a1 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 687cd2472 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 271b9b289 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 936e4316f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards a4bd75a8e 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b39dd7a77 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cc332a705 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2a4a386cd 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards c2d73951c 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 22434522c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 85908e790 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards acf93d684 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 9fa0a3f52 43: onsuccess: 7: Successful build after gcc: 2 commits discards 5d0f06376 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 8a6e62a6b 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ea2631d7f 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 17af35687 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 3eab0f107 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 84e3cad05 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ed5a06c12 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e6f05f43b 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards bb37ef83f 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c0a8642ef 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6d5a80fca 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 9fe063e46 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 993b60017 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 5daa69de2 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards fca4a2f22 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards bdd560454 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8194144da 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cd6fd675b 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0169b68e3 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 87d17978a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 847ef8434 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a02cc254a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6c63635af 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 570a03155 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 62ca1d3a0 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 84ab4b046 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7ef6e6baa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 991a72936 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 85d2a92b4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e7dab826e 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 939eed6e9 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f996a6f47 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5174d44d2 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ea8860d47 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3fcf45c5c 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5dbedf611 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2fbef8f50 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 493dd1f64 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1f292e147 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4cd8cae77 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2a1ba475a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fb108b8cb 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3cbdc2b98 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2b11550e7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 095a05a91 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0bc0c3df1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9b8bcdb91 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 56656b490 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6eceb0b94 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b8719ac4b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 70b156f6e 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 4fc0ded2c 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0414922e1 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 48009ff30 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new be651cfa4 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 06b3da2f9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c6ed39774 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c71d8579b 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 563370f5c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 919585153 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c8b243a53 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1e403532b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new a32b20206 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 21af8a80b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e874b7223 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7f1c4520d 42: onsuccess: 7: Successful build after baseline build: no n [...] new b6d883c72 43: onsuccess: 7: Successful build after gcc: 2 commits new c0ab736ab 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new d48468def 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 242dce0fc 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new b72e68739 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7fd719919 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new c569ad6da 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 31f2e4146 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4b3e343bf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 0ca6253cd 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new f2f634eec 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 183a10ce8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 83a971766 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dcd8651b1 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8d4af6db3 57: onsuccess: 7: Successful build after gcc: 7 commits new c7638f5ec 58: onsuccess: 7: Successful build after glibc: 2 commits new 7ef1d4857 59: force: 7: Successful build after gcc: 2 commits new 0ddb42f0b 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 9b1ef1487 61: onsuccess: 4: Successful build after gcc: 15 commits new 9a4c3d16f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1ccca755c 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new aa83fe4fc 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7b0d28576 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 746e21fa9 66: onsuccess: 7: Successful build after gcc: 3 commits new ddb423cc5 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 09c42babf 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f2f1ab16a 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 57ffde001 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 5ee5c33c1 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new fe67c0511 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new bca4feaf8 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a49b60f67 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 03ed33e73 75: onsuccess: 7: Successful build after linux: 44 commits new b0d91fa47 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 400f55652 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 74bfe585f 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5a16a55ef 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b1b2b1d23 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new cbc0594f3 81: onsuccess: 7: Successful build after gcc: 2 commits new 911424d83 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 602d106d3 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new f82a8f355 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 60a6ae383 85: onsuccess: 7: Success after gcc: 9 commits new c0f044c4d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 1dc15b9c6 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 7f1ea066c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 9c778f6d0 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new dff0d5ccb 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 24a657ce0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5b3b0c1e0 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 306fdc7bb 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new e480c8be9 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new eab4f5841 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new a34e0816d 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 48d2d3fdb 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 706b99e8f 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 8aad793d2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 8850c1d97 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 298cb9b7f 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 95d246d35 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new d35110f78 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new d09ea1d25 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new ea0b0b988 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new c1f33b0e4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 4403d1410 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a50c58803 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 29122c678 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new 86bb4b2f6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new 5b1d4e777 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 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 (7188413ff) \ 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 1628 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 29928 -> 30188 bytes 05-build_abe-stage1/console.log.xz | Bin 90788 -> 91120 bytes 07-build_abe-linux/console.log.xz | Bin 8296 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 232900 -> 234168 bytes 09-build_abe-stage2/console.log.xz | Bin 223152 -> 224652 bytes 10-build_abe-gdb/console.log.xz | Bin 37332 -> 37412 bytes 11-build_abe-qemu/console.log.xz | Bin 31632 -> 31444 bytes 12-check_regression/console.log.xz | Bin 2580 -> 2380 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++--------- 19 files changed, 54 insertions(+), 54 deletions(-)