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 5b1d4e777 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 86bb4b2f6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 29122c678 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards a50c58803 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 4403d1410 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards c1f33b0e4 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards ea0b0b988 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards d09ea1d25 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards d35110f78 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 95d246d35 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 298cb9b7f 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 8850c1d97 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 8aad793d2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 706b99e8f 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 48d2d3fdb 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards a34e0816d 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards eab4f5841 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards e480c8be9 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 306fdc7bb 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 5b3b0c1e0 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 24a657ce0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards dff0d5ccb 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9c778f6d0 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 7f1ea066c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 1dc15b9c6 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards c0f044c4d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 60a6ae383 85: onsuccess: 7: Success after gcc: 9 commits discards f82a8f355 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 602d106d3 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 911424d83 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards cbc0594f3 81: onsuccess: 7: Successful build after gcc: 2 commits discards b1b2b1d23 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 5a16a55ef 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 74bfe585f 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 400f55652 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards b0d91fa47 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 03ed33e73 75: onsuccess: 7: Successful build after linux: 44 commits discards a49b60f67 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards bca4feaf8 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fe67c0511 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 5ee5c33c1 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 57ffde001 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards f2f1ab16a 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 09c42babf 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ddb423cc5 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 746e21fa9 66: onsuccess: 7: Successful build after gcc: 3 commits discards 7b0d28576 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aa83fe4fc 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1ccca755c 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 9a4c3d16f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 9b1ef1487 61: onsuccess: 4: Successful build after gcc: 15 commits discards 0ddb42f0b 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 7ef1d4857 59: force: 7: Successful build after gcc: 2 commits discards c7638f5ec 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8d4af6db3 57: onsuccess: 7: Successful build after gcc: 7 commits discards dcd8651b1 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 83a971766 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 183a10ce8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards f2f634eec 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 0ca6253cd 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 4b3e343bf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 31f2e4146 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c569ad6da 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7fd719919 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards b72e68739 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 242dce0fc 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards d48468def 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c0ab736ab 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards b6d883c72 43: onsuccess: 7: Successful build after gcc: 2 commits discards 7f1c4520d 42: onsuccess: 7: Successful build after baseline build: no n [...] discards e874b7223 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 21af8a80b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a32b20206 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 1e403532b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards c8b243a53 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 919585153 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 563370f5c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c71d8579b 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c6ed39774 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 06b3da2f9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards be651cfa4 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 48009ff30 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 0414922e1 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 4fc0ded2c 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 70b156f6e 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b8719ac4b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6eceb0b94 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 56656b490 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9b8bcdb91 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0bc0c3df1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 095a05a91 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2b11550e7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3cbdc2b98 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fb108b8cb 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2a1ba475a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4cd8cae77 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1f292e147 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 493dd1f64 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2fbef8f50 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5dbedf611 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3fcf45c5c 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e8ef961e5 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 749c4d834 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a4be697c7 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a9eb9d71d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d1952a7de 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 49feb97c7 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dec4a93a1 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 63d26c125 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c0a3fc826 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 792cd5eed 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e6d945d0d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d889fa989 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new eef81e218 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9a257f49b 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ee99591f5 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 13cd5c0b0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new aa50e892f 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c7f581a7b 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 52edd83c7 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new fe2e4b10f 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 4c4ff7a01 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new f49a89e34 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 465b8306d 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1e84524ed 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 296ec8ec2 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 2e2117ac7 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e2b860352 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 88175d3ac 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 39af3333b 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 7b4edc6e2 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c74f7b43e 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c5b41c38b 42: onsuccess: 7: Successful build after baseline build: no n [...] new 79571398f 43: onsuccess: 7: Successful build after gcc: 2 commits new e9fb6006f 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new c82fbd437 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4bdb169e3 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 1814f3431 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8499390d1 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 6df62766d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9a307348d 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 12e15e342 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1176ba816 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new e95e2de08 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 117c2495b 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 42d1f979c 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 705ff8ee7 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8b699f728 57: onsuccess: 7: Successful build after gcc: 7 commits new 26f7e9ff1 58: onsuccess: 7: Successful build after glibc: 2 commits new fac1e614d 59: force: 7: Successful build after gcc: 2 commits new 168923813 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 4cd2f9458 61: onsuccess: 4: Successful build after gcc: 15 commits new 2c9b2e752 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 160fe55f9 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 7cbd1d144 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4b380e8bc 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 30953c632 66: onsuccess: 7: Successful build after gcc: 3 commits new 5afe1ce76 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 315c6f733 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 859374791 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 950e660f3 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 3e125ed0a 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new c064fc5fe 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 6dda48186 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 6c54cab09 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new db22d6dd0 75: onsuccess: 7: Successful build after linux: 44 commits new f35af66ff 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 89dea62e0 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new c70e225cf 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new afb238813 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new eeafc2876 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 3a948fd3a 81: onsuccess: 7: Successful build after gcc: 2 commits new 4d8c0e6e5 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new c26541ddc 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 77bb8aa0c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 9522ea664 85: onsuccess: 7: Success after gcc: 9 commits new b53425094 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 450e448d3 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new d2eda3dbc 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new c7f38c289 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 8a8a5db0a 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a9c190658 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5bc2b8d5e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new d07067d5a 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 05149ed87 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 848a26bdb 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 8dd7e6d24 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 7d4160789 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 1db0ba3ea 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 8c7fd6102 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new dae0d5268 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 4b917b60d 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 62b9dda44 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new b972e22e6 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new bd6dd1824 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e40086239 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new ec9bea7a8 106: onsuccess: #1617: 7: Success after gcc: 2 commits new f7dd4ac90 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 6d6c9c14c 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 8a3179d42 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new 5085b2336 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new 24e1cd723 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new f8bb0f2f3 112: onsuccess: #1623: 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 (5b1d4e777) \ 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 1748 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30188 -> 29896 bytes 05-build_abe-stage1/console.log.xz | Bin 91120 -> 90668 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8296 -> 8344 bytes 08-build_abe-glibc/console.log.xz | Bin 234168 -> 234196 bytes 09-build_abe-stage2/console.log.xz | Bin 224652 -> 223076 bytes 10-build_abe-gdb/console.log.xz | Bin 37412 -> 37160 bytes 11-build_abe-qemu/console.log.xz | Bin 31444 -> 31408 bytes 12-check_regression/console.log.xz | Bin 2380 -> 2188 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- manifest.sh | 32 ++++++++--------- 17 files changed, 53 insertions(+), 53 deletions(-)