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 fba4efc334 113: onsuccess: #522: 1: Success after gcc: 12 commits discards e4a4ef5813 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 76c857a454 111: force: #520: 6: Success after gcc: 9 commits discards 4315c4b471 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 439d92140f 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 72017cbeb4 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 97eb1afe49 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards fd66439216 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 15ada7b8c2 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards c3b6abbedb 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 91f86388f2 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 5c925bbd1c 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 93a0273356 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards cb1bc97903 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 02e85ad007 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards 8f98482a11 98: force: #504: 6: Success after gcc: 18 commits discards 322a9fbfd4 97: onsuccess: #503: 6: Success after linux: 11 commits discards edac4e1e1a 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 61d385dc58 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 15ca7eee12 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards dce4239380 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards deaee26b7e 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards 2c80fd2c8a 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 256340d09a 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 0b957a6b0f 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 1c1dd2072b 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 1be033677a 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards ff4e2a2647 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards 20727e7ce9 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards e20418c4b0 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 48041f07cb 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 71ac556563 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards 15befa130b 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards d26c00801c 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 1fee07494f 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 3cf6670dd4 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 44bb01c7e8 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 99c9a8326c 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 788db2aa66 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 33268e4d89 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 9e563b40d4 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards f48aee258b 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 4ddcbada14 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 24c4ff5491 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards de5366742f 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 001b2abc71 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards 62a2557f8a 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 0e8290c2e8 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 6a79b38e88 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 048af2a0c1 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 3b95b2488f 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards be061a81cd 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 0b1a9e7f19 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 830dbf56a6 60: onsuccess: #463: 1: Success after gcc: 10 commits discards 5a4253f468 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 44008c7623 58: force: #461: 6: Success after gcc: 29 commits discards a908db59bc 57: onsuccess: #459: 6: Success after binutils: 8 commits discards af2c80eacc 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards 9cea937500 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards fd58b27455 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards 3a3beffd8e 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] discards 0001021101 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] discards 36bba15127 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] discards 7761766a22 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] discards e218a407a9 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 26cfee426d 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] discards 6112b0ec71 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] discards 6ec06ea138 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards abd60e2a55 45: onsuccess: #446: 4: Success after gcc: 13 commits discards 7b74b330d0 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] discards 59b64db436 43: force: #444: 6: Success after gcc: 5 commits discards f495bafbfd 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] discards a460763439 41: onsuccess: #442: 6: Success after glibc: 3 commits discards 2609ba6e1d 40: onsuccess: #440: 6: Success after binutils: 11 commits discards 0e5a463521 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] discards 17abe693a9 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards abae710733 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] discards 5dc61332b2 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] discards 017fc3b71c 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] discards 592931d329 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] discards 6deb182aed 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] discards e18765b4ad 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] discards fb12d4d367 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] discards b2f1dc82e8 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] discards 2e526ca18e 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits discards 65f1bd7447 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards fd83cc3b22 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 0a5c16d578 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards cfbeefb831 25: onsuccess: 6: Successful build after linux: 72 commits discards b4fb1aef30 24: onsuccess: 6: Successful build after binutils: Automatic [...] discards 980de14568 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 2c28566753 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards b725e6f190 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 7d6d10ce02 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 921674f06c 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 0cd3d6a6c2 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards aa14e2060c 17: force: 6: Successful build after gcc: 17 commits discards 515ac0eb7a 16: onsuccess: 6: Successful build after binutils: 4 commits discards 2eabf008a9 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards c4e94548e6 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 774b6357e0 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 339d80dde9 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 8a880b6b87 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 5b09a4db94 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 9beec6ae8c 16: onsuccess: 6: Successful build after binutils: 4 commits new 83d96a5ae2 17: force: 6: Successful build after gcc: 17 commits new fb9fc124ce 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 91296925b4 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new e61bb78fb4 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new edd10c2ad0 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new e11b85cfa1 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 30fda77d3a 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 660e47d8cc 24: onsuccess: 6: Successful build after binutils: Automatic [...] new 349cacc41c 25: onsuccess: 6: Successful build after linux: 72 commits new 8e42f0ce95 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 1674d17cc6 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new e88723a9a7 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 46b4b9609d 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits new ea54d04fbc 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] new 0e7669bced 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] new 533a36d942 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] new 0f33b5265e 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] new 959cf371fc 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] new a34ecb6e59 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] new 9308b7fdd0 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] new 584fc33dc0 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] new 8699e2242d 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new db6219ee5a 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] new a5ddefb4e4 40: onsuccess: #440: 6: Success after binutils: 11 commits new 078faf6de3 41: onsuccess: #442: 6: Success after glibc: 3 commits new f4ff838564 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] new 2cf8463795 43: force: #444: 6: Success after gcc: 5 commits new 6a7e11c1f3 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] new 0b841e32fb 45: onsuccess: #446: 4: Success after gcc: 13 commits new cafbcacb31 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 4e277a6339 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] new a699f29a2a 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] new 30c4791ed8 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new f03b737c20 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 4e7f9ce8f0 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] new b761432790 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] new 930be0fd7a 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] new c8434bd5e3 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 79da96bbfe 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new 7ac6c98095 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new 1c21919dfa 57: onsuccess: #459: 6: Success after binutils: 8 commits new dc26c953c7 58: force: #461: 6: Success after gcc: 29 commits new 2ff83110c5 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new c07d87c762 60: onsuccess: #463: 1: Success after gcc: 10 commits new cf6befaf22 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new 8ef1941dbc 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 351a405cc4 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 1694f04206 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 8d1a0fb166 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new cb0194a52d 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 67fe81e87c 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 00c6ff2e48 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new 4d94d40849 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 5e7964d70c 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 1a7a645c3b 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 57f525c9b7 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 3fdee50343 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new eee26ade56 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 691efbd708 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 61001ea0d5 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new a3c228edba 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new c82d5127e6 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 8dac13262a 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new 0ad4269073 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 049c711f3d 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new b6eac8fcf1 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new e85bdca967 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 2e407adc21 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new cb2cca16e3 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 0ad62ead81 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 12bf8624ba 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 3776794f68 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new ab4de7bef7 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 42b2f1d8dc 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 59e29c9189 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new b828357e23 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new 46f01b5aba 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 7928c6df0c 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 5e2a686c1f 95: onsuccess: #500: 6: Success after binutils: 8 commits new fa4fc52328 96: onsuccess: #502: 6: Success after glibc: 10 commits new fdd083b96a 97: onsuccess: #503: 6: Success after linux: 11 commits new c94efb5f70 98: force: #504: 6: Success after gcc: 18 commits new 71a506530a 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 8ff5bd0758 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 490fa7325f 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new d746edd9d9 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new dff3d7d5a1 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 25058c6058 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 50b4b40ab0 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new b0c2650d4c 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 8cf79f5fe2 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 7ba0662b5b 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 076f887cde 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new e836bd4170 110: onsuccess: #518: 6: Success after binutils: 5 commits new e97dda9c8c 111: force: #520: 6: Success after gcc: 9 commits new 7a1ee76184 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new f7beb6b51b 113: onsuccess: #522: 1: Success after gcc: 12 commits new 02030fca21 114: onsuccess: #523: 1: Success after binutils/gcc: 18 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 (fba4efc334) \ 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 1920 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51112 -> 51464 bytes 05-build_abe-gcc/console.log.xz | Bin 233224 -> 213288 bytes 10-check_regression/console.log.xz | Bin 2688 -> 3432 bytes 10-check_regression/mail-body.txt | 9 ----- 11-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 +------ mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++++----- 14 files changed, 50 insertions(+), 64 deletions(-)