Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (b21e5c2525c -> 7a40f8dc8fa)

by git＠git.linaro.org

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-aarch64 in repository toolchain/ci/base-artifacts. discards b21e5c2525c 142: force: #565: 6: Success after gcc: 8 commits discards 18a600b52ce 141: onsuccess: #564: 6: Success after linux: 3224 commits discards b9afec2a7f1 140: onsuccess: #563: 6: Success after glibc: 2 commits discards 12d220b6d1b 139: onsuccess: #561: 6: Success after binutils: 23 commits discards 9b43b19310b 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards 9c236977fd8 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards b7eb5c761ef 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards 2cb24f3eca8 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards d46858222df 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards 3490045bc00 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 3ee94fd89bd 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] discards 2cd1e6c10ec 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] discards 90a2bd5918c 130: force: #551: 6: Success after gcc: 10 commits discards e6fe894cade 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 00f144f9b2f 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards a9c0b2dba8e 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards 3caa0344cf1 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards 61ce8b267ee 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 59b80a689f0 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 5286a159cb4 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards df2b9542986 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards b33f1ed7a5d 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 3f4243a5bb5 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 631a36f2710 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards fa48f0b0008 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 6292b524c7a 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards 2ec27f987a2 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards 89dd0f406d6 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards ec1e9cfa15c 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards 6f7ea1be6eb 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards 727ca784d4d 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards d98660f4075 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards bbee52610db 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 91ce102d741 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 4d4f949e032 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards c9a66d5f981 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 148a6ce8426 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 884133d06a0 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 7678ea60f26 104: force: #522: 6: Success after gcc: 24 commits discards 4451bf01d66 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 1e0d0bf691a 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards a9cb57c03f5 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards fcac0a0c367 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards 4aba94fd3bf 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 8de5fdcf140 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards ecbd45461f4 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 96d6e514c2b 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 8bbdd313b34 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards 1bc59a8ab02 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 4d33bc81996 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards f5ba8b8e273 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards d1cb0466040 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards 9e430204aee 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards 3d11e2e0fad 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards 6955328ad0e 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards 8098a6fabf2 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards 0fc43657589 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 2076fcc4986 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 2b75fc8fd3c 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 47a46852ddb 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards 2cdb96a1ad8 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards 844e3b6abe7 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards 76031d3a5f3 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards cc806817ea6 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards ffa88f392ef 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards f5dacb34c36 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards 0f1ea8a53ea 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards adb9c784eba 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 615f22f6560 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards c761d7b57b1 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards d9d236dda58 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 759c8756b16 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards 4ebf399dede 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 0c03cb85867 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards f871f7ad6d6 68: force: #484: 6: Success after gdb: 6 commits discards 57713bc9a5d 67: onsuccess: #483: 6: Success after linux: 384 commits discards bed7e167c95 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 5b7e8da4617 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 84c783cac6d 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 753fce6dd71 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 9c1eecfe0b4 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 567023db127 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 58257ee7d24 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards 095b51f97aa 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 57c48000856 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards a5d9f327f8b 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 410ea382a03 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards 59993ca7207 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards bb044a7329b 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards 24f21ee7a1e 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards 208e9e3879f 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 847ff5f97fd 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 84d4b61505f 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 63ce37552e3 49: force: #463: 6: Success after gcc: 18 commits discards 73a4535ff8e 48: onsuccess: #461: 6: Success after binutils: 10 commits discards b1ce8c16e1d 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards 0abc918ca9a 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards 48fdf74759d 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards a61749c0a49 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards 1d34dd1d7fa 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 02ed27ac3d4 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new a5d04c78bd9 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new 013e191f1e8 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new 21ca62f666d 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new 4651491e823 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new b4352d9f81b 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 3e9c46ad086 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 63441230beb 48: onsuccess: #461: 6: Success after binutils: 10 commits new 5eb6614913f 49: force: #463: 6: Success after gcc: 18 commits new 06be5289910 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new 885a0107f2b 51: onsuccess: #465: 1: Success after gcc: 10 commits new da965502904 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 6b56f13bd88 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new a8ba5bba6c6 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 755c6722f2f 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 391962dcd91 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new 40de539abc3 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new bc744cdf378 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new 7da71fa75c5 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 7ba10ac7384 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new a670f5bc216 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new ab7f6ca1c2b 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 33a2ec80955 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new 8c3971515fa 64: onsuccess: #479: 6: Success after binutils: 14 commits new a520a4018ad 65: onsuccess: #480: 6: Success after gcc: 12 commits new 198bae50534 66: onsuccess: #482: 6: Success after glibc: 2 commits new ffa411f2f11 67: onsuccess: #483: 6: Success after linux: 384 commits new 88b65574a4c 68: force: #484: 6: Success after gdb: 6 commits new 4695f0a206f 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new 8c7d6997f42 70: onsuccess: #486: 5: Success after gdb: 7 commits new e240223d15b 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 1c8d2a0bae6 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new 035b31255fc 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new 7e52c2d51d3 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new 4ba95a7a5f9 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new aa5c2ce6324 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new a495156938f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 8349696df4c 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new 01b3de8079c 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new f480135fcb1 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new 6b9156dd779 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new f51c79504fe 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 2d830fae5be 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 1e99b06b351 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new d6d22cc2b1a 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new 69a6df4253f 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new b19d9c803dc 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new 9d2f7f58489 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new ce1171ec436 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 17473e95fe3 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new e42eec3900d 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new 727f3a85106 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 2c6b8b6aca9 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new c74909ca0a6 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new b5533ac00d0 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new ed235fa9d3b 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new eab6fff9952 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new 020a822379e 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 0ce5cc87561 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 65e3469f0fb 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new af1c5848502 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new f36cd1a63a1 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new 6648e07f7a2 103: onsuccess: #520: 6: Success after binutils: 10 commits new e33e1df37a0 104: force: #522: 6: Success after gcc: 24 commits new f1a5d84d3ce 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new f6b83fb1498 106: onsuccess: #524: 1: Success after gcc: 11 commits new e3b2c590b64 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 6ae17aeceec 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 5e52d8aac52 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new b3e35563c40 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new 61a16e0a7e5 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new be67d85a0aa 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 603125501f0 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new 8a5b7830f8d 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new 70fb08e866e 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new e4204655af4 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new 4c47005e701 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new b133814ec69 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 11472b1792b 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 4b5a3637cbc 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 7c6ce7054c0 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 99bb754d61f 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 26a60fdc41c 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 2437b1d1222 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 958ed3c8974 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new ad2067fefa0 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new a521cc5ef3f 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new fd2db5076f1 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new 21b59ed6335 129: onsuccess: #548: 6: Success after binutils: 8 commits new 3d603a3146e 130: force: #551: 6: Success after gcc: 10 commits new 1f4de2a27a3 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] new 351951aedd7 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] new 55d9c4e8c57 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 8f73bdf5b02 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 166c41509e6 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 719ce68851b 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new ce3b1d130c8 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new da1d5ef1aa6 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new e89b4a9f8b1 139: onsuccess: #561: 6: Success after binutils: 23 commits new cf8f84daa16 140: onsuccess: #563: 6: Success after glibc: 2 commits new 07517a82600 141: onsuccess: #564: 6: Success after linux: 3224 commits new b5af1592b53 142: force: #565: 6: Success after gcc: 8 commits new 7a40f8dc8fa 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g [...] 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 (b21e5c2525c) \ 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 1660 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 39620 -> 40396 bytes 05-build_abe-gcc/console.log.xz | Bin 215000 -> 217712 bytes 07-build_abe-linux/console.log.xz | Bin 9532 -> 9524 bytes 08-build_abe-glibc/console.log.xz | Bin 245712 -> 171108 bytes 09-build_abe-gdb/console.log.xz | Bin 39872 -> 0 bytes 10-check_regression/console.log.xz | Bin 2988 -> 3640 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 13 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 7 + 10-check_regression/trigger-bisect | 2 + 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 40 +-- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 312 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +- results | 11 +- 28 files changed, 390 insertions(+), 49 deletions(-) delete mode 100644 09-build_abe-gdb/console.log.xz create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/trigger-bisect create mode 100644 10-check_regression/trigger-notify delete mode 100644 dashboard/squad-vs-first/score/results-functional.json create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/interesting-commits] branch master updated (cc8f038c -> aaf5d0a1)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from cc8f038c Add entry ac2d7fa9084892c2c1232016ecdeadf4b354212f from https [...] new aaf5d0a1 Add entry 17ae956c0fa6baac3d22764019d5dd5ebf5c2b11 from https [...] The 1 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: gcc/basepoints/gcc-13-4618-g17ae956c0fa | 1 + .../tcwg_gnu_native_build/master-aarch64/build_url | 2 +- .../tcwg_gnu_native_build/master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 1 + .../tcwg_gnu_native_build/status.txt | 71 ++++++++++++++++++++++ 5 files changed, 75 insertions(+), 1 deletion(-) create mode 120000 gcc/basepoints/gcc-13-4618-g17ae956c0fa copy gcc/sha1/{4500baaccb6e4d696e223c338bbdf7705c3646dd => 17ae956c0fa6baac3d22764 [...] create mode 100644 gcc/sha1/17ae956c0fa6baac3d22764019d5dd5ebf5c2b11/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/17ae956c0fa6baac3d22764019d5dd5ebf5c2b11/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/17ae956c0fa6baac3d22764019d5dd5ebf5c2b11/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (1bf337caba9 -> ea6929aaac3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 1bf337caba9 gold: Remove BND from 64-bit x86-64 IBT PLT new ea6929aaac3 [gdb/tdep] Fix s390_linux_nat_target::stopped_by_watchpoint The 1 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: gdb/s390-linux-nat.c | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan updated (755d388204b -> 9157a1df181)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan in repository toolchain/ci/base-artifacts. discards 755d388204b 134: onsuccess: #556: 1: Success after binutils/gcc: 44 commits discards 6e52ac8e5e6 133: onsuccess: #555: 1: Success after binutils/gcc: 27 commits discards c07c02e3b10 132: onsuccess: #554: 1: Success after gcc: 36 commits discards 5b0d04a2169 131: force: #553: 1: Failure after gcc: 10 commits discards 0e536521521 130: onsuccess: #549: 2: Success after binutils: 14 commits discards 28152bce88e 129: onsuccess: #546: 2: Success after binutils/gcc: 31 commits discards 5b49b655fe0 128: onsuccess: #545: 2: Success after binutils/gcc: 42 commits discards b34e0ba8c64 127: onsuccess: #544: 2: Success after binutils/gcc: 29 commits discards d9ccb0f542b 126: onsuccess: #543: 2: Success after binutils/gcc: 10 commits discards 06ac03eeefc 125: onsuccess: #542: 2: Success after binutils/gcc: 14 commits discards 7e2c6b8c120 124: onsuccess: #541: 2: Success after binutils/gcc: 36 commits discards b0e2598dd6a 123: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards f369cccf79a 122: onsuccess: #539: 2: Success after binutils/gcc: 37 commits discards 8b256ea1223 121: onsuccess: #538: 2: Success after binutils/gcc: 55 commits discards b4173024f35 120: onsuccess: #537: 2: Success after binutils/gcc: 79 commits discards 0d241be855e 119: onsuccess: #536: 2: Success after binutils/gcc: 4 commits discards f0d2d183fc2 118: onsuccess: #535: 2: Success after gcc: 3 commits discards 6094fe42b78 117: onsuccess: #534: 2: Success after binutils: 5 commits discards 64b78464628 116: onsuccess: #532: 2: Success after binutils/gcc: 21 commits discards 1e78b088276 115: onsuccess: #531: 2: Success after binutils/gcc: 50 commits discards 3101298d3f5 114: onsuccess: #530: 2: Success after binutils/gcc: 48 commits discards 679c4aedb34 113: onsuccess: #529: 2: Success after binutils/gcc: 44 commits discards 5f509d43368 112: onsuccess: #528: 2: Success after binutils/gcc: 35 commits discards c22f028c5f2 111: onsuccess: #527: 2: Success after binutils/gcc: 8 commits discards 1eb42626417 110: onsuccess: #526: 2: Success after binutils/gcc: 38 commits discards 58a73ef71e9 109: onsuccess: #525: 2: Success after binutils/gcc: 33 commits discards d0abe3159aa 108: onsuccess: #524: 2: Success after binutils/gcc: 43 commits discards 78d6048c2f5 107: onsuccess: #523: 2: Success after binutils/gcc: 227 commits discards ac0252ba398 106: onsuccess: #522: 1: Success after gcc: 11 commits discards 66d49d54b9d 105: force: #521: 1: Failure after basepoints/gcc-13-3918-g [...] discards 52ea38f9b30 104: force: #520: 2: Success after gcc: 10 commits discards 5a03e5c8699 103: onsuccess: #517: 2: Success after binutils: 5 commits discards 4b30fb0efd1 102: onsuccess: #515: 2: Success after binutils/gcc: 71 commits discards eea1b7bb3e9 101: onsuccess: #514: 2: Success after binutils/gcc: 43 commits discards c40dc07eaa3 100: onsuccess: #513: 2: Success after binutils/gcc: 60 commits discards 0f02a43fdb8 99: onsuccess: #512: 2: Success after binutils/gcc: 71 commits discards ae32e37a7f9 98: onsuccess: #511: 2: Success after binutils/gcc: 57 commits discards a65c7676928 97: onsuccess: #510: 2: Success after binutils/gcc: 12 commits discards e826dcafefe 96: onsuccess: #509: 2: Success after binutils/gcc: 28 commits discards 9489678c37a 95: onsuccess: #508: 2: Success after binutils/gcc: 85 commits discards b82b57d68b0 94: onsuccess: #507: 2: Success after binutils/gcc: 32 commits discards e82854cc7b1 93: onsuccess: #506: 2: Success after binutils/gcc: 26 commits discards 743cf32e3f3 92: onsuccess: #505: 2: Success after binutils/gcc: 34 commits discards 5607a336479 91: onsuccess: #504: 2: Success after binutils/gcc: 26 commits discards 840e95eb768 90: onsuccess: #503: 2: Success after binutils/gcc: 3 commits discards e218e0cda3b 89: onsuccess: #502: 2: Success after binutils/gcc: 31 commits discards 58077661534 88: onsuccess: #501: 2: Success after binutils/gcc: 36 commits discards 6242f25742f 87: onsuccess: #500: 2: Success after binutils/gcc: 28 commits discards 3eb658c6e36 86: onsuccess: #499: 2: Success after binutils/gcc: 36 commits discards 6753bf664ae 85: onsuccess: #498: 2: Success after binutils/gcc: 44 commits discards 75fa2785538 84: onsuccess: #497: 2: Success after binutils/gcc: 26 commits discards d5d80a7be60 83: onsuccess: #496: 2: Success after binutils/gcc: 4 commits discards fe2d855defc 82: onsuccess: #495: 2: Success after binutils/gcc: 15 commits discards 14a17c1c3b7 81: onsuccess: #494: 2: Success after binutils/gcc: 39 commits discards c9bc9af098e 80: onsuccess: #493: 2: Success after binutils/gcc: 48 commits discards 4d1bee6ae7b 79: onsuccess: #492: 2: Success after binutils/gcc: 40 commits discards 16ab72e01b1 78: onsuccess: #491: 2: Success after binutils/gcc: 58 commits discards 6c68e5f0ae5 77: onsuccess: #490: 2: Success after binutils/gcc: 30 commits discards 92ef2e07d93 76: onsuccess: #489: 2: Success after binutils/gcc: 9 commits discards b023689bdf3 75: onsuccess: #488: 2: Success after binutils/gcc: 15 commits discards 0e6c6ed9ec2 74: onsuccess: #487: 2: Success after binutils/gcc: 48 commits discards dc0466e0a79 73: onsuccess: #486: 2: Success after binutils/gcc: 31 commits discards b5786dd286e 72: onsuccess: #485: 2: Success after binutils/gcc: 39 commits discards 861542782cc 71: onsuccess: #484: 2: Success after binutils/gcc: 109 commits discards 6f0c824da73 70: onsuccess: #483: 1: Success after gcc: 3 commits discards 3e35faa6cfd 69: force: #482: 1: Failure after basepoints/gcc-13-3172-gf [...] discards cf09d89da0f 68: force: #481: 2: Success after gcc: 6 commits discards f50edef8c12 67: onsuccess: #478: 2: Success after binutils: 5 commits discards d48f7170dfc 66: onsuccess: #476: 2: Success after binutils/gcc: 37 commits discards 269de56b791 65: onsuccess: #475: 2: Success after binutils/gcc: 56 commits discards 950216dbf1c 64: onsuccess: #474: 2: Success after binutils/gcc: 37 commits discards f48a5b5c31a 63: onsuccess: #473: 2: Success after binutils/gcc: 37 commits discards 8061adf3c15 62: onsuccess: #472: 2: Success after binutils/gcc: 48 commits discards 31d10ea6f7e 61: onsuccess: #471: 2: Success after binutils/gcc: 16 commits discards 11d2735e31d 60: onsuccess: #470: 2: Success after binutils/gcc: 25 commits discards 7875c22837c 59: onsuccess: #469: 2: Success after binutils/gcc: 53 commits discards 5e51083385e 58: onsuccess: #468: 2: Success after binutils/gcc: 51 commits discards 5c45689c278 57: onsuccess: #467: 1: Success after binutils/gcc: 25 commits discards 2d4e32ba295 56: onsuccess: #466: 1: Success after binutils/gcc: 32 commits discards cbc48a2e040 55: onsuccess: #465: 1: Success after gcc: 6 commits discards 2ce612f3e5d 54: force: #464: 1: Failure after basepoints/gcc-13-2871-g1 [...] discards 3d15295903d 53: force: #463: 2: Success after gcc: 29 commits discards 95b67f1f0e8 52: onsuccess: #461: 2: Success after binutils: 8 commits discards 054ba4ecded 51: onsuccess: #459: 2: Success after binutils/gcc: 12 commits discards 7d4727fc7a7 50: onsuccess: #458: 2: Success after binutils/gcc: 19 commits discards 9b3d798c40b 49: onsuccess: #457: 2: Success after binutils/gcc: 55 commits discards 162ea14682b 48: onsuccess: #456: 2: Success after binutils/gcc: 39 commits discards cb6de4915bb 47: onsuccess: #455: 2: Success after binutils/gcc: 47 commits discards b8ca970913e 46: onsuccess: #454: 2: Success after binutils/gcc: 27 commits discards 34da46a33b2 45: onsuccess: #453: 2: Success after binutils/gcc: 8 commits discards 34d9f5c386c 44: onsuccess: #452: 2: Success after binutils/gcc: 6 commits discards 13a568ba93f 43: onsuccess: #451: 2: Success after binutils/gcc: 14 commits discards 3f425046694 42: onsuccess: #450: 2: Success after binutils/gcc: 25 commits discards 348919dafd3 41: onsuccess: #449: 2: Success after binutils/gcc: 16 commits discards 4ea92ab3af3 40: onsuccess: #448: 2: Success after binutils/gcc: 31 commits discards be2cace67a3 39: onsuccess: #447: 2: Success after binutils/gcc: 37 commits discards b772930b3e4 38: onsuccess: #446: 2: Success after binutils/gcc: 59 commits discards 7d164445d7d 37: onsuccess: #445: 2: Success after binutils/gcc: 4 commits discards 482cf0f126c 36: onsuccess: #444: 2: Success after binutils/gcc: 16 commits discards e49098b24d1 35: onsuccess: #443: 2: Success after binutils/gcc: 24 commits discards 4f520e5a960 34: onsuccess: #442: 2: Success after binutils/gcc: 26 commits new 249d1c895c3 34: onsuccess: #442: 2: Success after binutils/gcc: 26 commits new 1cdfff4e5b2 35: onsuccess: #443: 2: Success after binutils/gcc: 24 commits new a7f89e3d3e9 36: onsuccess: #444: 2: Success after binutils/gcc: 16 commits new 4a0248c3e75 37: onsuccess: #445: 2: Success after binutils/gcc: 4 commits new e9b1a419c01 38: onsuccess: #446: 2: Success after binutils/gcc: 59 commits new 66f58ed03b9 39: onsuccess: #447: 2: Success after binutils/gcc: 37 commits new e1b7136fb96 40: onsuccess: #448: 2: Success after binutils/gcc: 31 commits new 702c928554f 41: onsuccess: #449: 2: Success after binutils/gcc: 16 commits new 065c3caa4fd 42: onsuccess: #450: 2: Success after binutils/gcc: 25 commits new aa842cab394 43: onsuccess: #451: 2: Success after binutils/gcc: 14 commits new a03a9c7b27d 44: onsuccess: #452: 2: Success after binutils/gcc: 6 commits new 46eb8112c65 45: onsuccess: #453: 2: Success after binutils/gcc: 8 commits new b1a14fd0fb7 46: onsuccess: #454: 2: Success after binutils/gcc: 27 commits new 7d74b1d2976 47: onsuccess: #455: 2: Success after binutils/gcc: 47 commits new 86899d492bf 48: onsuccess: #456: 2: Success after binutils/gcc: 39 commits new 8b2e9576ff3 49: onsuccess: #457: 2: Success after binutils/gcc: 55 commits new ebe316a0c6c 50: onsuccess: #458: 2: Success after binutils/gcc: 19 commits new 8d4f0de1ad6 51: onsuccess: #459: 2: Success after binutils/gcc: 12 commits new 47852ba4d4c 52: onsuccess: #461: 2: Success after binutils: 8 commits new 513dc6ccf6c 53: force: #463: 2: Success after gcc: 29 commits new a8e2bc1a34c 54: force: #464: 1: Failure after basepoints/gcc-13-2871-g1 [...] new 25d813889dc 55: onsuccess: #465: 1: Success after gcc: 6 commits new e1747abce93 56: onsuccess: #466: 1: Success after binutils/gcc: 32 commits new df39fe40739 57: onsuccess: #467: 1: Success after binutils/gcc: 25 commits new c3e4ad45258 58: onsuccess: #468: 2: Success after binutils/gcc: 51 commits new 704975c4765 59: onsuccess: #469: 2: Success after binutils/gcc: 53 commits new 37a8beba859 60: onsuccess: #470: 2: Success after binutils/gcc: 25 commits new 29cf301fa9f 61: onsuccess: #471: 2: Success after binutils/gcc: 16 commits new 04be02a93a9 62: onsuccess: #472: 2: Success after binutils/gcc: 48 commits new 8a803907e9b 63: onsuccess: #473: 2: Success after binutils/gcc: 37 commits new 54271c876b1 64: onsuccess: #474: 2: Success after binutils/gcc: 37 commits new 341e6be820f 65: onsuccess: #475: 2: Success after binutils/gcc: 56 commits new 75113fc01b5 66: onsuccess: #476: 2: Success after binutils/gcc: 37 commits new a623964bdd3 67: onsuccess: #478: 2: Success after binutils: 5 commits new 768b3b83539 68: force: #481: 2: Success after gcc: 6 commits new 1ec9cc1ddf9 69: force: #482: 1: Failure after basepoints/gcc-13-3172-gf [...] new a7337a4acba 70: onsuccess: #483: 1: Success after gcc: 3 commits new b98d3ad10fe 71: onsuccess: #484: 2: Success after binutils/gcc: 109 commits new 366f3be3541 72: onsuccess: #485: 2: Success after binutils/gcc: 39 commits new aff59fcca0c 73: onsuccess: #486: 2: Success after binutils/gcc: 31 commits new 41d807d9af7 74: onsuccess: #487: 2: Success after binutils/gcc: 48 commits new ba73e170c86 75: onsuccess: #488: 2: Success after binutils/gcc: 15 commits new 2cd4297f26f 76: onsuccess: #489: 2: Success after binutils/gcc: 9 commits new 39198cd0740 77: onsuccess: #490: 2: Success after binutils/gcc: 30 commits new 93a8d7f0e1c 78: onsuccess: #491: 2: Success after binutils/gcc: 58 commits new d760d17b67d 79: onsuccess: #492: 2: Success after binutils/gcc: 40 commits new 10bb297f263 80: onsuccess: #493: 2: Success after binutils/gcc: 48 commits new a754f734d2e 81: onsuccess: #494: 2: Success after binutils/gcc: 39 commits new a5b3cf8f91c 82: onsuccess: #495: 2: Success after binutils/gcc: 15 commits new 9601cf0faa2 83: onsuccess: #496: 2: Success after binutils/gcc: 4 commits new 35476d918bc 84: onsuccess: #497: 2: Success after binutils/gcc: 26 commits new e7cee90eca0 85: onsuccess: #498: 2: Success after binutils/gcc: 44 commits new 42e3ce5355b 86: onsuccess: #499: 2: Success after binutils/gcc: 36 commits new 2874b447ef0 87: onsuccess: #500: 2: Success after binutils/gcc: 28 commits new f948737d2b8 88: onsuccess: #501: 2: Success after binutils/gcc: 36 commits new dd19ff219f4 89: onsuccess: #502: 2: Success after binutils/gcc: 31 commits new 33d5cefa056 90: onsuccess: #503: 2: Success after binutils/gcc: 3 commits new 60f55c65d22 91: onsuccess: #504: 2: Success after binutils/gcc: 26 commits new bc0ba1a6800 92: onsuccess: #505: 2: Success after binutils/gcc: 34 commits new f1b8b46550c 93: onsuccess: #506: 2: Success after binutils/gcc: 26 commits new c66dd7e298c 94: onsuccess: #507: 2: Success after binutils/gcc: 32 commits new 16e559fad02 95: onsuccess: #508: 2: Success after binutils/gcc: 85 commits new 29823b57ad7 96: onsuccess: #509: 2: Success after binutils/gcc: 28 commits new c3df436e605 97: onsuccess: #510: 2: Success after binutils/gcc: 12 commits new 8ac2a19e16c 98: onsuccess: #511: 2: Success after binutils/gcc: 57 commits new 7f413957e28 99: onsuccess: #512: 2: Success after binutils/gcc: 71 commits new c44e111020f 100: onsuccess: #513: 2: Success after binutils/gcc: 60 commits new 49ca11024b9 101: onsuccess: #514: 2: Success after binutils/gcc: 43 commits new f613f237aa9 102: onsuccess: #515: 2: Success after binutils/gcc: 71 commits new 8ee0f53fd79 103: onsuccess: #517: 2: Success after binutils: 5 commits new 64ff22b9f90 104: force: #520: 2: Success after gcc: 10 commits new b1efc012115 105: force: #521: 1: Failure after basepoints/gcc-13-3918-g [...] new 2e69a0d8b52 106: onsuccess: #522: 1: Success after gcc: 11 commits new 7cba3264074 107: onsuccess: #523: 2: Success after binutils/gcc: 227 commits new 51e585407db 108: onsuccess: #524: 2: Success after binutils/gcc: 43 commits new 83914887ec5 109: onsuccess: #525: 2: Success after binutils/gcc: 33 commits new 0c787ad88c8 110: onsuccess: #526: 2: Success after binutils/gcc: 38 commits new 7179c33c01f 111: onsuccess: #527: 2: Success after binutils/gcc: 8 commits new 432310efc24 112: onsuccess: #528: 2: Success after binutils/gcc: 35 commits new 8ff091e358a 113: onsuccess: #529: 2: Success after binutils/gcc: 44 commits new 0bc8676cdfa 114: onsuccess: #530: 2: Success after binutils/gcc: 48 commits new 72fc056273e 115: onsuccess: #531: 2: Success after binutils/gcc: 50 commits new 89a23e8db65 116: onsuccess: #532: 2: Success after binutils/gcc: 21 commits new 2e467064076 117: onsuccess: #534: 2: Success after binutils: 5 commits new aa379a63895 118: onsuccess: #535: 2: Success after gcc: 3 commits new 60e9700234e 119: onsuccess: #536: 2: Success after binutils/gcc: 4 commits new 87cb105983d 120: onsuccess: #537: 2: Success after binutils/gcc: 79 commits new e477ee5b0d3 121: onsuccess: #538: 2: Success after binutils/gcc: 55 commits new 1fc09c172b9 122: onsuccess: #539: 2: Success after binutils/gcc: 37 commits new a7c4ef4e598 123: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new f018e98912b 124: onsuccess: #541: 2: Success after binutils/gcc: 36 commits new 39a1ff07fa1 125: onsuccess: #542: 2: Success after binutils/gcc: 14 commits new 5157ed4b1da 126: onsuccess: #543: 2: Success after binutils/gcc: 10 commits new 585403928c5 127: onsuccess: #544: 2: Success after binutils/gcc: 29 commits new 68e48229f09 128: onsuccess: #545: 2: Success after binutils/gcc: 42 commits new 8f28995559b 129: onsuccess: #546: 2: Success after binutils/gcc: 31 commits new c3c0a5d4d94 130: onsuccess: #549: 2: Success after binutils: 14 commits new c3e40f3d6b8 131: force: #553: 1: Failure after gcc: 10 commits new 5e315ffc4df 132: onsuccess: #554: 1: Success after gcc: 36 commits new 0d98eaf3348 133: onsuccess: #555: 1: Success after binutils/gcc: 27 commits new 670127f0347 134: onsuccess: #556: 1: Success after binutils/gcc: 44 commits new 9157a1df181 135: onsuccess: #557: 1: Success after binutils/gcc: 69 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 (755d388204b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1724 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 52852 -> 53340 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 202404 -> 446620 bytes 06-check_regression/console.log.xz | Bin 3080 -> 3116 bytes 07-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++---- 13 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allmodconfig updated (dfefb3e0065 -> d32ecc848dc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from dfefb3e0065 38: onsuccess: #529: boot: Success after binutils/llvm/linu [...] new d32ecc848dc 39: onsuccess: #530: boot: Success after binutils/llvm: 523 [...] The 1 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 1968 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32400 -> 32048 bytes 04-build_kernel_llvm/console.log.xz | Bin 66888 -> 66884 bytes 05-build_abe-qemu/console.log.xz | Bin 30808 -> 31076 bytes 06-build_linux/console.log.xz | Bin 4180 -> 3376 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 4544 -> 3608 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++++++----------- 15 files changed, 17 insertions(+), 17 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (c1160b3ff9e -> b21e5c2525c)

by git＠git.linaro.org

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-aarch64 in repository toolchain/ci/base-artifacts. discards c1160b3ff9e 141: onsuccess: #564: 6: Success after linux: 3224 commits discards 61403dde637 140: onsuccess: #563: 6: Success after glibc: 2 commits discards 39e2c3cb39d 139: onsuccess: #561: 6: Success after binutils: 23 commits discards 751a5b2457c 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards 20da0838a73 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards e78bb34f601 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards 341161c6137 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 66fa2cbfb3d 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards df972620ebb 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards bb6d9dd5c04 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] discards 212501ad401 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] discards e0b58396b49 130: force: #551: 6: Success after gcc: 10 commits discards 52b9b8e3ff2 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 67cd81a636d 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards 4f96831fac8 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards d59582371a8 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards 60198d79e12 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 5d72d4c70cc 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards b858296015c 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 77e075cd23b 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 2526e0c8ff5 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards db30b1655bd 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 850ef1b577b 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 951c0992839 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards efcbca566cd 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards 6c0f0562660 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards fa1f95fabc0 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards ac2b697e138 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards b4cfc1e9175 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards 749437d1ba8 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards f7e6a71afff 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards c172ed61afa 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 08ee3ba0045 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 25d1af0d872 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards 130cb8cf76c 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 88d85244b28 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 21b90bcc23d 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 3afa5c259bb 104: force: #522: 6: Success after gcc: 24 commits discards f94809b33b6 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 85dc76bd1a9 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards 5432a7aad56 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards 255492fd04d 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards 67ac2e66e08 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards b9f2dd3a102 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards c01b8203457 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 3bae0399c56 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards a1a657e6f17 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards e8798d8077c 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 994f6640c54 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards e24e269f23c 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 68a2d600baa 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards 9ddf07fcfa2 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards b42729e8823 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards 930f67b07df 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards 2a755beb6c7 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards 699526adb8b 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards f3500129962 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 813b7373b8d 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 098507bcc7c 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards 85c2b70061b 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards f073ea2435c 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards 43e0596f431 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards 40c0536c455 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 44a9028ba1f 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards a184928f7c2 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards ad241512c95 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards e504a33095a 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards dc7ab5fa20d 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards 6142781b149 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 9151f4539f1 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 889c1bd625a 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards 02ec3428927 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 3e2da5a862a 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards f272efe7933 68: force: #484: 6: Success after gdb: 6 commits discards 2795bbefb95 67: onsuccess: #483: 6: Success after linux: 384 commits discards f891ba5a483 66: onsuccess: #482: 6: Success after glibc: 2 commits discards de7ecf0001b 65: onsuccess: #480: 6: Success after gcc: 12 commits discards f3082802a83 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 7925939abb3 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 7df9acf4f5e 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 7139be85111 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 6c3c79e38bd 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards 94e02e42ce1 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards ffc30d818f2 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards 23adab2c62d 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 95f0cc174b4 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards a63fdb231d2 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 98731d492a3 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards a27cbeb9b67 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards a549e909002 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 548df63d437 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 8c20fcbe3eb 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 7e777063ad9 49: force: #463: 6: Success after gcc: 18 commits discards d7b922b9fe4 48: onsuccess: #461: 6: Success after binutils: 10 commits discards 42c410ff240 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards 3329ff8fb95 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards d41f2fd4da5 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards e15bd8c326f 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards ae21cafad08 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 6fb808d7c73 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards a0dbae181ad 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new 380addb0294 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new 02ed27ac3d4 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new 1d34dd1d7fa 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new a61749c0a49 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new 48fdf74759d 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 0abc918ca9a 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new b1ce8c16e1d 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 73a4535ff8e 48: onsuccess: #461: 6: Success after binutils: 10 commits new 63ce37552e3 49: force: #463: 6: Success after gcc: 18 commits new 84d4b61505f 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new 847ff5f97fd 51: onsuccess: #465: 1: Success after gcc: 10 commits new 208e9e3879f 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 24f21ee7a1e 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new bb044a7329b 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 59993ca7207 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 410ea382a03 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new a5d9f327f8b 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new 57c48000856 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new 095b51f97aa 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 58257ee7d24 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new 567023db127 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new 9c1eecfe0b4 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 753fce6dd71 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new 84c783cac6d 64: onsuccess: #479: 6: Success after binutils: 14 commits new 5b7e8da4617 65: onsuccess: #480: 6: Success after gcc: 12 commits new bed7e167c95 66: onsuccess: #482: 6: Success after glibc: 2 commits new 57713bc9a5d 67: onsuccess: #483: 6: Success after linux: 384 commits new f871f7ad6d6 68: force: #484: 6: Success after gdb: 6 commits new 0c03cb85867 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new 4ebf399dede 70: onsuccess: #486: 5: Success after gdb: 7 commits new 759c8756b16 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new d9d236dda58 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new c761d7b57b1 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new 615f22f6560 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new adb9c784eba 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new 0f1ea8a53ea 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new f5dacb34c36 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new ffa88f392ef 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new cc806817ea6 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new 76031d3a5f3 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new 844e3b6abe7 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new 2cdb96a1ad8 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 47a46852ddb 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 2b75fc8fd3c 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new 2076fcc4986 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new 0fc43657589 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 8098a6fabf2 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new 6955328ad0e 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new 3d11e2e0fad 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 9e430204aee 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new d1cb0466040 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new f5ba8b8e273 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 4d33bc81996 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 1bc59a8ab02 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 8bbdd313b34 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 96d6e514c2b 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new ecbd45461f4 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new 8de5fdcf140 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 4aba94fd3bf 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new fcac0a0c367 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new a9cb57c03f5 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 1e0d0bf691a 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new 4451bf01d66 103: onsuccess: #520: 6: Success after binutils: 10 commits new 7678ea60f26 104: force: #522: 6: Success after gcc: 24 commits new 884133d06a0 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new 148a6ce8426 106: onsuccess: #524: 1: Success after gcc: 11 commits new c9a66d5f981 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 4d4f949e032 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 91ce102d741 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new bbee52610db 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new d98660f4075 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 727ca784d4d 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 6f7ea1be6eb 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new ec1e9cfa15c 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new 89dd0f406d6 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 2ec27f987a2 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new 6292b524c7a 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new fa48f0b0008 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 631a36f2710 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 3f4243a5bb5 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new b33f1ed7a5d 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new df2b9542986 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 5286a159cb4 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 59b80a689f0 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 61ce8b267ee 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new 3caa0344cf1 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new a9c0b2dba8e 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new 00f144f9b2f 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new e6fe894cade 129: onsuccess: #548: 6: Success after binutils: 8 commits new 90a2bd5918c 130: force: #551: 6: Success after gcc: 10 commits new 2cd1e6c10ec 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] new 3ee94fd89bd 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] new 3490045bc00 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new d46858222df 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 2cb24f3eca8 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new b7eb5c761ef 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 9c236977fd8 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 9b43b19310b 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 12d220b6d1b 139: onsuccess: #561: 6: Success after binutils: 23 commits new b9afec2a7f1 140: onsuccess: #563: 6: Success after glibc: 2 commits new 18a600b52ce 141: onsuccess: #564: 6: Success after linux: 3224 commits new b21e5c2525c 142: force: #565: 6: Success after gcc: 8 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 (c1160b3ff9e) \ 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 1724 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 39772 -> 39620 bytes 05-build_abe-gcc/console.log.xz | Bin 214428 -> 215000 bytes 07-build_abe-linux/console.log.xz | Bin 9416 -> 9532 bytes 08-build_abe-glibc/console.log.xz | Bin 243148 -> 245712 bytes 09-build_abe-gdb/console.log.xz | Bin 39616 -> 39872 bytes 10-check_regression/console.log.xz | Bin 2988 -> 2988 bytes 11-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 15 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (41daaea2cca -> 1bf337caba9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 41daaea2cca Remove two unnecessary casts new 1bf337caba9 gold: Remove BND from 64-bit x86-64 IBT PLT The 1 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: gold/x86_64.cc | 57 +++++++++------------------------------------------------ 1 file changed, 9 insertions(+), 48 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os_LTO updated (3870d69d819 -> f07abe1e8ea)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os_LTO in repository toolchain/ci/base-artifacts. from 3870d69d819 36: onsuccess: #350: 1: [TCWG CI] No change after binutils/ [...] new f07abe1e8ea 37: onsuccess: #351: 1: [TCWG CI] No change after binutils/ [...] The 1 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 1824 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32716 -> 31676 bytes 04-build_abe-stage1/console.log.xz | Bin 90896 -> 90100 bytes 06-build_abe-newlib/console.log.xz | Bin 16828 -> 16840 bytes 07-build_abe-stage2/console.log.xz | Bin 162388 -> 161424 bytes 08-benchmark/benchmark-build.log | 88 ++++++++++----------- 08-benchmark/benchmark.log | 86 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3824 -> 3816 bytes 09-check_regression/console.log.xz | Bin 5132 -> 5052 bytes 09-check_regression/results-vs-first.log | 8 +- 09-check_regression/results-vs-prev.log | 6 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 36 ++++----- mail/mail-body.txt | 36 ++++----- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++---- results_id | 2 +- 24 files changed, 167 insertions(+), 167 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allmodconfig updated (38a2ab9e998 -> 9c7a2243e9c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from 38a2ab9e998 44: onsuccess: #494: 23734: Success after binutils/linux/qe [...] new 9c7a2243e9c 45: onsuccess: #495: 23763: Success after binutils/linux: 1 [...] The 1 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 1756 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30324 -> 30360 bytes 04-build_kernel_llvm/console.log.xz | Bin 66256 -> 65876 bytes 05-build_abe-qemu/console.log.xz | Bin 31348 -> 30580 bytes 06-build_linux/console.log.xz | Bin 4436 -> 3868 bytes 08-check_regression/console.log.xz | Bin 3604 -> 3300 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++++++----------- results | 2 +- 17 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (23bcde3b2b0 -> c1160b3ff9e)

by git＠git.linaro.org

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-aarch64 in repository toolchain/ci/base-artifacts. discards 23bcde3b2b0 140: onsuccess: #563: 6: Success after glibc: 2 commits discards a93389e0c50 139: onsuccess: #561: 6: Success after binutils: 23 commits discards 7da96215f6d 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards ea348f47636 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 5243deb3377 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards 471312e6388 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 74db9711cad 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards 3929d806f1e 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards a1e98b289dc 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] discards 73b3a207143 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] discards 7de47ee29d2 130: force: #551: 6: Success after gcc: 10 commits discards 85efb967448 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 04d4857b59d 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards db12e09ab9c 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards 38f024c7191 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards 5beb65f5f4f 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards b876de6660a 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 58e1377d446 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 4d8397d01e2 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards ff940d75426 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 73fc8fdff30 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 871eaa5857f 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 9d6cac724c8 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards fef62511937 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards 96342f2f259 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards 05caa5d8722 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 63150b335ba 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards 48e142a3307 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards 67d9783eb93 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 5f078611380 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards 9f6b1c7cded 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 5da68610442 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards ef6628eb77a 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards 2ea7c0091ac 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 5e3c2ddc878 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 27d0a7462f0 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 9638fad3fda 104: force: #522: 6: Success after gcc: 24 commits discards be5cf56d9db 103: onsuccess: #520: 6: Success after binutils: 10 commits discards da20a9c0745 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards f1cd5dadaa4 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards e08c2b66eb9 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards 3aa9aaf96c1 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 4fc463aac02 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards f713e5169a3 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards f413dc38862 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 128ac57419e 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards 05972489230 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 97008b81422 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards b1b048ba7ea 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards acfce00269f 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards f41d75e9dfa 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards d0813ea3ff9 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards b8aee5f099f 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards 2b12f722f7e 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards 862ad3c9166 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 062023107ca 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 969d664f6b5 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 3ae742d9ec8 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards 1546b9c2730 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards 76c726f9955 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards cf0a3593467 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards f555e84a325 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards e346caefd75 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards 7d0485d9473 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards 214f05726ef 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 0e4567c2b8d 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards cd9ef2b40c7 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards fa75821677d 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards bf0ca3a2f81 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 75f8c4a3592 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards a183d09f4c2 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 7798cb63856 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards 04529bf2df9 68: force: #484: 6: Success after gdb: 6 commits discards f7cb22e9ba0 67: onsuccess: #483: 6: Success after linux: 384 commits discards ef44d22d8b5 66: onsuccess: #482: 6: Success after glibc: 2 commits discards c7011e8c8ad 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 89275188cb7 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 211df992a7f 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 385aee5a5dd 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 2766d6446ae 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 73108c58e87 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards 9544220ddd1 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 66af47b8f62 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards 6a28fc27482 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 2026b43e29d 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards 3ae0b61ad67 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 676e2c28ce9 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards 3523a592898 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards ed9cda4cd1e 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 2d614b3383e 51: onsuccess: #465: 1: Success after gcc: 10 commits discards f9f01b4d6ad 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 832398f7e8f 49: force: #463: 6: Success after gcc: 18 commits discards 69bfe95db85 48: onsuccess: #461: 6: Success after binutils: 10 commits discards b8069727b25 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards a5380d327c6 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards 3c0bfeab796 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards d08b47ce9b2 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards b2505f05b21 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards def64acadde 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards f930bbad2b4 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] discards c83b5493406 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new 964643ce079 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new a0dbae181ad 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new 6fb808d7c73 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new ae21cafad08 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new e15bd8c326f 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new d41f2fd4da5 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 3329ff8fb95 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 42c410ff240 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new d7b922b9fe4 48: onsuccess: #461: 6: Success after binutils: 10 commits new 7e777063ad9 49: force: #463: 6: Success after gcc: 18 commits new 8c20fcbe3eb 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new 548df63d437 51: onsuccess: #465: 1: Success after gcc: 10 commits new a549e909002 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new a27cbeb9b67 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 98731d492a3 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new a63fdb231d2 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 95f0cc174b4 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new 23adab2c62d 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new ffc30d818f2 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new 94e02e42ce1 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 6c3c79e38bd 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new 7139be85111 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new 7df9acf4f5e 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 7925939abb3 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new f3082802a83 64: onsuccess: #479: 6: Success after binutils: 14 commits new de7ecf0001b 65: onsuccess: #480: 6: Success after gcc: 12 commits new f891ba5a483 66: onsuccess: #482: 6: Success after glibc: 2 commits new 2795bbefb95 67: onsuccess: #483: 6: Success after linux: 384 commits new f272efe7933 68: force: #484: 6: Success after gdb: 6 commits new 3e2da5a862a 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new 02ec3428927 70: onsuccess: #486: 5: Success after gdb: 7 commits new 889c1bd625a 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 9151f4539f1 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new 6142781b149 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new dc7ab5fa20d 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new e504a33095a 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new ad241512c95 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new a184928f7c2 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 44a9028ba1f 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new 40c0536c455 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new 43e0596f431 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new f073ea2435c 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new 85c2b70061b 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 098507bcc7c 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 813b7373b8d 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new f3500129962 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new 699526adb8b 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 2a755beb6c7 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new 930f67b07df 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new b42729e8823 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 9ddf07fcfa2 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new 68a2d600baa 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new e24e269f23c 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 994f6640c54 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new e8798d8077c 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new a1a657e6f17 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 3bae0399c56 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new c01b8203457 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new b9f2dd3a102 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 67ac2e66e08 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 255492fd04d 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new 5432a7aad56 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 85dc76bd1a9 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new f94809b33b6 103: onsuccess: #520: 6: Success after binutils: 10 commits new 3afa5c259bb 104: force: #522: 6: Success after gcc: 24 commits new 21b90bcc23d 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new 88d85244b28 106: onsuccess: #524: 1: Success after gcc: 11 commits new 130cb8cf76c 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 25d1af0d872 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 08ee3ba0045 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new c172ed61afa 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new f7e6a71afff 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 749437d1ba8 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new b4cfc1e9175 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new ac2b697e138 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new fa1f95fabc0 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 6c0f0562660 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new efcbca566cd 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new 951c0992839 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 850ef1b577b 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new db30b1655bd 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 2526e0c8ff5 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 77e075cd23b 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new b858296015c 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 5d72d4c70cc 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 60198d79e12 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new d59582371a8 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new 4f96831fac8 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new 67cd81a636d 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new 52b9b8e3ff2 129: onsuccess: #548: 6: Success after binutils: 8 commits new e0b58396b49 130: force: #551: 6: Success after gcc: 10 commits new 212501ad401 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] new bb6d9dd5c04 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] new df972620ebb 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 66fa2cbfb3d 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 341161c6137 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new e78bb34f601 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 20da0838a73 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 751a5b2457c 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 39e2c3cb39d 139: onsuccess: #561: 6: Success after binutils: 23 commits new 61403dde637 140: onsuccess: #563: 6: Success after glibc: 2 commits new c1160b3ff9e 141: onsuccess: #564: 6: Success after linux: 3224 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 (23bcde3b2b0) \ 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 1720 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 40072 -> 39772 bytes 05-build_abe-gcc/console.log.xz | Bin 214252 -> 214428 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8472 -> 9416 bytes 08-build_abe-glibc/console.log.xz | Bin 243360 -> 243148 bytes 09-build_abe-gdb/console.log.xz | Bin 39300 -> 39616 bytes 10-check_regression/console.log.xz | Bin 2768 -> 2988 bytes 11-update_baseline/console.log | 42 +++++++++++++++++------------------ 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 | 12 +++++----- 16 files changed, 32 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022