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 b71b12c9c 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards ac52c14e8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 2bb875f97 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 2edc6e9d0 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards df1183769 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 64ef07bab 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 326ab9537 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards b5e828028 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 6a7a0d6a9 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 682cbce2b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards b231ce17c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 07a88ea27 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 690d81d38 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 134d5141c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards c54b0204e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 32c351e54 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 59d12b55e 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 203c8b245 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 73d49b73e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 64b73de20 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 091ef3a83 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 617829898 85: onsuccess: 7: Success after gcc: 9 commits discards c6a87faab 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 148fbf2b7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards a67f336a8 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards ab6f268e4 81: onsuccess: 7: Successful build after gcc: 2 commits discards 1f3f28be7 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards efe644422 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5d9375a37 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b12415009 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards c574024b2 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3782c315b 75: onsuccess: 7: Successful build after linux: 44 commits discards 53a49df8f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards be70ca262 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 911c9b605 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 7404fbea2 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards ffcf00cc2 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 87da99bfa 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards e776ee3b1 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards dd9e8afbe 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4500c19f6 66: onsuccess: 7: Successful build after gcc: 3 commits discards a80b9c313 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cf09a29ef 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0266e0112 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards d8ecc6513 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards b76197842 61: onsuccess: 4: Successful build after gcc: 15 commits discards fea118aed 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards e4591db78 59: force: 7: Successful build after gcc: 2 commits discards e9bcdd716 58: onsuccess: 7: Successful build after glibc: 2 commits discards ff8b1d990 57: onsuccess: 7: Successful build after gcc: 7 commits discards 34cd050cf 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 046f05da8 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fefe1e24e 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 4ec5a8644 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards a3a98627a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards fad2f9fb4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ddb930b27 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2f7841333 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c1b201c31 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 017159daa 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 43bbe622b 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards f53c0c856 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6b9a7897c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards cdec483d2 43: onsuccess: 7: Successful build after gcc: 2 commits discards 74da085dd 42: onsuccess: 7: Successful build after baseline build: no n [...] discards d7ad67ce0 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7369d9cf6 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 72147d516 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards cd633df01 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards aefa9fa2d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 96b9b29e2 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 09b1dc3a1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7db600b22 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 1cd53dcdc 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6e0c51cd1 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 02c9f221b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f6fe8b0e7 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards c84056e17 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 94e5195e7 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a745c928a 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 997bd8301 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards be0e7a661 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 29dcf2782 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 841b3de2d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3c947d902 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2a97f37c4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8143210f9 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9b254a859 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7d0a54e08 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7796c943a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b7852f535 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 616f1b2a0 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 37b4f9cee 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4266f9c09 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b77cde2b3 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e768eafbf 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 51343f027 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fbf653606 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9f258e127 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9948bbd4e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f28b3b495 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1089b3436 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c103fcefc 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3a2842477 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ec2103972 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7c62eb16d 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84edebcdc 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 11179f36d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new df8222ec3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9ba861b5f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 78cd73d54 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 864adeba9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d0405245c 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9f12fde28 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 42271e6a9 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c57f4eddb 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2d158625d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d93a3d64f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 94124291b 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 449e693bf 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c6f62672a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7e5b32e17 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fa60f4ba0 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 211fb3104 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5700e5e99 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 93634f04f 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new aa709da91 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 3a0224fac 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c86c4c471 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d6c08525e 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 22250cf0d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ac2f2df17 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1a2a10c3d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new eb08f3a08 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 469900fb7 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new ca86eaf6b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 65d0ec0d9 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new bdfa2ade0 42: onsuccess: 7: Successful build after baseline build: no n [...] new adc3f822b 43: onsuccess: 7: Successful build after gcc: 2 commits new d54dd49c2 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 2a9a5134a 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 91e5b20aa 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new aa2500ffc 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3b754ac9f 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 76d1f436d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9af8e3e45 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 49733247a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9d5a17235 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 72f98604b 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 57c41daf5 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 1cbca3d0b 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0594ece6c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3c8d70c69 57: onsuccess: 7: Successful build after gcc: 7 commits new 4b9415973 58: onsuccess: 7: Successful build after glibc: 2 commits new da33f1d38 59: force: 7: Successful build after gcc: 2 commits new ae7b28ef2 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 27156c50b 61: onsuccess: 4: Successful build after gcc: 15 commits new 673a59cf4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 84ab553e0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 34587bd7a 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 336cf78cf 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8647cdcd6 66: onsuccess: 7: Successful build after gcc: 3 commits new 2be0feb10 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 401983ecb 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3a5fb57c5 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c2a7b6602 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 4a835e2c3 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new ec8e5b22d 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 41c918fe6 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2b02f6a8c 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 464bc4b40 75: onsuccess: 7: Successful build after linux: 44 commits new 325e089b3 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3b71b0a57 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 5a1d13e29 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9898318fc 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 583bd3bd4 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new bb208fe85 81: onsuccess: 7: Successful build after gcc: 2 commits new 1182870c2 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 5a1fa0c01 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 5a12ae682 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2b5217168 85: onsuccess: 7: Success after gcc: 9 commits new 59464e9f9 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 9d1d26530 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 86b5dd348 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 78a5d3a60 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 01713bc14 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 943c5a4ab 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b64d2901b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new fba3124ae 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 73ea13154 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new abd2aff0a 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new ca6ccd4f8 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 492534169 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new d6d14ad3b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new cc78b3a1c 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new a5a53399f 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 1248222c1 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 9e5c9d6fc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 5a416f32a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new bdcafddcc 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 2b084ce7c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new d499fac43 106: onsuccess: #1617: 7: Success after gcc: 2 commits new f752500b5 107: onsuccess: #1618: 7: Success after gcc: 2 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 (b71b12c9c) \ 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 1728 -> 1864 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29852 -> 29812 bytes 05-build_abe-stage1/console.log.xz | Bin 91456 -> 90960 bytes 07-build_abe-linux/console.log.xz | Bin 8628 -> 8596 bytes 08-build_abe-glibc/console.log.xz | Bin 233860 -> 233584 bytes 09-build_abe-stage2/console.log.xz | Bin 224132 -> 223780 bytes 10-build_abe-gdb/console.log.xz | Bin 37152 -> 37268 bytes 11-build_abe-qemu/console.log.xz | Bin 31192 -> 31248 bytes 12-check_regression/console.log.xz | Bin 2324 -> 2136 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- manifest.sh | 22 ++++++------ 14 files changed, 45 insertions(+), 45 deletions(-)