Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[gcc] branch releases/gcc-10 updated (22055748e5f -> dd2cd1e7050)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from 22055748e5f Daily bump. new dd2cd1e7050 Fortran: fix compile-time simplification of SET_EXPONENT [P [...] 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/fortran/simplify.c | 12 +++++----- gcc/testsuite/gfortran.dg/set_exponent_1.f90 | 36 ++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+), 6 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/set_exponent_1.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch releases/gcc-11 updated (ed643a18359 -> dfcdb457c46)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from ed643a18359 Daily bump. new dfcdb457c46 Fortran: fix compile-time simplification of SET_EXPONENT [P [...] 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/fortran/simplify.c | 12 +++++----- gcc/testsuite/gfortran.dg/set_exponent_1.f90 | 36 ++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+), 6 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/set_exponent_1.f90 -- 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_size-cpu2017rate/llvm-arm-master-O2_LTO updated (cbbb50b838 -> 6450fdcd65)

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_size-cpu2017rate/llvm-arm-master-O2_LTO in repository toolchain/ci/base-artifacts. from cbbb50b838 1: onsuccess: #6: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 6450fdcd65 2: onsuccess: #7: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] 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 1876 -> 1876 bytes 02-build_bmk_llvm/console.log.xz | Bin 231148 -> 237992 bytes 03-benchmark/benchmark-build.log | 117 +- 03-benchmark/benchmark.log | 115 +- 03-benchmark/console.log.xz | Bin 3920 -> 3960 bytes 04-check_regression/bmk-specific-variability.csv | 11 + 04-check_regression/console.log.xz | Bin 5636 -> 5972 bytes .../output-bmk-results/exe.improvement | 1 - .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression | 1 + .../output-bmk-results/exe.regression.diff | 1 + .../results_id.first | 0 05-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - git/llvm_rev | 2 +- jenkins/dashboard-push.sh | 7 - jenkins/notify.sh | 2 +- manifest.sh | 12 +- results-vs-first/compare-results-internal.csv | 44 +- results-vs-first/csv-results-1/perf.csv | 92 +- results-vs-first/csv-results-1/results.csv | 1587 +++++----- results-vs-first/csv-results-1/size.csv | 1513 +++++----- results-vs-first/results-brief.csv | 42 +- results-vs-first/results-full.csv | 102 +- results-vs-first/results-internal.csv | 48 +- results-vs-first/results.csv | 48 +- results-vs-first/tcwg-benchmark-results.log | 1770 +++++------ results-vs-prev/compare-results-internal.csv | 44 +- results-vs-prev/csv-results-0/perf.csv | 87 +- results-vs-prev/csv-results-0/results.csv | 3084 ++++++++++---------- results-vs-prev/csv-results-0/size.csv | 3015 ++++++++++--------- results-vs-prev/csv-results-1/perf.csv | 92 +- results-vs-prev/csv-results-1/results.csv | 1587 +++++----- results-vs-prev/csv-results-1/size.csv | 1513 +++++----- results-vs-prev/results-brief.csv | 42 +- results-vs-prev/results-full.csv | 102 +- results-vs-prev/results-internal.csv | 48 +- results-vs-prev/results.csv | 48 +- results-vs-prev/tcwg-benchmark-results.log | 1630 +++++------ results_id | 2 +- 41 files changed, 8403 insertions(+), 8440 deletions(-) delete mode 100644 04-check_regression/output-bmk-results/exe.improvement delete mode 100644 04-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 04-check_regression/output-bmk-results/exe.regression create mode 100644 04-check_regression/output-bmk-results/exe.regression.diff rename results_id.first => 04-check_regression/results_id.first (100%) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh 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_native_fast_check_gdb/master-arm updated (503a77a6ac -> 778b7aedcd)

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-arm in repository toolchain/ci/base-artifacts. discards 503a77a6ac 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 887c4fc246 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 298d809f7c 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4d8926a700 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ef768646e5 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d145ae7061 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 15e57ecb97 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 219ef219cb 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 07a008e65e 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards b0a21a5722 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1067196613 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 21d7e33ef1 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards ea501ee338 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards b966152f47 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards b6fbd43e8a 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5b13844f12 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 29ee848a0a 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards a53da6fb64 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 2f582b4f2a 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 6e4cf44c5f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards c254c283ac 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 6ae100c8b7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards cedd028571 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 140b0599a9 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 18305fec86 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards fc225ecb75 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards db53b20366 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 2f10917a37 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 2e31180ba3 121: force: #26: : Failure after baseline build: no new commits discards 678a41d4db 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 0031291d5c 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards e61f5083b5 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 3f24e4b972 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 1ae627faa8 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards f3939d02df 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards fa8d3784a0 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards e21aba53c4 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 44cb7a7f77 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards dcd3711583 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards e380614f48 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3d344dd591 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 006fb12e43 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards e7187dddef 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3d7c198af0 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards e10c3cbeba 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 76c76bd13e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards c8a43ef794 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ab5a0d26ee 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards eb773746f3 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards a54c027a07 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 026c5be3fd 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards bb9b043fd4 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 36304bfaa3 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 834b032a47 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 8a83333cf6 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards f64f7bccad 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 5b46e4ad35 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards c3a80e8bd8 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 819018574c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards cc865117e2 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards ef3fb09a93 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 3aff44e533 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5c577bc280 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards d8e537ca0c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 2f7faceaa4 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 2b2d9e060a 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards bf7620235b 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards e99185d8e8 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards fde6dbceb6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards cee95b6ac8 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 97796e8467 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 5786afe31e 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 5b648269e8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 72bad4bdbb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards e7f992b8c4 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 02222be65a 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 824c755fdf 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards ace03d4852 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 809f4963ab 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 9a8c820a2f 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards a6a262c6ea 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 1d452f3b8f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 87ce0440a2 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 19838bd0b8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 499047c6f3 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards d7f389cd37 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 4a1c349c4b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 6d204b2293 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards d3ea1a178b 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards f3485443fd 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards fdb6bb24b6 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards ed8befa0e3 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 92b5413c97 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 4efa8d8fa9 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards b0a0c05f88 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards f59e30feb3 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 7d3740c423 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards cd64e16b1c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 0703e917de 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards f2459dac70 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d58d486e2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 6697dbcc22 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 4ad276963f 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new d69ab42da9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 84fe0c150a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 7592259800 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 95eeab04ba 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new c9fa7dd0b7 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 352a86a6f2 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new ca368d48e9 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 499871400f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 634b5c478f 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new d1e7ce9854 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 6f3e3a3784 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new dac7ff59a5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 8f3b82c946 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 8b5f93d6dc 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 51bd58420c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new c7afbeec8c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new a66bb35f3a 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new db3823432b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 53551111ca 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 2ec802c142 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 0791274d02 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 1628a7d8fb 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new cbc3cee3fd 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 7b4c717312 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new ad01f858a7 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 2bab72b9f1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 00e9bb0e73 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new f1007ae99c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new c7e57c854e 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 0c0aedd9dd 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 2dab10d1bb 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new b188117220 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 2d14baf6cb 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new d4abfb88ee 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 831996b0a0 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 3eb20685df 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new ffb5840998 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 300a68de93 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 60a787e112 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 0d5d2ea8be 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new d4f7fd31c6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 98c9d372d0 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new e4eca772bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 28cb307f5d 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 87d1b0c41a 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new e7b5ee3f60 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 7dd8601f4b 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 450700337f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 900310c010 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new fc0bbc1acb 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 0ef5521183 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 1188db75d4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new fb7f5421ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 73d241bbc3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 5a5dde367a 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 30ae1afa57 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new e5b803d06e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b626173e0c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 7f933d27ef 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 29293d96b9 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 2bc88fb4bc 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 47a5faef60 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 93fec16608 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 14c597de7c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 1d68412565 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ba9d925061 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new ae49afec34 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 6ee4b389b6 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9399eadbe0 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 4b94129d98 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 4719e24ee6 121: force: #26: : Failure after baseline build: no new commits new c7322210ab 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3986fe1e51 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 81d245e0f5 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7428735da7 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new feb91fd7c7 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new a136295ca0 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 166add88d7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 4b8bfc2408 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new d4bf8de028 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 86b2437bbb 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new fd439eb5c3 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 0461e6f671 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 44ed05c2da 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new a9aaa85457 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 0c839ddfc8 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new e6bf01653d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 3c56396abc 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 23b44720f8 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new bc7cfa2232 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 370f2eeed9 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 8d25eb89ef 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a5065b3c4f 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new e26f25f12e 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 693df2ce28 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 138fb5e9d2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 50e2d19182 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2ce38b79bd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 5f275bbc98 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 778b7aedcd 150: onsuccess: #65: 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 (503a77a6ac) \ 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 2200 -> 2220 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49220 -> 48904 bytes 04-build_abe-gcc/console.log.xz | Bin 236160 -> 235504 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8452 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 233052 -> 233108 bytes 08-build_abe-gdb/console.log.xz | Bin 46416 -> 46496 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1732 -> 1716 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 64 +++++++++++++++++----------------- 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, 53 insertions(+), 53 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_gnu_native_check_binutils/master-aarch64 updated (1f29c93615 -> fb840583cb)

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_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 1f29c93615 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards d1cc2bad8f 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards a3e95262d5 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 75d54987a0 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 904ee82495 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 9c349cb42a 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 87c56f5c67 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9788e29ed0 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d051b4339a 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 36ea684b03 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 0d0a886d50 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 7836550b48 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards deae5c8caa 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 2eca85a6d6 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 6885ba8356 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards c6f26709ba 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards b3c4765793 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 5ce91fe2ee 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards d01b3ebc51 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards a395609271 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards bed0d88d85 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 39eace3318 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 15f20f1ef1 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 10e8b441e0 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 5612cbe3ed 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards bb2f34acd1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 8bc943bc83 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards a01dd5758a 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards c63ea30806 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 6780c3bd81 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 7daaf1bd00 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 4383761db8 212: force: #24: 1: Success after binutils: 2 commits discards 994b723a52 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 7578108b5f 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards b3928cc288 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 05481b29a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 1885c593f6 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards ee65b84c51 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1d4166ae99 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 0e784d7713 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards af6d5dfe3d 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 99d7ea9982 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards a7dc000e3b 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 8f403b66e6 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards ccead872f5 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 4322c11f75 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards d7d0856374 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 0885c84a09 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 50f67bb9ae 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards a10371b012 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d6ab22eec 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 51f6cea97c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 0ed2234a6f 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 05f98e1675 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards fd9341d175 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 2c5f4e0114 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 28c2a58759 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards ee4d34cc2a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 57d906a50a 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 6f66167e24 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards ffa82596f2 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 0939d1105f 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 2c8cedba5d 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 94a52e8e2e 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 1d6654bb3e 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards dfd47923ff 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 50375866b4 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 76078a1cba 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards cb878fed18 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 4ca5b67db7 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards aba1a510ff 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 45aa770fcc 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 9958243090 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards f6fdd28e13 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards b05dc76106 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 75a5df625e 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards d89f7b39a6 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 7420ac7c9a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 7bd139e103 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards c6cc914455 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 4f33021ac7 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 50e9690e0b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards faf7c9d93c 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 126598f547 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards dd2756672e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards f8f7a23f53 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 22778577a4 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards bff2d1d462 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 11d20e5aea 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 11e940f8df 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 6d1255cb88 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards add0bb3d26 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards eb680dba23 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards eba15acc72 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 437a1e3419 149: onsuccess: #684: 1: Success after linux: 10 commits discards 04f4e63ca5 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 1be638489a 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 21a90ab7ff 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 51fac635e6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 69691b961a 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards fe3117963e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new bce104da6a 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new c71cd11cc2 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 12252c8c11 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 2a85fa396b 146: onsuccess: #680: 1: Success after binutils: 20 commits new 0b3f39a8f7 147: onsuccess: #681: 1: Success after gcc: 6 commits new 8bfeae6833 148: onsuccess: #683: 1: Success after glibc: 9 commits new aa5c6738df 149: onsuccess: #684: 1: Success after linux: 10 commits new 4a25f373ff 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new b9be66ac30 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 8eb7f99c59 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new a828599d0f 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new a9522a3209 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new ac1f148551 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new ce028aa30b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 66c281e75c 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 02511a8779 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 6418c7d11d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new c2afd7576d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new bb40843b20 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new ab2941e94a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 67a589657a 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 8721dff9c1 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new b224678ffe 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new db001f0089 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 9cb4098afa 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 34932536e9 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 40793fcdf4 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 20f7cb959a 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 75a5a3b90b 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new ed9e433e21 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 5ea06b55e4 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 6fc143a72d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 2f6963bbdc 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new d711e4d850 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 0cc9f80537 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new e128bbf31f 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new dc7ff6f165 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new b977e22b55 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new fc82bdfe2b 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new de751aa680 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 9000b79a11 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 5c6f30ebae 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 96a6150840 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 53a576e2a9 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new cbe63d1212 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new f24b8d43be 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 67807321e8 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 1ecd24871c 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new ec1dfa05c3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new bd1143169f 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 0f09a69176 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3ecdf5e7db 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 453220280a 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9c8608699f 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new ced1f73c32 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 46d949e5e9 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 86af63c1f4 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 4720ba3a16 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a1050a4dd5 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 35c6933efa 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 33529afaac 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 404eb27265 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8b93ec353a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new fa6ca72f67 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new b0b2fca4e4 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 19de522c1e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 828a5cd216 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 47624f8716 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 1c2c4d313f 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 465408eb68 212: force: #24: 1: Success after binutils: 2 commits new b874b00d7a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 5a1146ae5f 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0d32f100dd 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 38bd2fe4c1 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new b59243c2a1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 3193e7e7f8 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new cfbb6e71c6 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 6ae73efe44 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a7009193af 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 77e9ac3eaf 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new a8575004ec 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new d8e4327e69 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 36d3dd35f5 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 61b16d9c9d 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 4479544f99 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new da963b4a90 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 0a430d0630 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 42590151b9 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 6d32db029c 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 40539e4d15 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 288750e969 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new f35f3a0349 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 6abdb769e3 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new eb7f1097c9 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 92894e1e84 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5df71dd7f7 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c9040e56ea 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new da6c131f8e 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 4bbeaf4b6a 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 8637d6ae4e 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new cf56f70c3d 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new fb840583cb 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] 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 (1f29c93615) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2240 -> 2232 bytes 02-prepare_abe/console.log.xz | Bin 2556 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 35908 -> 36016 bytes 04-build_abe-gcc/console.log.xz | Bin 203404 -> 204860 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8932 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 241452 -> 241136 bytes 08-build_abe-gdb/console.log.xz | Bin 35048 -> 34980 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3004 -> 2996 bytes 11-check_regression/console.log.xz | Bin 1600 -> 1612 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.regressions | 8 ++-- 11-check_regression/trigger-bisect | 4 +- 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 64 ++++++++++++++--------------- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++-- mail/results.regressions | 8 ++-- manifest.sh | 8 ++-- results | 8 ++-- sumfiles/binutils.log.xz | Bin 62664 -> 62616 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150712 -> 150812 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122644 -> 122644 bytes sumfiles/ld.sum | 2 +- 28 files changed, 64 insertions(+), 64 deletions(-) delete mode 100644 11-check_regression/trigger-notify -- 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_profiled_lto updated (a96ee38b50 -> 3fe6cabbe1)

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_profiled_lto in repository toolchain/ci/base-artifacts. discards a96ee38b50 216: onsuccess: #59: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2c371deaa2 215: onsuccess: #58: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 35f1f466cd 214: onsuccess: #57: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3e4ef31043 213: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 18ccf8efd2 212: onsuccess: #55: 2: [TCWG CI] Success after binutils/gcc [...] discards f4f2874853 211: onsuccess: #54: 2: [TCWG CI] Success after binutils/gcc [...] discards 2dba1a4d0e 210: onsuccess: #53: 2: [TCWG CI] Success after binutils/gcc [...] discards 72e32ca244 209: onsuccess: #52: 2: [TCWG CI] Success after binutils/gcc [...] discards 4afd9859f1 208: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] discards 4a0a566f29 207: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] discards e1f5c680bc 206: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] discards 4ce157930f 205: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards dd7aa0941a 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards 112f3f505b 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] discards f1df06cf97 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards ca23f12efa 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards cb3b9bdcf0 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards 9a18ce76c3 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits discards 507abbcc8a 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] discards dd73e27b2c 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits discards 7f30396ebd 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: 59 [...] discards 3518877545 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits discards 35fbbe7cc7 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits discards 0709afa6be 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits discards 40d75fb3f4 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits discards f419ebd19c 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits discards 7bef7e925f 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 6c4c5479c8 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards 93da172cdf 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards 794c06f2f7 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards 56cf739fa3 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards e7f572f728 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards c753ca68ff 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards 4699d47672 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards 27765ae17c 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards 47f528ee3d 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards dea9827aaa 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards 456a8792d1 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards df8451ea98 178: onsuccess: #16: 0: Success after binutils: 15 commits discards 695495848f 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] discards eb90c1f42a 176: force: #14: 2: Success after binutils: 18 commits discards dbf871d90c 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards fbac31d78c 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards 0879475c68 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards 35ab262291 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards b1e16043ce 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards 7225b31b87 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards e9f553491f 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 9095a8423b 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 21d00666ce 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 5de2cf4ead 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards 237b4b9589 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards 72dd6c22e3 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards ddf84c3aa5 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards 5d756a1309 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards 63e824fd63 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards daecccc88b 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 0d6bd7bb9e 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards 6c9c480f18 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards f4bfdb88e0 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards 3fe01e5537 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards 8187646b7a 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards 2be0416408 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards 03179fce45 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 45d60cf5a4 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards 5679aa3a8a 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards ee25483904 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards 72e0ace3ad 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards ececf11757 148: onsuccess: #571: 2: Success after gcc: 4 commits discards aea6cc004f 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards 4dbb7f188d 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards 54bd63e5bd 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards 75bb421ef8 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards ab2aa9960b 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards 8c36e278c4 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards c6966d556c 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards 104d0cc2e0 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards f524f1e407 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards 25c09677b2 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards 7a290b2c8f 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 8da1d1935a 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards a0a0eca63a 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards 486cb7596b 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards 61e3717401 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards bf30df48eb 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards 4067c6ddeb 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards bfd949a9a8 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards 7a15d227e1 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards 36280cb079 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards e4f43be11d 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards 5bc712139b 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards d0d6dec806 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 200b9a79d7 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards 13bcd04796 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards 6678bb09d4 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards 7310254797 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards ca83f810cc 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards 84ea424127 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards 69dbdb7c0c 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards 57e0d10442 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards 7ba6fc8d9a 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new 066e9994d7 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new de3d19b5f9 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new 12d3b7ec22 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new 8caf2192a1 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new 6702501657 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new 858cfd6379 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new 74db371224 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new b487355e0e 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new adb7a1df9e 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new bc9b2ff67d 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new bb894c6a28 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new 45df8c5173 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new 3de20cc4ec 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new 1d99fa758f 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new 7293fd76a3 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new 32c7dfbcfc 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 566d860b33 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new 9981d95034 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 83f46d1500 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new 6574124148 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new caf8d3fc5a 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new 6399fbd25d 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new 89c0dbecbb 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new e09f1736f2 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new 19a5f44d85 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new bfe7a2dfbe 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new 2c4b3aff6b 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new 5bab4892df 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new 62f9f8125f 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new 90a786ab4c 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new 5d4a2afddd 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new e250a65947 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new 58def6dcbc 148: onsuccess: #571: 2: Success after gcc: 4 commits new 7d20f690bf 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new 1a53ab5c2b 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new bb17842cd6 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new d644dfcb00 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new fa163cb3c1 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new e566f5d25d 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new bc0a0daf6b 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new ae0dd659cb 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new b6baaa93db 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new 35b7a56e13 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new f0cfd10299 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new 0ef6790e47 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 4a1a894159 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new b177f028dc 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new 9d6e8ac713 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new 8d916c8839 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new dd23b1749b 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new db701ab259 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new c09ba3a0ef 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new aa25de87cd 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new 5184702732 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new 1ab1f22bc1 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new 853ac27c8c 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new 5bcb4ea047 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 08773cb063 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new e3aae67916 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new be8363ab96 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 7cc754464a 176: force: #14: 2: Success after binutils: 18 commits new af7d3887de 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] new b19a968f86 178: onsuccess: #16: 0: Success after binutils: 15 commits new f05ea7387c 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new 0f8f196441 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new 1a900e54c3 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 386cb46066 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new 87ffde9dc3 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new c58e3f2599 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new 4a156aca8d 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new 2854bff353 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new 439517d5a8 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new a1390e8cc2 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new e14b137d18 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new c5d0d3579f 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new 3e9bd8c806 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits new e0fee214da 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits new ae0cea3146 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits new 465ccdeada 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits new d995ad20da 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits new 273db3f4c0 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: 59 [...] new d522f136fb 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits new b8ae4c9db4 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] new 3998c38276 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits new 6da323ad0b 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new e8a9eea8d9 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new 80b7bdc8b1 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new 771276f11d 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] new 2c8b015e38 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new 580e66c9aa 205: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new f9621251e2 206: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] new a08e7b6c3d 207: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] new f699424165 208: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] new 7d56588952 209: onsuccess: #52: 2: [TCWG CI] Success after binutils/gcc [...] new 4b89d4586e 210: onsuccess: #53: 2: [TCWG CI] Success after binutils/gcc [...] new dbd8f2ce2f 211: onsuccess: #54: 2: [TCWG CI] Success after binutils/gcc [...] new 3325a70258 212: onsuccess: #55: 2: [TCWG CI] Success after binutils/gcc [...] new fb90f0952e 213: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 8818055849 214: onsuccess: #57: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new e79903c3ab 215: onsuccess: #58: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 9b6176679e 216: onsuccess: #59: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 3fe6cabbe1 217: onsuccess: #60: 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 (a96ee38b50) \ 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 1948 -> 2112 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 04-build_abe-binutils/console.log.xz | Bin 49028 -> 49284 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 611836 -> 612164 bytes 06-check_regression/console.log.xz | Bin 548 -> 552 bytes 07-update_baseline/console.log | 64 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 16 +++--- 10 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] branch master updated (3e7bb4f24617 -> 6c538e1adbfc)

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 3e7bb4f24617 Merge tag '6.3-rc6-smb311-client-negcontext-fix' of git:// [...] new e7067a446264 ksmbd: avoid out of bounds access in decode_preauth_ctxt() new 6586c4d48018 Merge tag '6.3-rc6-ksmbd-server-fix' of git://git.samba.org/ksmbd new d83806c4c0cc purgatory: fix disabling debug info new dcc11ac9dcaf Documentation/llvm: Add a note about prebuilt kernel.org t [...] new aa7d233f45b4 kbuild: give up untracked files for source package builds new 5efb685bb3af initramfs: Check negative timestamp to prevent broken cpio [...] new 735faf92fb06 init/initramfs: Fix argument forwarding to panic() in pani [...] new f6d8283549bc kbuild: merge cmd_archive_linux and cmd_archive_perf new f8d94c4e403c kbuild: do not create intermediate *.tar for source tarballs new 3c65a2704cdd kbuild: do not create intermediate *.tar for tar packages new f0dd81db3eac Merge tag 'kbuild-fixes-v6.3-3' of git://git.kernel.org/pu [...] new b277fc793daf powerpc/papr_scm: Update the NUMA distance table for the t [...] new 4a1c388ce052 Merge tag 'powerpc-6.3-5' of git://git.kernel.org/pub/scm/ [...] new 775d3c514c5b x86/rtc: Remove __init for runtime functions new e623175f6418 Merge tag 'x86_urgent_for_v6.3_rc7' of git://git.kernel.or [...] new 91dcf1e8068e sched/fair: Fix imbalance overflow new 6c538e1adbfc Merge tag 'sched_urgent_for_v6.3_rc7' of git://git.kernel. [...] The 17 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: Documentation/kbuild/llvm.rst | 4 ++ arch/powerpc/mm/numa.c | 1 + arch/powerpc/platforms/pseries/papr_scm.c | 7 ++ arch/riscv/purgatory/Makefile | 7 +- arch/x86/kernel/x86_init.c | 4 +- arch/x86/purgatory/Makefile | 3 +- fs/ksmbd/smb2pdu.c | 23 ++++--- init/initramfs.c | 11 +--- kernel/sched/fair.c | 10 +++ scripts/Makefile.package | 64 ++++++++++--------- scripts/package/gen-diff-patch | 62 ++++++++---------- scripts/package/mkdebian | 103 +++++++++++++++++------------- scripts/package/mkspec | 11 +--- usr/gen_init_cpio.c | 12 +++- 14 files changed, 172 insertions(+), 150 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_gnu_native_check_binutils/master-arm updated (293812cf9f -> 309bd39bb7)

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_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards 293812cf9f 247: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 21c79628e8 246: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 6c141079cf 245: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 386e649c8d 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 84fe980d20 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards e917268a2d 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 3abb29fcd4 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3d4f3934b1 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2aaf702672 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards de87bee23f 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 41a9cd57c7 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards c86ef11821 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 91bb22cbb1 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 6c35b20bcb 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1483ea4c9b 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 0b7ef9810f 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 68c71f8e18 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 884d2151d5 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards d2188c5065 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5e6a5e8fd9 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 313d72642f 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards b711b93a55 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 9ede714a29 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 59761a427f 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 6ba620c1b4 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 459416a52f 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 8eebfb5bf0 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 0a6ff06c78 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards a3c53c2b8b 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 8f02a9750b 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards cb9f5f500e 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 581ae08847 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 774f62aa11 215: onsuccess: #26: 1: Success after binutils: 10 commits discards e11be22eb2 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards b4cfbb9804 213: force: #24: 1: Success after binutils: 2 commits discards 2df2aa9213 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards c27c4b77b8 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards b4a6f917ee 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 2c5f73e0ff 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 6f46fd918b 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 458a81c6da 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards af003049a2 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a22b00a28f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 779007fc22 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards abf50085b7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 24300af67b 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 904342bc63 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards c35f0aa8d7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9bec861944 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards fb33b27ded 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards f8428c59a5 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards a8a87751d5 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 28c75a5b39 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a5484d1260 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 89b4c656e3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 67b7ac95d4 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 0216159ed0 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 83ce744dea 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 8f0c7fcee9 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards d3ad365b96 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 466423cdac 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards ddc64fe9ee 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 7a4a096aed 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards e799e7fac8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 99de265b8f 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 1cc8d9d239 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards c6db6b80dc 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 27d97965a8 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards ac3704d6d8 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards cdbd25b5b4 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards de6db45da6 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 33a905883c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 7d3c571098 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 839ebf9a65 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards ac79ad5e18 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards d549946f9e 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 8f99189da4 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 2424a10e59 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5dae1ffe55 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards ca87a85330 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 9e6a6eb061 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards e6d372103a 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards b517fea732 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards c0425237e4 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 2d8450c72a 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 9ab6bebad5 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 569c316060 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 7886dc0182 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards a3b5de806b 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards e51b4c6e5d 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards a66520ee8a 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 7a98475c9f 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 161ce59330 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards a2ac2b0288 154: onsuccess: #583: 1: Success after linux: 10 commits discards 8b281e88b3 153: onsuccess: #582: 1: Success after glibc: 9 commits discards a02d008720 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f3a540b09b 151: onsuccess: #579: 1: Success after binutils: 21 commits discards d9e110c667 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 974d0754be 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards c828a0ec8f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 2a65b29f46 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new f254fed5dc 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 10cf5bbecd 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 0453b831c4 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 4b54560dcb 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 4961baeb5f 151: onsuccess: #579: 1: Success after binutils: 21 commits new 4c37fea7e2 152: onsuccess: #580: 1: Success after gcc: 6 commits new 5716b5d767 153: onsuccess: #582: 1: Success after glibc: 9 commits new 64913b94f5 154: onsuccess: #583: 1: Success after linux: 10 commits new 6187ac1ddb 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 3f3145c6f1 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 8152a31b4a 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new de02894e14 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 8cc918ec39 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 78e0a8ce87 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 8829b12242 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new d361f64ba7 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 9be4746625 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 94107cf0c4 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new f664c4a982 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 4435ccb89c 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 5f0122fc85 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 9c75bd0a71 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 5c0f4816e6 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 9051e34d0d 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 92c8501f45 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 2e13f74486 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 8552cdd657 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 949075c6c0 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 38f8743834 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 7c41040aa6 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 3afcf16661 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 2b183975c3 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 49e9de4cff 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 854cce361d 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new b3d090ad4b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 71256d7d58 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 60bcdd7160 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new 436b51afdf 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new ca119e66d7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new db87077a07 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new f8d7ec36ee 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 196454ffb0 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new b108fd72a7 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 1c81c7cb72 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new f15523b955 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new ea7180b4d7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 64319d3aff 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 4be9668621 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 10cf2fed88 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new dee6eadc86 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 663cc90c26 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 37b9cc08ac 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 504d827368 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 0c5631c2a3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 255ba2fe5d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 879583d7dd 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new c43f5c842f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 9ed9fcfd55 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8037e2538e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ea0f926028 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 348d1c9f43 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 512ed9accc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 69940a9525 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d0b0c10317 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 290c15db65 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 1b38460793 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 567b985742 213: force: #24: 1: Success after binutils: 2 commits new b99037b9be 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new bb13d76dc3 215: onsuccess: #26: 1: Success after binutils: 10 commits new edb9607183 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new c2eda3e002 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 6d18ad2dc9 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 7ec363cd07 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c5dedb3ceb 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 3146e5dd79 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new a996b59210 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f7346eeead 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 1ba84a5087 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6b870d9a08 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 78d0ad2cee 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 8401314823 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 6a4eee6b03 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new aaea2c3f66 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 128a09f086 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new e781e7107f 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 0d985a800a 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 301eedfb2d 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new cb37ce116c 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 25ca38c404 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new d355fd2bae 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a72005d506 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 54a78566a7 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c7fb670091 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 39fb20bdf7 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d12cacb3e4 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f0c4b22271 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 41895bb8b0 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new ab12e2bd51 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new c05311f281 245: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new aa961c5b1b 246: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 6d53a789ab 247: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 309bd39bb7 248: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] 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 (293812cf9f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2032 -> 2184 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 50356 -> 49392 bytes 04-build_abe-gcc/console.log.xz | Bin 236844 -> 238376 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 232788 -> 232572 bytes 08-build_abe-gdb/console.log.xz | Bin 46984 -> 47144 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3856 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3012 -> 2456 bytes 11-check_regression/console.log.xz | Bin 1616 -> 1604 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 4 +-- 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 44 ++++++++++++++--------------- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 8 +++--- results | 8 +++--- sumfiles/binutils.log.xz | Bin 62176 -> 62456 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100948 -> 100584 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132324 -> 132312 bytes sumfiles/ld.sum | 2 +- 28 files changed, 54 insertions(+), 54 deletions(-) create mode 100644 11-check_regression/trigger-notify -- 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 (24d66f3f -> 254b78b2)

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 24d66f3f Add entry b8d1a3a8ef9aff015ae963522287f7785bc552ec from https [...] new 254b78b2 Add entry e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722 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: .../tcwg_gnu_native_check_binutils/master-arm/build_url | 2 +- .../master-arm}/last_good | 0 .../tcwg_gnu_native_check_binutils/master-arm}/summary.txt | 10 +++++----- .../status.txt | 14 +++++++------- 4 files changed, 13 insertions(+), 13 deletions(-) copy binutils/sha1/{b8d1a3a8ef9aff015ae963522287f7785bc552ec => e10d82fc3ed03ee03f [...] copy binutils/sha1/e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722/{tcwg_gnu_woa_check_bi [...] copy binutils/sha1/{acdf60711d44d20608873bec0376688c9a80e281/tcwg_gnu_woa_check_bi [...] copy binutils/sha1/e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722/{tcwg_gnu_woa_check_bi [...] -- 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 (70fb752498 -> 69fe1bbafa)

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 70fb752498 34: force: #53: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 69fe1bbafa 35: force: #55: 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 1992 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49004 -> 49568 bytes 04-build_abe-gcc/console.log.xz | Bin 236696 -> 235120 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 233492 -> 232892 bytes 08-build_abe-gdb/console.log.xz | Bin 46736 -> 46736 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3800 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9792 -> 9520 bytes 11-check_regression/console.log.xz | Bin 1660 -> 1668 bytes 11-check_regression/results.compare | 10 +- 11-check_regression/results.regressions | 10 +- 11-check_regression/trigger-bisect | 4 +- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 10 +- mail/results.regressions | 10 +- manifest.sh | 8 +- results | 10 +- sumfiles/g++.log.sep.xz | Bin 1440 -> 1440 bytes sumfiles/g++.log.xz | Bin 1408 -> 1412 bytes sumfiles/g++.sum.sep | 2 +- sumfiles/gcc.log.sep.xz | Bin 4980 -> 4796 bytes sumfiles/gcc.log.xz | Bin 377100 -> 377208 bytes sumfiles/gcc.sum.sep | 589 ++++++++++++++++---------------- sumfiles/gfortran.log.sep.xz | Bin 3644 -> 1448 bytes sumfiles/gfortran.log.xz | Bin 56708 -> 56792 bytes sumfiles/gfortran.sum.sep | 163 +-------- 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 +- 37 files changed, 330 insertions(+), 498 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