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 a161de826133 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] discards b5c492b506c3 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] discards 2760ac1af50e 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] discards 35815cf7ef50 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] discards b5afe415d99b 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] discards d293b5f4e327 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] discards dbfca8d2480c 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] discards e2ae72762ca5 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] discards 4b89cd481567 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] discards 2328812e7915 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] discards aa2dadf833e4 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] discards 6ec17b505b8b 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] discards 2d598a1365fe 134: onsuccess: #544: 6: Success after binutils: 18 commits discards fd4b2722ed82 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] discards 570b36795feb 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] discards d595206005ef 131: onsuccess: #540: 6: Success after binutils/gcc/linux/ [...] discards 5c494f510cad 130: onsuccess: #539: 6: Success after binutils/gcc/linux/ [...] discards 9695085e264d 129: onsuccess: #538: 6: Success after binutils/gcc/linux/ [...] discards 9d849e2699b6 128: onsuccess: #537: 6: Success after binutils/gcc/linux/ [...] discards ffd3905869b7 127: onsuccess: #536: 6: Success after binutils/gcc/linux/ [...] discards c72b055ec41b 126: onsuccess: #535: 6: Success after binutils/gcc/linux/ [...] discards 5f75ac6bbdf3 125: onsuccess: #534: 6: Success after binutils/gcc/linux/ [...] discards 1a8c3be7cefb 124: onsuccess: #533: 6: Success after binutils/gcc/linux/ [...] discards 952b78695ee4 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 6 [...] discards a45a5d3a9c18 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 5 [...] discards f13c3e52dd22 121: onsuccess: #530: 6: Success after binutils/gcc/linux/ [...] discards 42e85d8eb045 120: onsuccess: #529: 6: Success after binutils/gcc/linux/ [...] discards 07fb78f461ce 119: onsuccess: #528: 6: Success after binutils/gcc/linux/ [...] discards 10f7993ecf71 118: onsuccess: #527: 6: Success after binutils/gcc/linux/ [...] discards b9b936b9f1ef 117: onsuccess: #526: 6: Success after binutils/gcc/linux/ [...] discards 7c2f87dfb922 116: onsuccess: #525: 6: Success after binutils/gcc/linux/ [...] discards 1861770b731e 115: onsuccess: #524: 6: Success after binutils/gcc/linux/ [...] discards 8899787b0d9e 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 8b3066fa661e 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 73c31ba2d07b 112: force: #521: 1: Failure after basepoints/gcc-13-3918- [...] discards 590033cb4c5d 111: force: #520: 6: Success after gcc: 9 commits discards d8ece500a936 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 9d56386b0393 109: onsuccess: #516: 6: Success after binutils/gcc/linux/ [...] discards 6c588512c31c 108: onsuccess: #514: 6: Success after binutils/gcc/linux/ [...] discards de63159dc909 107: onsuccess: #513: 6: Success after binutils/gcc/linux/ [...] discards ad20b627e173 106: onsuccess: #512: 6: Success after binutils/gcc/linux/ [...] discards 7f60f9f32fe4 105: onsuccess: #511: 6: Success after binutils/gcc/linux/ [...] discards 9492b6b50013 104: onsuccess: #510: 6: Success after binutils/gcc/linux/ [...] discards c11fbcdcca9b 103: onsuccess: #509: 6: Success after binutils/gcc/linux/ [...] discards fa54cfeaa2f5 102: onsuccess: #508: 6: Success after binutils/gcc/linux/ [...] discards 2d978271f0cb 101: onsuccess: #507: 4: Success after binutils/gcc/linux/ [...] discards 61ed04040678 100: onsuccess: #506: 4: Success after baseline build: no [...] discards 933339027077 99: force: #505: 4: Failure after basepoints/gcc-13-3596-g [...] discards df0a80abc18b 98: force: #504: 6: Success after gcc: 18 commits discards 27878db20ea7 97: onsuccess: #503: 6: Success after linux: 11 commits discards 10a1effddedd 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 51da898e225a 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 26a4e7706a76 94: onsuccess: #498: 6: Success after binutils/gcc/linux/g [...] discards 79e52f64ee2c 93: onsuccess: #497: 6: Success after binutils/gcc/linux/g [...] discards 07c739405219 92: onsuccess: #496: 6: Success after binutils/gcc/linux/g [...] discards f423aff38efb 91: onsuccess: #495: 6: Success after binutils/gcc/linux/g [...] discards 9e5e3dc9f333 90: onsuccess: #494: 6: Success after binutils/gcc/linux/g [...] discards be0bde0fdd08 89: onsuccess: #492: 6: Success after binutils/gcc/linux/g [...] discards 44e5c67d22d3 88: onsuccess: #491: 6: Success after binutils/gcc/linux/g [...] discards 95b077709174 87: onsuccess: #490: 6: Success after binutils/gcc/linux/g [...] discards 4e3aee2e72fa 86: onsuccess: #489: 6: Success after binutils/gcc/linux/g [...] discards 4b272b35ac51 85: onsuccess: #488: 6: Success after binutils/gcc/linux/g [...] discards 9e6e6d64fca7 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/g [...] discards 5dd30271b3df 83: onsuccess: #486: 6: Success after binutils/gcc/linux/g [...] discards f81ab2b84c48 82: onsuccess: #485: 6: Success after binutils/gcc/linux/g [...] discards a5c5b15b88ae 81: onsuccess: #484: 6: Success after binutils/gcc/linux/g [...] discards 3bd179cac502 80: onsuccess: #483: 6: Success after binutils/gcc/linux/g [...] discards 8fb3f8f3c1b5 79: onsuccess: #482: 6: Success after binutils/gcc/linux/g [...] discards 89bb337949fa 78: onsuccess: #481: 6: Success after binutils/gcc/linux/g [...] discards 7f4a72984920 77: onsuccess: #480: 6: Success after binutils/gcc/linux/g [...] discards dd62a41e9d51 76: onsuccess: #479: 6: Success after binutils/gcc/linux/g [...] discards cfce0b9cfb68 75: onsuccess: #478: 6: Success after binutils/gcc/linux/g [...] discards 20f5375f65c4 74: onsuccess: #477: 6: Success after binutils/gcc/linux/g [...] discards c1af70472d17 73: onsuccess: #476: 6: Success after binutils/gcc/linux/g [...] discards d4f85ef700cb 72: onsuccess: #475: 6: Success after binutils/gcc/linux/g [...] discards 28c6d90dc98b 71: onsuccess: #474: 6: Success after binutils/gcc/linux/g [...] discards 85d2000b2669 70: onsuccess: #473: 6: Success after binutils/gcc/linux/g [...] discards 7d347084e50a 69: onsuccess: #472: 6: Success after binutils/gcc/linux/g [...] discards 1096afb59761 68: onsuccess: #471: 6: Success after binutils/gcc/linux/g [...] discards e0b6c46189e2 67: onsuccess: #470: 6: Success after binutils/gcc/linux/g [...] discards 5520be962ed9 66: onsuccess: #469: 6: Success after binutils/gcc/linux/g [...] discards 03b8f834a45d 65: onsuccess: #468: 6: Success after binutils/gcc/linux/g [...] discards d94f89af688a 64: onsuccess: #467: 6: Success after binutils/gcc/linux/g [...] discards c77cde854834 63: onsuccess: #466: 6: Success after binutils/gcc/linux/g [...] discards ca9fc794b5c9 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 37557c785b34 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 696fff4d01d4 60: onsuccess: #463: 1: Success after gcc: 10 commits discards cfd1300034d6 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g [...] discards e98b20579165 58: force: #461: 6: Success after gcc: 29 commits discards 68bfedde658e 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 1eb567360751 56: onsuccess: #457: 6: Success after binutils/gcc/linux/g [...] discards 5d9ffd34804a 55: onsuccess: #456: 6: Success after binutils/gcc/linux/g [...] discards e21b62621ac8 54: onsuccess: #455: 6: Success after binutils/gcc/linux/g [...] discards 801591385424 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/g [...] discards 5f5427db81e6 52: onsuccess: #453: 6: Success after binutils/gcc/linux/g [...] discards 1b6bff161845 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/g [...] discards 4af00684b1c6 50: onsuccess: #451: 6: Success after binutils/gcc/linux/g [...] discards 771d17bd64dc 49: onsuccess: #450: 6: Success after binutils/gcc/linux/g [...] discards 3edd9858cfa4 48: onsuccess: #449: 6: Success after binutils/gcc/linux/g [...] discards 0b45e8e219c2 47: onsuccess: #448: 4: Success after binutils/gcc/linux/g [...] discards b96f5f16435c 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 011f4d2f2ca1 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new b3bde94377e2 47: onsuccess: #448: 4: Success after binutils/gcc/linux/g [...] new e01fe4432ba4 48: onsuccess: #449: 6: Success after binutils/gcc/linux/g [...] new 6990b7fea21a 49: onsuccess: #450: 6: Success after binutils/gcc/linux/g [...] new 512c1c89d3d1 50: onsuccess: #451: 6: Success after binutils/gcc/linux/g [...] new 034a830a41b1 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/g [...] new 585e78b56006 52: onsuccess: #453: 6: Success after binutils/gcc/linux/g [...] new fcbc3f1c26e8 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/g [...] new 49e8198d2e8a 54: onsuccess: #455: 6: Success after binutils/gcc/linux/g [...] new 7c2bcb049ea2 55: onsuccess: #456: 6: Success after binutils/gcc/linux/g [...] new 195aed212859 56: onsuccess: #457: 6: Success after binutils/gcc/linux/g [...] new 744581f4190d 57: onsuccess: #459: 6: Success after binutils: 8 commits new 6ce9480eb8e1 58: force: #461: 6: Success after gcc: 29 commits new 69f83cb43c7c 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g [...] new 83fb17a90d1e 60: onsuccess: #463: 1: Success after gcc: 10 commits new b12467a9c5d0 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new 9c51bae5492e 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 08e684a56ea4 63: onsuccess: #466: 6: Success after binutils/gcc/linux/g [...] new 641625edfcce 64: onsuccess: #467: 6: Success after binutils/gcc/linux/g [...] new 70030b49feb5 65: onsuccess: #468: 6: Success after binutils/gcc/linux/g [...] new c2e8c7cb2581 66: onsuccess: #469: 6: Success after binutils/gcc/linux/g [...] new f4b519662ac9 67: onsuccess: #470: 6: Success after binutils/gcc/linux/g [...] new ff5659e79952 68: onsuccess: #471: 6: Success after binutils/gcc/linux/g [...] new 5b8c50c9ff0e 69: onsuccess: #472: 6: Success after binutils/gcc/linux/g [...] new d31b854d9e67 70: onsuccess: #473: 6: Success after binutils/gcc/linux/g [...] new 7fe30ab8dcf2 71: onsuccess: #474: 6: Success after binutils/gcc/linux/g [...] new 4d4768d8246d 72: onsuccess: #475: 6: Success after binutils/gcc/linux/g [...] new 807834c28113 73: onsuccess: #476: 6: Success after binutils/gcc/linux/g [...] new fd50079c22da 74: onsuccess: #477: 6: Success after binutils/gcc/linux/g [...] new d290d15b4821 75: onsuccess: #478: 6: Success after binutils/gcc/linux/g [...] new 85789c0710b6 76: onsuccess: #479: 6: Success after binutils/gcc/linux/g [...] new 93920dd719bf 77: onsuccess: #480: 6: Success after binutils/gcc/linux/g [...] new 07aff758daaa 78: onsuccess: #481: 6: Success after binutils/gcc/linux/g [...] new fae214b709ed 79: onsuccess: #482: 6: Success after binutils/gcc/linux/g [...] new a103959186c1 80: onsuccess: #483: 6: Success after binutils/gcc/linux/g [...] new 5e5435c5cf29 81: onsuccess: #484: 6: Success after binutils/gcc/linux/g [...] new 7012d9fbe1f1 82: onsuccess: #485: 6: Success after binutils/gcc/linux/g [...] new d95cd834d806 83: onsuccess: #486: 6: Success after binutils/gcc/linux/g [...] new 8630d33b4cb8 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/g [...] new dfe13cb9ea64 85: onsuccess: #488: 6: Success after binutils/gcc/linux/g [...] new a9871fb0cade 86: onsuccess: #489: 6: Success after binutils/gcc/linux/g [...] new ae448f119376 87: onsuccess: #490: 6: Success after binutils/gcc/linux/g [...] new 879017bd283e 88: onsuccess: #491: 6: Success after binutils/gcc/linux/g [...] new cb9e2beeb10e 89: onsuccess: #492: 6: Success after binutils/gcc/linux/g [...] new aeff345310c1 90: onsuccess: #494: 6: Success after binutils/gcc/linux/g [...] new 2e6a99c952a6 91: onsuccess: #495: 6: Success after binutils/gcc/linux/g [...] new e6ebd105a1ef 92: onsuccess: #496: 6: Success after binutils/gcc/linux/g [...] new 8cbe14d352e2 93: onsuccess: #497: 6: Success after binutils/gcc/linux/g [...] new e047fa619927 94: onsuccess: #498: 6: Success after binutils/gcc/linux/g [...] new a3b79be133c4 95: onsuccess: #500: 6: Success after binutils: 8 commits new 4fd55816dc51 96: onsuccess: #502: 6: Success after glibc: 10 commits new 970274ddf4ac 97: onsuccess: #503: 6: Success after linux: 11 commits new 883abf2a3f02 98: force: #504: 6: Success after gcc: 18 commits new a6025b09e7ab 99: force: #505: 4: Failure after basepoints/gcc-13-3596-g [...] new 6e3745a18b31 100: onsuccess: #506: 4: Success after baseline build: no [...] new 29691072c8c0 101: onsuccess: #507: 4: Success after binutils/gcc/linux/ [...] new 4782eff0dd15 102: onsuccess: #508: 6: Success after binutils/gcc/linux/ [...] new 9b59e8926a04 103: onsuccess: #509: 6: Success after binutils/gcc/linux/ [...] new d2a41764d7a9 104: onsuccess: #510: 6: Success after binutils/gcc/linux/ [...] new 5a53c196ed26 105: onsuccess: #511: 6: Success after binutils/gcc/linux/ [...] new ddb98da8c69a 106: onsuccess: #512: 6: Success after binutils/gcc/linux/ [...] new 10573204c289 107: onsuccess: #513: 6: Success after binutils/gcc/linux/ [...] new 284a66d4251b 108: onsuccess: #514: 6: Success after binutils/gcc/linux/ [...] new b846077a29ea 109: onsuccess: #516: 6: Success after binutils/gcc/linux/ [...] new 2c727b0750c3 110: onsuccess: #518: 6: Success after binutils: 5 commits new dedb9d497d5f 111: force: #520: 6: Success after gcc: 9 commits new 152c3e2a2bad 112: force: #521: 1: Failure after basepoints/gcc-13-3918- [...] new 1926c832bb79 113: onsuccess: #522: 1: Success after gcc: 12 commits new c72a2f228489 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 4cd35a2246fe 115: onsuccess: #524: 6: Success after binutils/gcc/linux/ [...] new 3b2d9270a276 116: onsuccess: #525: 6: Success after binutils/gcc/linux/ [...] new ea6c1c9f412c 117: onsuccess: #526: 6: Success after binutils/gcc/linux/ [...] new ca8920b96186 118: onsuccess: #527: 6: Success after binutils/gcc/linux/ [...] new ad62f990e061 119: onsuccess: #528: 6: Success after binutils/gcc/linux/ [...] new 45a566e990fe 120: onsuccess: #529: 6: Success after binutils/gcc/linux/ [...] new b9feeb23f3e1 121: onsuccess: #530: 6: Success after binutils/gcc/linux/ [...] new ec90b9120b67 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 5 [...] new a4e9aa0b18a3 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 6 [...] new 71c0345972ab 124: onsuccess: #533: 6: Success after binutils/gcc/linux/ [...] new 8e593a6c5de5 125: onsuccess: #534: 6: Success after binutils/gcc/linux/ [...] new df9f036b32d6 126: onsuccess: #535: 6: Success after binutils/gcc/linux/ [...] new 23e7211849bf 127: onsuccess: #536: 6: Success after binutils/gcc/linux/ [...] new c181e40bea89 128: onsuccess: #537: 6: Success after binutils/gcc/linux/ [...] new 4f6713d457fa 129: onsuccess: #538: 6: Success after binutils/gcc/linux/ [...] new fab9f03a138d 130: onsuccess: #539: 6: Success after binutils/gcc/linux/ [...] new 606e3ead8837 131: onsuccess: #540: 6: Success after binutils/gcc/linux/ [...] new 2d033a5e5cf0 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] new 63e14631f22f 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] new 14007b01cc48 134: onsuccess: #544: 6: Success after binutils: 18 commits new 08d7dea27450 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] new ca28d8036837 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] new 3449a9d133a1 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] new f3bd9ca0f09d 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] new e28e4242871c 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] new cdb37f801c1b 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] new c9aba1550b67 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] new 080d1e57f0a0 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] new d24ca39d1531 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] new 5c72f237e7a6 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] new 7e88f768e055 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] new 120b3c525a96 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] new e2e2fcfd96a0 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...]
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 (a161de826133) \ 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 1712 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 52684 -> 53556 bytes 05-build_abe-gcc/console.log.xz | Bin 233924 -> 235212 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8600 -> 9076 bytes 08-build_abe-glibc/console.log.xz | Bin 234784 -> 236736 bytes 09-build_abe-gdb/console.log.xz | Bin 51760 -> 52196 bytes 10-check_regression/console.log.xz | Bin 3600 -> 4456 bytes 11-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 20 files changed, 59 insertions(+), 59 deletions(-)