This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts.

discards 2bfc5fb8c4 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 14b1fdfccf 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards f563ea4455 98: force: #504: 6: Success after gcc: 18 commits discards 0b9a3911a1 97: onsuccess: #503: 6: Success after linux: 11 commits discards 25117f11f1 96: onsuccess: #502: 6: Success after glibc: 10 commits discards ae2a7d7978 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 8cf82c969e 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 8a7a4ad471 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards a1e51e508f 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards 218812679c 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 91e72b8d2e 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 5596ae8c4f 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards b56e2e79f0 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards c360160b57 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards bd994b3d0f 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards 01e208baa0 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards 8291c58f53 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards f7ea9aaee9 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards b29456916b 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards 128b779cfe 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 9d02d82a56 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 909836dfbe 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 131d5eb349 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards c314ecdb45 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards fdf95c34fb 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 719a95e8e8 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 15961b2147 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 3f7827b818 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards aa9587ab4b 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 518d965597 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 9ddbf2e8a2 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards 51dcc4424a 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 5886976202 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards 9b4e0f14d3 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards e9404eb8bf 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 4055ad88d0 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards a7ce9ac3b6 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 19b7782e36 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards d67a5603e6 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 793a22838b 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards e4f207bdf0 60: onsuccess: #463: 1: Success after gcc: 10 commits discards f1506ed8ff 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 3919576e50 58: force: #461: 6: Success after gcc: 29 commits discards 7a7e6ffd7d 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 8df5d73f10 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards 86228eecdb 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards c8e037b8a4 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards df6258b593 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] discards bb8a20f4fc 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] discards 71d64753a5 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] discards 25a50791bf 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] discards 6210273956 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards fb2610c6dc 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] discards edbe2fe2dc 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] discards f0c02329d8 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards 59d594a1c2 45: onsuccess: #446: 4: Success after gcc: 13 commits discards 5823efc2d6 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] discards 4510f4fb35 43: force: #444: 6: Success after gcc: 5 commits discards 02fb436136 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] discards d843c9fca6 41: onsuccess: #442: 6: Success after glibc: 3 commits discards 2bd87a415f 40: onsuccess: #440: 6: Success after binutils: 11 commits discards a05bd78478 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] discards 4f9ffd41fd 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards 35ab502765 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] discards c0a5db009e 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] discards e017958d12 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] discards 80669532a6 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] discards e6b058ce29 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] discards 01750041d8 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] discards 2249b86c84 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] discards 7b90f72c96 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] discards 6c504fd6fa 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits discards b053bd62cf 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 784d40604b 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards fd90ab5fce 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 7d9ad6502a 25: onsuccess: 6: Successful build after linux: 72 commits discards dd39516c06 24: onsuccess: 6: Successful build after binutils: Automatic [...] discards 9212996475 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards c1d6f5abe9 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards eaa37531b9 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 0eb15b25a3 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards adefc26215 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 9c68c4567a 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards ff29b98175 17: force: 6: Successful build after gcc: 17 commits discards cfe0082002 16: onsuccess: 6: Successful build after binutils: 4 commits discards 6baf1aafb9 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 6f2c803c34 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 378856bc65 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 74e2ab0547 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ebe971810d 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ae60f82a44 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 5903a0b685 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] discards 352a3384c5 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] discards f026e3bd10 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 851efeb079 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards c28fe324c4 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards b565688c89 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards ae23ed4f1c 3: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 680f15a16a 2: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 2108972d75 1: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 5f25a9080c 0: update: binutils-gcc-linux-glibc-gdb: 6 new 246c29e001 0: update: binutils-gcc-linux-glibc-gdb: 6 new ff55e858fa 1: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 83aa8a5d75 2: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 903a240e59 3: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 8c29c674c8 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new ffff465212 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new f4e1382321 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 568d786742 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 2508b55f29 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] new e9ba089eb3 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] new e56d74a9a4 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new ff33dd354f 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new a201676c27 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 012408440a 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 078045d35e 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new b0ee6b007e 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new ee15106624 16: onsuccess: 6: Successful build after binutils: 4 commits new a1b93b588e 17: force: 6: Successful build after gcc: 17 commits new dc5e28e937 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new cec6e1d97a 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 2f6507c78d 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 91263bc532 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new cdc1c2c2f1 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new eb210fe977 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new e82b78bca4 24: onsuccess: 6: Successful build after binutils: Automatic [...] new c6494ddf6f 25: onsuccess: 6: Successful build after linux: 72 commits new a2c62efcde 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new ac85e58e16 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new a681904b4d 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 5fbf64d236 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits new 2e17caee66 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] new 30179f64c0 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] new bea7958df4 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] new c3e89ac92d 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] new 722050c752 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] new 2ba3c51300 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] new 996c084bd6 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] new 3cef349261 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] new fd532fd4b4 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new 659059b8b8 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] new bbd6f006fd 40: onsuccess: #440: 6: Success after binutils: 11 commits new d92704fc98 41: onsuccess: #442: 6: Success after glibc: 3 commits new dcc9681ce0 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] new 78be1a42b1 43: force: #444: 6: Success after gcc: 5 commits new 0e9c931fe5 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] new 783e91a695 45: onsuccess: #446: 4: Success after gcc: 13 commits new 8fbf1e2658 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 314bb2e01d 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] new 7691755b1c 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] new 97fc966988 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new 367d7f966e 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 544901c16c 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] new 9a06121465 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] new 982be794e8 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] new ca57f91331 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new d63ebbc12b 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new e71ffeeaa6 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new cea824a6e5 57: onsuccess: #459: 6: Success after binutils: 8 commits new 4995705bfe 58: force: #461: 6: Success after gcc: 29 commits new c11414b821 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new f82cbad2dc 60: onsuccess: #463: 1: Success after gcc: 10 commits new 9330a44379 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new 7e7a2885db 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new faf23fae03 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 63f9446d5a 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 06e21f6128 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new c2216ab664 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 6e5bf23958 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 5850e12efa 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new f7198fe885 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new a948633db1 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new a7db81744b 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 731efe9fa3 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 878ce05df1 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 44f079508c 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 0c67b486c0 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 819346a021 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new a846ffa4f4 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new a1a3a49ec4 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new c2c4d20bb5 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new d5ecb12772 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 300131b7b4 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 9c5fc7c95c 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 4adfb42ad2 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 0f22c6e441 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new 86a4e925ca 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new b9f94a54da 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 46333fe723 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 45406d79f8 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 6ff9da796e 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 85c842f461 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new f80f25dce9 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 583e0103a7 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new d44a302091 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 676d442865 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 866246d132 95: onsuccess: #500: 6: Success after binutils: 8 commits new 00c9a4abfa 96: onsuccess: #502: 6: Success after glibc: 10 commits new 2fcbdc86c5 97: onsuccess: #503: 6: Success after linux: 11 commits new 97c1dc0806 98: force: #504: 6: Success after gcc: 18 commits new 3f83def636 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 0001559d58 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 6512e95fcb 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...]

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 (2bfc5fb8c4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]

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 1632 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 51152 -> 51312 bytes 05-build_abe-gcc/console.log.xz | Bin 232900 -> 235384 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8968 -> 8500 bytes 08-build_abe-glibc/console.log.xz | Bin 190604 -> 191504 bytes 10-check_regression/console.log.xz | Bin 2216 -> 4260 bytes 10-check_regression/mail-body.txt | 7 ------ 11-update_baseline/console.log | 40 +++++++++++++++++++++++++++++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 9 +------- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++++++++------------ 19 files changed, 65 insertions(+), 35 deletions(-)