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 f752500b5 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards d499fac43 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 2b084ce7c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards bdcafddcc 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 5a416f32a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 9e5c9d6fc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 1248222c1 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards a5a53399f 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards cc78b3a1c 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards d6d14ad3b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 492534169 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards ca6ccd4f8 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards abd2aff0a 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 73ea13154 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards fba3124ae 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards b64d2901b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 943c5a4ab 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 01713bc14 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 78a5d3a60 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 86b5dd348 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 9d1d26530 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 59464e9f9 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 2b5217168 85: onsuccess: 7: Success after gcc: 9 commits discards 5a12ae682 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 5a1fa0c01 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 1182870c2 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards bb208fe85 81: onsuccess: 7: Successful build after gcc: 2 commits discards 583bd3bd4 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 9898318fc 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5a1d13e29 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3b71b0a57 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 325e089b3 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 464bc4b40 75: onsuccess: 7: Successful build after linux: 44 commits discards 2b02f6a8c 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 41c918fe6 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ec8e5b22d 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 4a835e2c3 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards c2a7b6602 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 3a5fb57c5 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 401983ecb 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2be0feb10 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8647cdcd6 66: onsuccess: 7: Successful build after gcc: 3 commits discards 336cf78cf 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 34587bd7a 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 84ab553e0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 673a59cf4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 27156c50b 61: onsuccess: 4: Successful build after gcc: 15 commits discards ae7b28ef2 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards da33f1d38 59: force: 7: Successful build after gcc: 2 commits discards 4b9415973 58: onsuccess: 7: Successful build after glibc: 2 commits discards 3c8d70c69 57: onsuccess: 7: Successful build after gcc: 7 commits discards 0594ece6c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1cbca3d0b 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 57c41daf5 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 72f98604b 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 9d5a17235 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 49733247a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9af8e3e45 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 76d1f436d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3b754ac9f 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards aa2500ffc 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 91e5b20aa 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 2a9a5134a 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d54dd49c2 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards adc3f822b 43: onsuccess: 7: Successful build after gcc: 2 commits discards bdfa2ade0 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 65d0ec0d9 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ca86eaf6b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 469900fb7 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards eb08f3a08 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 1a2a10c3d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ac2f2df17 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 22250cf0d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards d6c08525e 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c86c4c471 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3a0224fac 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards aa709da91 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 93634f04f 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 5700e5e99 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 211fb3104 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fa60f4ba0 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7e5b32e17 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c6f62672a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 449e693bf 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 94124291b 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d93a3d64f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2d158625d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c57f4eddb 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 42271e6a9 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9f12fde28 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d0405245c 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 864adeba9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 78cd73d54 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9ba861b5f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards df8222ec3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 11179f36d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 84edebcdc 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7c62eb16d 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ec2103972 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3a2842477 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c103fcefc 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 479aa1e5f 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1e7f1bc66 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 65f681604 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e373159b3 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e498a68cb 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6db2ca82f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ca929676c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f22bfe65d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d015985fb 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new faf8fed1c 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1820ebf08 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8597778a9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 58452bcdd 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6afe6e6d7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 172a9a5ba 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f0b6a82d2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 969910196 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0844e9f4a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 08b3b99ec 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a6085133c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8a7c9e0e7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 27f280c88 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new bfa703dbc 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 8c7b8a013 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1737cd1c9 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 16c0577b9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 7425ebb26 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7d983b2ec 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 0bd61d968 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 2a994227c 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 563e11974 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d55655b7a 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 28986ee55 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new e01028825 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 45c5011a1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 134cdc262 42: onsuccess: 7: Successful build after baseline build: no n [...] new f13c88c67 43: onsuccess: 7: Successful build after gcc: 2 commits new 5cbe4386c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 605603cbd 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d75ff0081 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new e27ae96c1 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ebeb715f5 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new c5b366004 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 5c4b3d0bf 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3066a416c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9c2cdea2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 42dd03b21 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 211dbf48f 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 6b7c1b1f5 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 28229e292 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8fcb7d424 57: onsuccess: 7: Successful build after gcc: 7 commits new 0bde18d9b 58: onsuccess: 7: Successful build after glibc: 2 commits new 169506537 59: force: 7: Successful build after gcc: 2 commits new f984f7ad8 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new dd0961ce0 61: onsuccess: 4: Successful build after gcc: 15 commits new b333e2fda 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 0698d5f61 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 70165a7ea 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 95adce5e4 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 237552bef 66: onsuccess: 7: Successful build after gcc: 3 commits new 563d17811 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 77f0ba9b6 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7912da988 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ff0b4942d 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 09df4e51b 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 8ee68758b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new d026dc34a 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d86067227 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 3ff4e0653 75: onsuccess: 7: Successful build after linux: 44 commits new 3282187f0 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 05bb13472 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new fbeb5e629 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new cfd38d608 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 03a01dccf 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 3e38ed108 81: onsuccess: 7: Successful build after gcc: 2 commits new 5a6111ac5 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 03531c426 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new ad819e31c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e36bb7d40 85: onsuccess: 7: Success after gcc: 9 commits new 830cc3b46 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 978cd5b6a 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 5286a9ae8 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 6c1a46d82 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new d0e8f23e6 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new bd4c466cc 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fec155ae5 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new dd0d7ce11 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 488391772 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new e7cc0186f 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 8ee42dff9 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 4d3d663be 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 3ddedaa82 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 9022b346e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new b3852eb93 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 6aa2034b6 101: onsuccess: #1609: 7: Success after binutils: 78 commits new c374b1db9 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new fee1edc81 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 451bf4ba6 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 10cb6e544 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new ea62c7123 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 5757e1e9d 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 04b6801f9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...]

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 (f752500b5) \ 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 1864 -> 1624 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 29812 -> 29840 bytes 05-build_abe-stage1/console.log.xz | Bin 90960 -> 90672 bytes 07-build_abe-linux/console.log.xz | Bin 8596 -> 8672 bytes 08-build_abe-glibc/console.log.xz | Bin 233584 -> 233540 bytes 09-build_abe-stage2/console.log.xz | Bin 223780 -> 226552 bytes 10-build_abe-gdb/console.log.xz | Bin 37268 -> 37112 bytes 11-build_abe-qemu/console.log.xz | Bin 31248 -> 31664 bytes 12-check_regression/console.log.xz | Bin 2136 -> 2148 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++------- 17 files changed, 47 insertions(+), 47 deletions(-)