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 f8bb0f2f3e 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 24e1cd7233 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 5085b23363 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 8a3179d42c 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 6d6c9c14c7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards f7dd4ac900 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ec9bea7a8c 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards e40086239e 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards bd6dd18243 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards b972e22e65 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 62b9dda448 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 4b917b60d1 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards dae0d52688 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 8c7fd61024 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 1db0ba3ea5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 7d4160789f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 8dd7e6d244 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 848a26bdbc 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 05149ed875 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards d07067d5a0 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 5bc2b8d5e8 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a9c190658c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8a8a5db0ae 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c7f38c2893 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards d2eda3dbc2 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 450e448d30 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards b534250941 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 9522ea664f 85: onsuccess: 7: Success after gcc: 9 commits discards 77bb8aa0c5 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards c26541ddc5 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 4d8c0e6e53 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 3a948fd3a7 81: onsuccess: 7: Successful build after gcc: 2 commits discards eeafc28761 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards afb2388139 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c70e225cf3 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 89dea62e0d 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards f35af66ff7 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards db22d6dd01 75: onsuccess: 7: Successful build after linux: 44 commits discards 6c54cab092 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 6dda481863 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c064fc5fe8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 3e125ed0ad 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 950e660f35 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 8593747917 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 315c6f733b 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5afe1ce76f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 30953c6326 66: onsuccess: 7: Successful build after gcc: 3 commits discards 4b380e8bc3 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7cbd1d1446 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 160fe55f9e 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 2c9b2e752c 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4cd2f94589 61: onsuccess: 4: Successful build after gcc: 15 commits discards 168923813f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards fac1e614dc 59: force: 7: Successful build after gcc: 2 commits discards 26f7e9ff1d 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8b699f7285 57: onsuccess: 7: Successful build after gcc: 7 commits discards 705ff8ee7b 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 42d1f979c1 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 117c2495b8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards e95e2de088 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 1176ba816d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 12e15e342b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9a307348d7 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6df62766d8 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 8499390d14 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 1814f3431f 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4bdb169e35 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards c82fbd4371 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e9fb6006ff 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 79571398f3 43: onsuccess: 7: Successful build after gcc: 2 commits discards c5b41c38b4 42: onsuccess: 7: Successful build after baseline build: no [...] discards c74f7b43e0 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7b4edc6e20 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 39af3333b3 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards 88175d3ac6 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards e2b860352f 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2e2117ac7c 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 296ec8ec2c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1e84524ed1 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 465b8306d2 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f49a89e349 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 4c4ff7a011 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fe2e4b10f1 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 52edd83c7f 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards c7f581a7b5 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards aa50e892f4 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 13cd5c0b04 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ee99591f5d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9a257f49b8 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards eef81e2182 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d889fa989d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e6d945d0dd 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 792cd5eed8 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c0a3fc8262 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 63d26c125c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dec4a93a13 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 49feb97c77 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d1952a7de7 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a9eb9d71d4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a4be697c7e 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 749c4d8348 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c4d2c3cb52 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 66a0900d8b 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7435cbd053 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ab3456dea6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fac4ef0544 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 86fbb6b9ab 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 50beb62ba7 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 48c9c33e3d 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f3ddd2beb2 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2db9a8a04a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c8c79d64a1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new aa5c81e2eb 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d074dc606f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new eb9087d827 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 69f08dba86 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ca6def3351 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b0b8d92a46 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 04bc95b90e 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new dc64adcc1a 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 29cc197474 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new dd71ade997 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new e1c226f0f5 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3c2bd746d6 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a70d407a79 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 365769474c 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a363d05c9f 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3936f31b1b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new d36da896c1 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new af6e3705fa 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e79bf06876 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ced499fa08 42: onsuccess: 7: Successful build after baseline build: no [...] new 4e9f62a295 43: onsuccess: 7: Successful build after gcc: 2 commits new 319ee955cf 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 6d7af5deb5 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f7437686c3 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 435e6a8c62 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e355316401 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 8d807ce511 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 25de5550ba 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8657953099 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 319d093808 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new b4b3d0b945 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new c7a8a246c5 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 0df4605e57 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9e28ec5984 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2390a4c387 57: onsuccess: 7: Successful build after gcc: 7 commits new 067a5ac8fe 58: onsuccess: 7: Successful build after glibc: 2 commits new 48f4506541 59: force: 7: Successful build after gcc: 2 commits new 74f01de300 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 3011cf6cec 61: onsuccess: 4: Successful build after gcc: 15 commits new 6ecfa4fabb 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 464af48265 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 5e3d6132b6 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b69144b4d4 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6ca23c9728 66: onsuccess: 7: Successful build after gcc: 3 commits new 027ebe4ac8 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 31ce8916b4 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2a1b51c256 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d3e3235e55 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 954c4c3aa0 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 731d17d147 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new dede9ad58f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8792292a42 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new c6ff5442a4 75: onsuccess: 7: Successful build after linux: 44 commits new 89c8df5cc2 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cac0f0160b 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 292e6431f7 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b27f13175f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 367b537671 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 55380251b2 81: onsuccess: 7: Successful build after gcc: 2 commits new 045848164b 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new b4ce0e9d6b 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 8a6324d36f 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e9c02b6180 85: onsuccess: 7: Success after gcc: 9 commits new a74e469c3e 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 03b9baba99 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 9c737b9692 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 4c764e9699 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 0e59d39dc8 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 57c8ec17a9 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a6a141dc21 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 5461e4f17c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 7d0136b550 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new d4243189f3 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new c76a2db82c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new b6d9dbe496 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new d90c320858 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 3a6d7c4358 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new b18e1256fd 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 2782430505 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 11f880aa75 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new e6abce1201 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 133f43ee12 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new f3efb7d25a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 43d0d4b762 106: onsuccess: #1617: 7: Success after gcc: 2 commits new d9aabe6634 107: onsuccess: #1618: 7: Success after gcc: 2 commits new abd9db328b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 2df35c68c2 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new d8886434eb 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 9f3dec4da4 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new ba9ce9befe 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new cf833c5bf8 113: onsuccess: #1624: 7: Success after gcc: 6 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 (f8bb0f2f3e) \ 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 1676 -> 1940 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29896 -> 30232 bytes 05-build_abe-stage1/console.log.xz | Bin 90668 -> 91804 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8344 -> 8380 bytes 08-build_abe-glibc/console.log.xz | Bin 234196 -> 235632 bytes 09-build_abe-stage2/console.log.xz | Bin 223076 -> 226648 bytes 10-build_abe-gdb/console.log.xz | Bin 37160 -> 37940 bytes 11-build_abe-qemu/console.log.xz | Bin 31408 -> 31616 bytes 12-check_regression/console.log.xz | Bin 2188 -> 2516 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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, 49 insertions(+), 49 deletions(-)