Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (040d8fc685 -> ea10c5a5c5)

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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 040d8fc685 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 562404d4fe 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 83282f95f4 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 594658d2b4 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c9a59758c4 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ffa83a3223 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 11f5dfee76 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards a4457f9314 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 2b9a16c144 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 45725e2824 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards efcc29d1d9 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c0b7eb2d9 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards a809a2582a 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 2832ae64db 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 40a5698b48 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards dccce68b69 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 63026a89c6 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 94e7ad6378 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 7a6f0e457c 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 5eafce3f66 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 25d03b8c57 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 5558e877c5 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards c3afbfb0d3 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 167da83f8c 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 576416386a 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards bdec31e97a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards ad0f3c94ab 127: force: #27: : Failure after baseline build: no new commits discards 7a48c30cd1 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 2103ad9e1c 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards cdd2158ceb 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 3b2c409ba4 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards e0e2c9e08d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards c4c5f1e6a8 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards cc698c4c31 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 18d279a518 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards a68e5271e4 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5dc63755dc 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 84d2a8bded 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 1a65f5693d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 7fb7dd1464 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 8a1de1b86a 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards bad021cc17 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards ade7e83c42 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards c1f2802ae1 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 92472fe532 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards f7b61ecd8a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards bd53ba3cf4 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 094ed2d5c3 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 7bb2427474 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 07c2c40be5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 5ba2b13b2e 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 9ba1ab3c10 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards dbb10cce0e 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 1aff968e62 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 96e204f11c 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards ed86474ea4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 51570983e5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 7ac8eed37c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 7c40b9cfa5 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 5edc1f35ab 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards b9967f7374 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards d8d498f4ed 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 768754ec8d 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards e9a092d06a 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 4f27fa0859 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards d974672a06 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 070d5740af 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 52faa6cc00 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 3516ba6be0 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 1e669aab1e 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 9e71deeb9e 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 61b36f9ad3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards e347295376 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards fefd536f7a 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 456cdcce8c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 97f653e7a9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards c8f8970d03 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards e8ea90c023 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 03f8cb9fb2 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards eee39d301f 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 13deea7817 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 54ba874b97 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 6a371ae553 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 88adf6200e 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 41207c72ef 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards b0a667baa2 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 0bd4f90e94 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards d8561102db 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 267d6827cc 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards e41a0da9e3 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 7750048f2b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards d78f273fec 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 57fbd8dce7 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 603acd8c0c 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 37c73f3cba 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 5bb318f87f 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 93bd356522 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 71bcda1a28 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 46037725c1 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards c519e4a04b 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards c09bdda135 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 40f0bf4434 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 9159522dab 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 2393595b88 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new c9c76dfdea 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new fc30a74c02 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 91acff30ad 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new d3f2d625f8 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 0e8caa4974 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 6286c6e189 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 60cd1ebbe7 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 4b0e4149e4 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 2df2e00018 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new af21a64858 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 611728d06d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 3284cf79e9 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 8c4d674acf 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new e068d014d3 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 5cbbe20f2f 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new f69ef3845b 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 625067a114 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 788083bee4 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 36b9b8c1c9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 6558f3e596 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new fad79bcb92 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new a0c50803eb 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new d9a43afb22 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 6f512bb30c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 83ae4b5d55 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new a109139c60 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new fc24179aef 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 5d60e0f8b2 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 4786223d34 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 832b68b8f3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new c122506a9b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 01b901881e 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new aa6777b342 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 050ee1cfe1 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new a0ad95b6ef 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new c9cb19bac3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 4c3fafbdb3 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new c0abcae656 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new bcb45df58e 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 0fbe107053 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 52f9c98f23 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 3490eabe48 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 4fdbf4fc14 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 18d75290f0 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new d3612cc239 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new e5c0d25cf6 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 3ea0d4d28c 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new bcbad1739f 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 575fec0c37 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new e3a45c9bc9 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new befe3ce298 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new aebfc5b579 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 4836a622c4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new f00bdc406a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 613d1f43e8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new c7f4a4e369 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9ff6c36c29 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 82a12d258b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new bf7f3aef90 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 052774f25e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0823a15e2c 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 067f3bd97d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new dec560f05b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 30b380d3b6 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8ec2d5536f 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e26c32fb1b 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a2361a7948 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 6a9d0d490e 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 017ddf6eb0 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new ef85666416 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 41962840f1 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new eea0feccdc 127: force: #27: : Failure after baseline build: no new commits new 76f7b2ea3d 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 41927e90d9 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 6a581a6b48 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 54f9137a3c 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 43ccd9d35b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 7374dc120a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new c62c9b0a2b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 7f75f79fa8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 462026cf0e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new a29650bad8 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 9d5eca028b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new a38e1ff17d 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 4dff8fd6f6 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new d60076c066 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 736e61364a 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 4517e1e2d3 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 734d7d80e6 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 5be55e8539 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 07f2cc3396 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new bc65cea118 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new edb7bf2bcd 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new a8acfe1582 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 274be53d03 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6fce410605 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 53498c0fc5 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 840605e1a0 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new ea10c5a5c5 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (040d8fc685) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 2228 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 35056 -> 35312 bytes 04-build_abe-gcc/console.log.xz | Bin 203856 -> 203788 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8416 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 240896 -> 241520 bytes 08-build_abe-gdb/console.log.xz | Bin 34556 -> 34828 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1716 -> 1712 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 44 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 30 +++++++++++------------ 19 files changed, 43 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[linux] annotated tag v6.3-rc7 created (now 1c8c28415e87)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to annotated tag v6.3-rc7 in repository linux. at 1c8c28415e87 (tag) tagging 6a8f57ae2eb07ab39a6f0ccad60c760743051026 (commit) replaces v6.3-rc6 tagged by Linus Torvalds on Sun Apr 16 15:23:53 2023 -0700 - Log ----------------------------------------------------------------- Linux 6.3-rc7 -----BEGIN PGP SIGNATURE----- iQFSBAABCAA8FiEEq68RxlopcLEwq+PEeb4+QwBBGIYFAmQ8dXkeHHRvcnZhbGRz QGxpbnV4LWZvdW5kYXRpb24ub3JnAAoJEHm+PkMAQRiG24sH/1ADVMOmTCAsYODk QeFm1PvcpDenmGnGN69r5iJ2AbPAhfo3TOAMnQLSxz7ES4VFs6CeArqMGKYYLa0k 2no/gra2jpVLx/qBMIjxkxUBS4uKNOjm9PR+vaamJ2yZOXTWTJFUThzMjVZI8anm TFewF4Nb/A91+a4unPtYWROSjozr27g0aqUAu80/V73xmxSk74pvDJLLA+NMB7vZ cQWkABqW9wpSPr1vkxVNgf6N5DmSmKZWnePG5GjfN5P+BU+eQLyERrOx8ttOvmAR Z62R7S49Zc5BeR2CuBNxWwDober1UIb2Q0PUbvLo6HbN+LidJh90WtAlRYpref2f NRB49N4= =70dU -----END PGP SIGNATURE----- ----------------------------------------------------------------------- This annotated tag includes the following new commits: new 6a8f57ae2eb0 Linux 6.3-rc7 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[linux] branch master updated (6c538e1adbfc -> 6a8f57ae2eb0)

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 linux. from 6c538e1adbfc Merge tag 'sched_urgent_for_v6.3_rc7' of git://git.kernel. [...] new 6a8f57ae2eb0 Linux 6.3-rc7 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: Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO updated (2a864474a6 -> 000d2ec147)

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-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO in repository toolchain/ci/base-artifacts. from 2a864474a6 76: force: #42: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 000d2ec147 77: force: #44: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] 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 1964 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 26756 -> 27012 bytes 04-build_abe-stage1/console.log.xz | Bin 87056 -> 87712 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 12280 -> 12388 bytes 07-build_abe-stage2/console.log.xz | Bin 162744 -> 162744 bytes 08-benchmark/benchmark-build.log | 82 ++++++++++++++-------------- 08-benchmark/benchmark.log | 80 ++++++++++++++------------- 08-benchmark/console.log.xz | Bin 3976 -> 4072 bytes 09-check_regression/console.log.xz | Bin 2740 -> 2764 bytes 09-check_regression/trigger-bisect | 4 +- 10-update_baseline/console.log | 9 +++ git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 12 ++-- results-vs-first/tcwg-benchmark-results.log | 64 +++++++++++----------- results-vs-prev/tcwg-benchmark-results.log | 68 +++++++++++------------ results_id | 2 +- 19 files changed, 169 insertions(+), 156 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (5bd3d445 -> 38181cf9)

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 5bd3d445 Add entry b8d1a3a8ef9aff015ae963522287f7785bc552ec from https [...] new 38181cf9 Add entry 25264f6b3a75f505c1ca3bc7e48ce173560c1b2c 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-7163-g25264f6b3a7 | 1 + .../gnu_eabi-arm_eabi-master-O3_LTO/build_url | 2 +- .../gnu_eabi-arm_eabi-master-O3_LTO/last_good | 1 + .../gnu_eabi-arm_eabi-master-O3_LTO/summary.txt | 8 ++-- .../tcwg_bmk-code_speed-coremark/status.txt | 49 ++++++++++++++++++++++ 5 files changed, 56 insertions(+), 5 deletions(-) create mode 120000 gcc/basepoints/gcc-13-7163-g25264f6b3a7 copy {binutils/sha1/ca26b8030e8c184bdeca7280e31c10c6e9fc3f78 => gcc/sha1/25264f6b3 [...] create mode 100644 gcc/sha1/25264f6b3a75f505c1ca3bc7e48ce173560c1b2c/tcwg_bmk-code [...] copy {binutils/sha1/fade906daab13c99fc329c1e08447f2aac168b62 => gcc/sha1/25264f6b3 [...] create mode 100644 gcc/sha1/25264f6b3a75f505c1ca3bc7e48ce173560c1b2c/tcwg_bmk-code [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (91d678bbac -> 42c44b3fb1)

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_O3 in repository toolchain/ci/base-artifacts. discards 91d678bbac 242: onsuccess: #55: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3800c02c6d 241: onsuccess: #54: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards b69bf06597 240: onsuccess: #53: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 46c5bebfaf 239: onsuccess: #52: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 63ed584a9e 238: onsuccess: #51: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 85a9df6415 237: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] discards c21a5c7010 236: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] discards f8c00d0ca2 235: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards 1d4ab40abf 234: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards ac8f0a8db1 233: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards 0804a53e7b 232: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 42d762fcd0 231: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards c829a89118 230: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] discards af7920ffa3 229: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] discards 015b01294c 228: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] discards 54df43d159 227: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] discards dcff868e31 226: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] discards 0677fbb8ef 225: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] discards e5317f2cf8 224: onsuccess: #35: 2: Success after binutils/gcc: 7 commits discards ee098b3b1e 223: onsuccess: #34: 2: Success after binutils/gcc: 7 commits discards 003b37518b 222: onsuccess: #33: 2: Success after binutils/gcc: 32 commits discards f6dd24fea2 221: onsuccess: #32: 2: Success after binutils/gcc: 32 commits discards da3a683257 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits discards 5c3b2d77e6 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits discards 135d6d71d0 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits discards 442125503a 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits discards f3f4fb47d2 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits discards 7eeeed2533 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards 6d1d99a633 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits discards ed71b97a93 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits discards 636c791c66 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits discards 1ee2b01742 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits discards bc8964ce9c 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits discards 6475a0cdca 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits discards 870161d13a 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits discards 088ff9021f 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits discards 475d19c62a 206: onsuccess: #16: 0: Success after binutils: 17 commits discards 061be9fdde 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] discards 11d440063b 204: force: #14: 2: Success after binutils: 17 commits discards 2de044634f 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits discards 085b29a040 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 59f32c69a5 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits discards 51dca04f05 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits discards 6e44e747e9 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits discards d51578de35 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits discards e82e405439 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits discards 8d57932a8e 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits discards 53517c9b71 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits discards d43a2c143b 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits discards 7c8f88d8b5 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits discards e19736f10b 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits discards e4b70e7fc1 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits discards 304df2d3d1 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits discards 87e93fb064 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits discards 46d8bee634 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits discards da99873482 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits discards 8ea7b5b091 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits discards 708f1c80e3 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits discards 426fe6248e 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits discards 1f14f2dea2 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits discards 58239a1d0b 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits discards db584d0976 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits discards 54ad54e232 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits discards e6a5a390e3 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits discards c27114092f 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits discards 149ab48018 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits discards 0d7e6c09cb 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits discards d9956255ec 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits discards f928c23943 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits discards f0fc256447 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits discards e93c336376 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits discards 035287d3fe 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits discards 4f81a4ee81 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits discards 3083a41404 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits discards 3629706977 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits discards 98edb05e6e 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits discards 4bf3d12f1f 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits discards 45c9d201b6 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits discards fb30a6c5aa 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits discards b156f95c84 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits discards 1a30533987 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits discards 33e3cb3e3d 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits discards 41efae043e 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits discards 21115ccffd 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits discards 21660fc06c 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits discards 495b42191c 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits discards c95b52f6ca 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits discards 812a010601 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 029ed06e6f 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits discards a061caea5a 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits discards 07f622fa57 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits discards e1c6a1a008 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits discards ab2fac4c5b 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits discards f12c9e65de 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits discards 3638f0ac96 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits discards e79d686d7a 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits discards 2472446c22 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits discards 9144fd6094 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards 20ff0b68e7 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits discards 549e69769c 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits discards 57064b315d 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new 4a6f22889c 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new 2aafdbb157 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits new 5df266bb77 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits new 19efc8491e 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new 50f88c5c44 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits new a1cb0c642e 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits new f4ac2ec8d0 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits new 774045a8dc 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits new f1962417bb 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits new 9e02934dc3 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits new b0ba44a7a9 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits new aaca2fec71 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits new 819a4a23cf 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits new 169500ed71 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 19651487ea 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits new f42dbfcf29 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits new 85a4f97d4a 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits new 0ee3568dd6 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits new eecc386dba 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits new 279fd8bc3b 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits new bc51fdd9e6 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits new 86fd2d6b64 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits new e26abdca33 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits new c2af3406a7 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits new 3a23178d26 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits new 4c3b3c56d2 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits new 0cba8856c8 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits new 97e200c51c 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits new 3227bd4bf5 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits new 3dd185e5e6 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits new 8e99569d24 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits new 1d78867a9a 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits new a722cd912c 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits new 9b936444ee 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits new 671fa920b4 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits new 1246067cf1 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits new 5b35247bcb 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits new 5fbc47e02a 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits new d77fe12a86 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits new 577d07071d 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits new 083ee77abc 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits new ceb829298d 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits new 132bf17ed4 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits new 704210c2f5 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits new 54fc8e235c 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits new f4ab9543c1 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits new 5b6bfa527a 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits new 36d0843bd8 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits new 9994d6324d 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits new 14a6df3af4 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits new d2b55290a1 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits new a4481a25ae 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits new c74ce1c532 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits new 06ab0ff458 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits new b93529cc6b 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits new 4a6ea3be4f 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits new 779a734314 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits new 9e1faac9cd 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits new 1ffa0cd7ab 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits new dffa614640 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits new 6f256aaf28 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new a2d1c2d540 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits new 38d914a083 204: force: #14: 2: Success after binutils: 17 commits new e74e632071 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] new 5e59c9ee2b 206: onsuccess: #16: 0: Success after binutils: 17 commits new 839abe4d0c 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits new 052168f72c 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits new 50625942f0 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits new e796352da5 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits new 711d1fd658 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits new 57a93e0ce8 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits new faf8b4ee7c 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits new 8d1d3a4483 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits new 6144a71268 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new 8ec879c364 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits new 9d7435d7ae 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits new df9c4fa45d 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits new 21d221577c 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits new d945e48756 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits new 585dc38e5c 221: onsuccess: #32: 2: Success after binutils/gcc: 32 commits new b7e77b15ed 222: onsuccess: #33: 2: Success after binutils/gcc: 32 commits new 396cee4ef3 223: onsuccess: #34: 2: Success after binutils/gcc: 7 commits new a136f27d24 224: onsuccess: #35: 2: Success after binutils/gcc: 7 commits new 1a1024b940 225: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] new 73f2d83e8a 226: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] new 064301388b 227: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] new f361aaf248 228: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] new 9ebf6fb4f6 229: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] new 421172c1f8 230: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] new 524abd64cd 231: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new 4696979cea 232: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new 5144aa3bff 233: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new 21d9120e10 234: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new f16a1cd6c3 235: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new 56d1fa4c09 236: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] new 9048a58cc0 237: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] new 24d9a0bac1 238: onsuccess: #51: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new eb3dbebb62 239: onsuccess: #52: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 955d07809f 240: onsuccess: #53: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 53e6516383 241: onsuccess: #54: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 398b8b9978 242: onsuccess: #55: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 42c44b3fb1 243: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (91d678bbac) \ 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 2096 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2500 bytes 04-build_abe-binutils/console.log.xz | Bin 49072 -> 48632 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 470180 -> 469292 bytes 06-check_regression/console.log.xz | Bin 548 -> 548 bytes 07-update_baseline/console.log | 42 +++++++++++++++---------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 16 ++++++------ 10 files changed, 32 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig updated (3c56a72d9e -> 94c6104110)

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/gnu-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from 3c56a72d9e 66: onsuccess: #18: boot: [TCWG CI] https://ci.linaro.org/jo [...] new 94c6104110 67: onsuccess: #19: boot: [TCWG CI] https://ci.linaro.org/jo [...] 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 2008 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2556 bytes 03-build_abe-binutils/console.log.xz | Bin 27068 -> 26956 bytes 04-build_abe-stage1/console.log.xz | Bin 71208 -> 71528 bytes 05-build_abe-qemu/console.log.xz | Bin 30604 -> 31000 bytes 06-build_linux/console.log.xz | Bin 5204 -> 5204 bytes 07-boot_linux/console.log.xz | Bin 6124 -> 6116 bytes 08-check_regression/console.log.xz | Bin 1216 -> 528 bytes dashboard/dashboard-generate.sh | 17 ------------- dashboard/dashboard-push.sh | 7 ------ dashboard/squad-vs-first/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 ------ jenkins/notify.sh | 2 +- manifest.sh | 30 +++++++++++------------ 18 files changed, 19 insertions(+), 53 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/results-functional.json delete mode 100755 jenkins/dashboard-push.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (396b91efd6 -> e8fd2d9254)

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_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 396b91efd6 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 321fefd1c3 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fcec9a47c6 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b5a135d672 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 670e144ef6 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2dbd8256ec 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 0f9bf730d4 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards e1d7c21563 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 73ffcab0eb 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 9f2c5be738 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards c959de0774 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 64a9193b0b 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f92a5fae0 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 501a0358e2 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards e872159918 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d954936d4 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 8ec751e0f6 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards adcefea1bd 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 355d05691e 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 894871b01a 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards f38ef61742 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards a14c721c3d 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards bfd7f04c3f 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards ec53118a4a 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards e6eb83d5a1 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 934e67bc86 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 59719b9986 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 393f9f4b1d 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 62be44510a 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 08cdedff9f 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 3a7b65a308 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards 1e0a416047 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards ff2888e38c 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards 89a8545985 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards a225cb7266 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 287e63a10e 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards ceb968e771 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9953e5daff 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards a1147cda62 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 78d531a3cd 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 1647b07cbc 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards b3e219e795 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 1b622bee9e 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 63b37f0626 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards 181002f9a4 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards d05f46cdf8 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards dca47964eb 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 552acfbc6e 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards e08ea587b4 427: onsuccess: #7: 1: Success after linux: 26 commits discards 9393a05f98 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards d95daf5ffb 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 63dd9b709e 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 33716b105a 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 56a42bcfb1 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 47d9acf57f 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 282eb917a0 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 6a6dd45a47 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 6dd0328672 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 8dccda4840 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards b1b6f03be9 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 6179163ff7 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards a9fd4233e0 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards ecfcc56031 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards dc28de809e 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 4dbc40bdcc 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 5adcc50073 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards fd3e49c9ae 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards f7ed5b7d12 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 9a8a107860 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards c5a8f3f67d 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 655e4f33ae 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 18d1c8bb8f 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards c7ad12003e 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards a87345b42b 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards b2d3012503 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 4e160fb68c 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 80ddcf2e46 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards ce59cad3b9 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards e61669e6ca 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 0584cdc250 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards d72cae919c 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards f5de01307d 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 7deed1da7c 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards b9e419ee70 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 160477e6d7 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 62786fbc3b 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 6f72dcf51e 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 4b23405641 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards a8e87428aa 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 7fd112425a 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 516e3e00a4 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 5eaeb86e81 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 830f6ffa37 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 222d7f0845 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 02ba7864a2 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 07e0e3d057 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards d780f3b82a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 9b9023e4a9 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 2e82995d22 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards d91f00d38d 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 16c3ff2613 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 147fe98175 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 6b33733c74 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 4edf68c178 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 906d4ec7d5 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 2cd1c1343a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new b4293e99ca 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 574f43ba7e 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 80d6ebab23 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 965c41b9b3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new eb7cbb091c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 5778e3cbbe 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 4ece1c0f5b 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 076deed2d9 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new f5dddbdef9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 0667699241 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 2d43e23e93 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new cdff9a6b16 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 27b24da11e 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new e83a52760c 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 2b5504d0c8 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 1a4e7391fc 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new e090657620 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 07f56b0931 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new b3f3ba77ac 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 23601f2595 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new e0bc89c97c 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new e4c2c59aaa 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new edd334169e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 7673216ae9 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new e5bd73f9ca 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 3aa78d7651 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new b96322ac69 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 8a4214df8d 407: onsuccess: #2661: 1: Success after gcc: 7 commits new b1909820b9 408: onsuccess: #2662: 1: Success after linux: 11 commits new c80a8e5284 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 7309e436d9 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 8e052144b6 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 27199f7434 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 37b7269bf6 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 6d39349c16 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new b9465a7c01 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new d134dd5f5d 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 93a6031825 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 5fad129e73 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 2df532a6b9 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 53a07f03f6 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new ee18ed5a99 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new dba4c4dff6 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 5f5e65ad57 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d14b3c558e 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 4986c606b8 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 722ff70bd3 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 7df44c2111 427: onsuccess: #7: 1: Success after linux: 26 commits new ec998edc31 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new c1c8387020 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new d7679e39c0 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new f4191f6eea 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 0b318f345c 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new 2d43ba0a0b 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 98e2d529ed 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 5ecd850ecc 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6759a382aa 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new a78097efb0 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new e238b98420 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 70c90df6ef 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 298a541c0a 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 73358bad0e 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new a4ad9ad06a 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new b68f4cc4cb 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new c04241dd41 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new 4931a48078 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 9bdc893ce0 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 04b76c2469 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 9adcc44fdb 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 8621da0e83 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9707a1a5f5 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new c552719a81 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new cece569b8a 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new f70c4f6a1c 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 35620e63b2 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 739104dbfa 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 69df126044 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 9a1eb76d26 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 6d940ab229 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new db731a4319 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 1a29848669 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4e122c5aca 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 3b5b12eb9d 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 42579064b9 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 27a4fe7e23 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 99ccfb3a83 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 33d384458b 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 7fd671da42 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new ae9352a9d4 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new b6db470f18 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 1fc9d4bdc9 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 9be8098442 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7bec4c2785 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 81c48b911c 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d0f365f249 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bca8b39f75 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e8fd2d9254 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (396b91efd6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 2144 -> 2112 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2544 bytes 03-build_abe-binutils/console.log.xz | Bin 27108 -> 27112 bytes 04-build_abe-stage1/console.log.xz | Bin 71252 -> 71632 bytes 06-build_abe-linux/console.log.xz | Bin 8476 -> 8476 bytes 07-build_abe-glibc/console.log.xz | Bin 240468 -> 240344 bytes 08-build_abe-stage2/console.log.xz | Bin 201720 -> 202048 bytes 09-build_abe-gdb/console.log.xz | Bin 34392 -> 34324 bytes 10-build_abe-qemu/console.log.xz | Bin 31160 -> 31040 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 7536 -> 7820 bytes 13-check_regression/console.log.xz | Bin 1964 -> 1668 bytes 13-check_regression/results.compare2 | 97 +- 14-update_baseline/console.log | 60 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 36 +- sumfiles/g++.log.sep.xz | Bin 102256 -> 107680 bytes sumfiles/g++.log.xz | Bin 3428960 -> 3427924 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 9996 ++++++++++++++++++++++++--------- sumfiles/gcc.log.sep.xz | Bin 145420 -> 144828 bytes sumfiles/gcc.log.xz | Bin 3059516 -> 3052044 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 3511 +++++++----- sumfiles/gfortran.log.sep.xz | Bin 192772 -> 174584 bytes sumfiles/gfortran.log.xz | Bin 1049924 -> 1050612 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 6461 ++++++++++----------- sumfiles/libatomic.log.xz | Bin 2312 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217372 -> 217556 bytes sumfiles/libgomp.sum | 10 +- sumfiles/libitm.log.xz | Bin 2680 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 9656 -> 8908 bytes sumfiles/libstdc++.log.xz | Bin 444940 -> 442516 bytes sumfiles/libstdc++.sum | 6 +- sumfiles/libstdc++.sum.sep | 446 +- 42 files changed, 12409 insertions(+), 8234 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3 updated (e29ac40797 -> b950f2b6e3)

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-code_speed-coremark/gnu_eabi-arm_eabi-master-O3 in repository toolchain/ci/base-artifacts. from e29ac40797 57: onsuccess: #17: 1: [TCWG CI] https://ci.linaro.org/job/t [...] new b950f2b6e3 58: onsuccess: #18: 1: [TCWG CI] https://ci.linaro.org/job/t [...] 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 1984 -> 1976 bytes 02-prepare_abe/console.log.xz | Bin 2580 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 26892 -> 26444 bytes 04-build_abe-stage1/console.log.xz | Bin 87244 -> 87324 bytes 06-build_abe-newlib/console.log.xz | Bin 12184 -> 12412 bytes 07-build_abe-stage2/console.log.xz | Bin 162260 -> 162952 bytes 08-benchmark/benchmark-build.log | 98 ++++++++++----------- 08-benchmark/benchmark.log | 96 ++++++++++---------- 08-benchmark/console.log.xz | Bin 4032 -> 4052 bytes 09-check_regression/console.log.xz | Bin 4460 -> 5232 bytes .../results_id.first | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 26 +++--- results-vs-first/tcwg-benchmark-results.log | 4 +- results-vs-prev/tcwg-benchmark-results.log | 6 +- results_id | 2 +- 19 files changed, 120 insertions(+), 120 deletions(-) rename results_id.first => 09-check_regression/results_id.first (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gcc/master-arm updated (69fe1bbafa -> a2666ea2f4)

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_fast_check_gcc/master-arm in repository toolchain/ci/base-artifacts. from 69fe1bbafa 35: force: #55: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new a2666ea2f4 36: force: #57: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] 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 2044 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 49568 -> 50096 bytes 04-build_abe-gcc/console.log.xz | Bin 235120 -> 236056 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8648 bytes 07-build_abe-glibc/console.log.xz | Bin 232892 -> 232832 bytes 08-build_abe-gdb/console.log.xz | Bin 46736 -> 47288 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9520 -> 9536 bytes 11-check_regression/console.log.xz | Bin 1668 -> 1660 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.regressions | 16 +- 11-check_regression/trigger-bisect | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 16 +- mail/results.regressions | 16 +- manifest.sh | 10 +- results | 16 +- sumfiles/g++.log.sep.xz | Bin 1440 -> 1440 bytes sumfiles/g++.log.xz | Bin 1412 -> 1408 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 4 +- sumfiles/gcc.log.sep.xz | Bin 4796 -> 6224 bytes sumfiles/gcc.log.xz | Bin 377208 -> 377672 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 736 +++++++++++++++++++------------- sumfiles/gfortran.log.sep.xz | Bin 1448 -> 1448 bytes sumfiles/gfortran.log.xz | Bin 56792 -> 56356 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 4 +- sumfiles/libatomic.log.xz | Bin 436 -> 436 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 436 -> 436 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 436 -> 436 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 444 -> 444 bytes sumfiles/libstdc++.log.xz | Bin 428 -> 428 bytes sumfiles/libstdc++.sum.sep | 2 +- 41 files changed, 503 insertions(+), 351 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023