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 6512e95fcb 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards 0001559d58 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 3f83def636 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards 97c1dc0806 98: force: #504: 6: Success after gcc: 18 commits discards 2fcbdc86c5 97: onsuccess: #503: 6: Success after linux: 11 commits discards 00c9a4abfa 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 866246d132 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 676d442865 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards d44a302091 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 583e0103a7 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards f80f25dce9 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 85c842f461 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 6ff9da796e 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 45406d79f8 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 46333fe723 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards b9f94a54da 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards 86a4e925ca 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards 0f22c6e441 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 4adfb42ad2 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 9c5fc7c95c 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards 300131b7b4 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards d5ecb12772 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards c2c4d20bb5 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards a1a3a49ec4 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards a846ffa4f4 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 819346a021 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 0c67b486c0 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 44f079508c 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 878ce05df1 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 731efe9fa3 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards a7db81744b 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards a948633db1 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards f7198fe885 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 5850e12efa 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards 6e5bf23958 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards c2216ab664 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 06e21f6128 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 63f9446d5a 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards faf23fae03 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards 7e7a2885db 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 9330a44379 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards f82cbad2dc 60: onsuccess: #463: 1: Success after gcc: 10 commits discards c11414b821 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 4995705bfe 58: force: #461: 6: Success after gcc: 29 commits discards cea824a6e5 57: onsuccess: #459: 6: Success after binutils: 8 commits discards e71ffeeaa6 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards d63ebbc12b 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards ca57f91331 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards 982be794e8 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] discards 9a06121465 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] discards 544901c16c 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] discards 367d7f966e 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] discards 97fc966988 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 7691755b1c 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] discards 314bb2e01d 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] discards 8fbf1e2658 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards 783e91a695 45: onsuccess: #446: 4: Success after gcc: 13 commits discards 0e9c931fe5 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] discards 78be1a42b1 43: force: #444: 6: Success after gcc: 5 commits discards dcc9681ce0 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] discards d92704fc98 41: onsuccess: #442: 6: Success after glibc: 3 commits discards bbd6f006fd 40: onsuccess: #440: 6: Success after binutils: 11 commits discards 659059b8b8 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] discards fd532fd4b4 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards 3cef349261 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] discards 996c084bd6 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] discards 2ba3c51300 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] discards 722050c752 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] discards c3e89ac92d 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] discards bea7958df4 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] discards 30179f64c0 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] discards 2e17caee66 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] discards 5fbf64d236 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits discards a681904b4d 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards ac85e58e16 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards a2c62efcde 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards c6494ddf6f 25: onsuccess: 6: Successful build after linux: 72 commits discards e82b78bca4 24: onsuccess: 6: Successful build after binutils: Automatic [...] discards eb210fe977 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards cdc1c2c2f1 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 91263bc532 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 2f6507c78d 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards cec6e1d97a 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards dc5e28e937 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards a1b93b588e 17: force: 6: Successful build after gcc: 17 commits discards ee15106624 16: onsuccess: 6: Successful build after binutils: 4 commits discards b0ee6b007e 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 078045d35e 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 012408440a 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards a201676c27 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ff33dd354f 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards e56d74a9a4 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards e9ba089eb3 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] discards 2508b55f29 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] discards 568d786742 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards f4e1382321 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards ffff465212 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 8c29c674c8 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 903a240e59 3: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 83aa8a5d75 2: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards ff55e858fa 1: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new d3f1827610 1: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 94c5c53cb0 2: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 28a8146f84 3: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new c32742d07d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new b6664e0540 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 9fca112a32 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new d328ef4cff 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 565fbc76b3 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] new a3ee39440b 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] new ac8388b388 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 9e83d2763c 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 8344584bdd 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 6a4f95cc64 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new b558ed3d88 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new bf08d1bb1d 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 4eb19ef651 16: onsuccess: 6: Successful build after binutils: 4 commits new c4803d189b 17: force: 6: Successful build after gcc: 17 commits new 192fff3a65 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 2c3cc2629b 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 641f011669 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 7deaa37150 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 7d04c678c8 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 040e181c57 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 920a1f6218 24: onsuccess: 6: Successful build after binutils: Automatic [...] new 94a3262dc0 25: onsuccess: 6: Successful build after linux: 72 commits new b48e3d7a4a 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 5a99d573fe 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 9be73e0b70 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new d951061243 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits new a690853ab8 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] new 000a2ab0c8 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] new 2e32e808fd 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] new b26c037c9a 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] new fb674f8274 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] new 7ddafdd4a8 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] new af3625ba94 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] new 15b9cdf05e 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] new 3416d00ad2 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new ac94d8b815 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] new 1199be9a5c 40: onsuccess: #440: 6: Success after binutils: 11 commits new 8041847c4f 41: onsuccess: #442: 6: Success after glibc: 3 commits new 6b45a794a1 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] new 74b8a787a2 43: force: #444: 6: Success after gcc: 5 commits new a0a4c8613b 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] new bb3d10f3ed 45: onsuccess: #446: 4: Success after gcc: 13 commits new 1efcb2cf43 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 34328d1be0 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] new 5775da2abe 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] new 4d90632bdb 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new b85ff4f4e0 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 89c94ef330 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] new 434cfc6e9a 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] new 67d4395156 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] new 45d602531c 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 386a36cbb8 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new 2471118988 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new fdec8361b9 57: onsuccess: #459: 6: Success after binutils: 8 commits new 7081348d2f 58: force: #461: 6: Success after gcc: 29 commits new b544623fb8 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new e2676c3776 60: onsuccess: #463: 1: Success after gcc: 10 commits new 96e5d01faa 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new 35da5a2997 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 8552ce2cfe 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 89411644ea 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 7e0581dbcd 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new db9e522c8b 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 14ee820564 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new bedefcb0f0 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new 1606bc1cee 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new b33a314ad9 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 6f920e3926 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new a00e1595fe 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 493c145395 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 3d5b2e12f3 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new f72540c547 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 107ac60f29 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new ecb8f7f928 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new 6e60d216de 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new d7fefbfc48 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new 0a65bed25f 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 69516cdee0 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 63c5c4475f 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 1cb4bfb8c5 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 544718158d 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new 5bbbb4cb51 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 6bd81d31ce 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new ae40f10909 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 8d71f1d7c1 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 3f9e4e5b73 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new c69d34e90c 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 44259db761 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new b3af13a261 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new 2848bed4dc 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 6cd47415b1 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 1f2da163db 95: onsuccess: #500: 6: Success after binutils: 8 commits new 49e6da8ecd 96: onsuccess: #502: 6: Success after glibc: 10 commits new 2ecb2f0f1f 97: onsuccess: #503: 6: Success after linux: 11 commits new 9887862d47 98: force: #504: 6: Success after gcc: 18 commits new 01926787af 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new b79345db28 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 0906d88f15 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new bca14e5caf 102: onsuccess: #508: 6: 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 (6512e95fcb) \ 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 1676 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 51312 -> 51716 bytes 05-build_abe-gcc/console.log.xz | Bin 235384 -> 232632 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8500 -> 8772 bytes 08-build_abe-glibc/console.log.xz | Bin 191504 -> 235868 bytes 09-build_abe-gdb/console.log.xz | Bin 0 -> 49512 bytes 10-check_regression/console.log.xz | Bin 4260 -> 4608 bytes 10-check_regression/mail-body.txt | 4 ++- 11-update_baseline/console.log | 40 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 + git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 37 ++++++++++--------- results | 4 ++- 23 files changed, 59 insertions(+), 49 deletions(-) create mode 100644 09-build_abe-gdb/console.log.xz create mode 100644 dashboard/squad-vs-first/score/results-functional.json