Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Os_LTO updated (87cd78da0e -> 95a82ab480)

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-spec2k6/llvm-arm-master-Os_LTO in repository toolchain/ci/base-artifacts. from 87cd78da0e 48: onsuccess: #9: 1: [TCWG CI] No change after llvm: 202 commits new 95a82ab480 49: onsuccess: #10: 1: [TCWG CI] No change after binutils/gc [...] 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 1804 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31492 -> 31572 bytes 04-build_abe-stage1/console.log.xz | Bin 94284 -> 93648 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 238948 -> 239252 bytes 08-build_abe-stage2/console.log.xz | Bin 217936 -> 225068 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 61392 -> 64584 bytes 10-benchmark/benchmark-build.log | 84 +- 10-benchmark/benchmark.log | 82 +- 10-benchmark/console.log.xz | Bin 3956 -> 3888 bytes 11-check_regression/console.log.xz | Bin 5796 -> 6704 bytes .../csv-results-vs-first-1/perf.csv | 115 +- .../csv-results-vs-first-1/results.csv | 3248 +- .../csv-results-vs-first-1/size.csv | 128682 +++++++++--------- 11-check_regression/csv-results-vs-first-1/sve.csv | 12 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 117 +- .../csv-results-vs-prev-0/results.csv | 3218 +- 11-check_regression/csv-results-vs-prev-0/size.csv | 3096 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 115 +- .../csv-results-vs-prev-1/results.csv | 3248 +- 11-check_regression/csv-results-vs-prev-1/size.csv | 128682 +++++++++--------- 11-check_regression/csv-results-vs-prev-1/sve.csv | 12 +- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 111 +- 11-check_regression/results-vs-first-internal.csv | 50 +- 11-check_regression/results-vs-first.csv | 50 +- 11-check_regression/results-vs-first.log | 852 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-full.csv | 123 +- 11-check_regression/results-vs-prev-internal.csv | 50 +- 11-check_regression/results-vs-prev.csv | 50 +- 11-check_regression/results-vs-prev.log | 872 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 14 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 14 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 26 +- mail/mail-body.txt | 26 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 71 files changed, 135212 insertions(+), 138211 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (e8cac3c80a -> e002d03dd5)

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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards e8cac3c80a 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] discards 7be6e85e21 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] discards 88c054ee34 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] discards 54b5e01251 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 8b3f777258 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] discards 1b959a7f38 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] discards d2eba127bf 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards 130032212c 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 328b0d29a4 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 35a29db497 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 7f7e810757 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards d2f94b8228 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards 93b31f52ad 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards bcd6af9342 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards a68e149fb4 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 9c44c832ba 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 30ec709ee0 152: onsuccess: #903: 1: Success after linux: 22 commits discards c4544ecb3b 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 3a76dedc49 150: onsuccess: #900: 1: Success after gcc: 11 commits discards cb00f0af6b 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 2da3337c45 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards efd1480d4e 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards b0c1119019 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 3beaa5daf9 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards b319b6fc53 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 54e8c38bd7 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 8a99065c3c 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards baff0a41b5 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 1468f3a60a 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 6838eb9f3b 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 8155a117be 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards ef953d4d0e 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 792973c571 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 9aad53fa55 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards ca0c8a4c59 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 06bd955387 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards ee2634dbb0 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards a9ca1255b9 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 1dd073a4b8 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 7b2ab4020b 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 680e6cd19e 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 4d111a30bb 127: onsuccess: #874: 1: Success after linux: 219 commits discards 53e9923adc 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 3369d94ec6 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 801a360a55 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 6568105bee 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 6f48c2e1a9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards c7a3402017 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards b794e0568f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards a883dd66b5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards f01b5dbe2b 118: onsuccess: #863: 1: Success after linux: 12 commits discards ef3a350c8e 117: onsuccess: #861: 1: Success after binutils: 18 commits discards e9607c82c5 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 5e59b72eb5 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 0517492aef 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 63fa5a8189 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards c4cb8a8e77 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards ea9e13eddb 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 4c23474848 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 023811ce08 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards c530d294d5 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 521853b26b 107: onsuccess: #849: 1: Success after binutils: 5 commits discards d043d40ff7 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 7f074e12ef 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 6e2e1d0ff4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3b9ec05cb6 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards ea8bd73d1e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards dc5fe9c43c 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards fa17485eee 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards bcd7c35be5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d03bcd4039 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 5664d7cca4 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 837fb35b9b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 25017437e3 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 298636610c 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 6a2d953ecd 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ae6922cf19 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 0e7d583ef2 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 0a45250ad4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 14cb31dea6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards c8d0797001 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 5c224f3214 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5b2563146d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 89bef487b4 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 5e7a012d60 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 280bb9bdea 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards b0b427d6ad 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 109817fa80 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 280852d4dc 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6ef6a34982 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards a7f21f63e3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 19b7b563d1 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 3341754221 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 508988dafa 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 320403372e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 3142385441 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards e175744cc1 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 572c87cbce 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 98ba2b77e1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards e583bf0761 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards c95a849cb3 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new b668abaaab 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 9871c9a56e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new c06d86336d 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f41a414eb6 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new a3df386851 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new a6ed1bfed1 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 47a8017171 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new f0d2575011 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new b5042cca1a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new c566e8e27b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 5dd5e13d30 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 401ff6eff2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 943971b324 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 96874231be 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new bd56f91fe5 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new cae9a30754 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 1a7ff0c730 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new f2b67e3def 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 65cb32ea5c 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 8394238478 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new ebeb37032b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 41218cd745 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 51a19e5035 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 36a555fb99 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new cd352908be 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new a0ba6d4339 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 8a39dba88d 94: onsuccess: #832: 1: Success after binutils: 5 commits new 1902fadef9 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7bafde6b55 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 224dd16fe0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 6c7730bbc9 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new f5065e1979 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 31446c985f 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 56350a0ad9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new cbcf314279 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 3eb46a1e79 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 362de609da 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 9237d5109e 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 8f7577fca9 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 94b8d08d92 107: onsuccess: #849: 1: Success after binutils: 5 commits new 170450d925 108: onsuccess: #850: 1: Success after gcc: 2 commits new adb1d8ca05 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 4685b76442 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 88d1194ebb 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 791b4db7b1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 446ca23efd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 4f351fd566 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new c35b40abb7 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 2f54629e89 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 2b547fab72 117: onsuccess: #861: 1: Success after binutils: 18 commits new 4b65c62b69 118: onsuccess: #863: 1: Success after linux: 12 commits new b65a97f5bc 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 48810ac3be 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new d2b64caed9 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new d5d9a24652 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 78a6434910 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new e11a989f16 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 47ee25f817 125: onsuccess: #871: 1: Success after binutils: 26 commits new 1b87a67e2e 126: onsuccess: #873: 1: Success after glibc: 2 commits new 4bc6d28495 127: onsuccess: #874: 1: Success after linux: 219 commits new 7eb458eb97 128: onsuccess: #876: 1: Success after binutils: 12 commits new 6aabca4cf5 129: onsuccess: #878: 1: Success after linux: 3008 commits new e72de1656a 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 55391e1e65 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 26c91ecff4 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new fa47bcc3e7 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 1f438071c8 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new f3268e4157 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 621d238700 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new ce59d9ecdb 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new f0e006d679 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new e275de264e 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new f607f1e7ea 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 23413e65b0 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 5fe3aa2074 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new b644c32ed7 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new fcb0f9984f 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new e412e1e0f7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 8282f95c6d 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 48bf69a566 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new f84f310a1a 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 6a4e166c75 149: onsuccess: #899: 1: Success after binutils: 15 commits new b26ef6286a 150: onsuccess: #900: 1: Success after gcc: 11 commits new 14b53f8c54 151: onsuccess: #902: 1: Success after glibc: 8 commits new c511f99fd7 152: onsuccess: #903: 1: Success after linux: 22 commits new cbb6417a4d 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new f4ffa8a258 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 621ca92b74 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new 4693764914 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new cad68624a3 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 7bef632ff0 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 9840b3dbb4 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new db5bbe6cc7 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new e92918ec50 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new d6a6cb2457 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new 6c729a214c 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] new 93eda4f6fa 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] new 2c8d17ffd8 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new ed92777762 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] new 28214a5d2a 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] new 8671e1fc28 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] new e002d03dd5 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] 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 (e8cac3c80a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38688 -> 38840 bytes 04-build_abe-gcc/console.log.xz | Bin 215012 -> 212944 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 8700 bytes 07-build_abe-glibc/console.log.xz | Bin 245188 -> 244732 bytes 08-build_abe-gdb/console.log.xz | Bin 38444 -> 38472 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2624 bytes 11-check_regression/console.log.xz | Bin 6112 -> 6352 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 69 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 - sumfiles/g++.log.xz | Bin 3749388 -> 3738720 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 3301224 -> 3320376 bytes sumfiles/gcc.sum | 5012 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1087840 -> 1085808 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232364 -> 232560 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455700 -> 457132 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2780 insertions(+), 2826 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (bc0c6793fb4 -> 36025e8f484)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from bc0c6793fb4 [gdb/testsuite] Fix untested in gdb.base/frame-view.exp new 36025e8f484 [gdb/testsuite] Simplify gdb.base/unwind-on-each-insn.exp The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/testsuite/gdb.base/unwind-on-each-insn.exp | 62 +++++--------------------- 1 file changed, 11 insertions(+), 51 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (e94e9944f59 -> 20552407ae1)

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 gcc. from e94e9944f59 install.texi: Bump newlib version for nvptx + gcn new 20552407ae1 libgomp.texi: Impl. status - non-rect loop nest only partial 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: libgomp/libgomp.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (106f9940631 -> e94e9944f59)

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 gcc. from 106f9940631 tree-optimization/108449 - keep maybe_special_function_p behavior new e94e9944f59 install.texi: Bump newlib version for nvptx + gcn 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/doc/install.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (c90b8902de -> 87e8b0cdc2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from c90b8902de 36: onsuccess: #428: all: Success after binutils/llvm/linux/ [...] new 87e8b0cdc2 37: onsuccess: #429: all: Success after binutils/llvm/linux/ [...] 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 1788 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32420 -> 31116 bytes 04-build_kernel_llvm/console.log.xz | Bin 65596 -> 63796 bytes 05-build_abe-qemu/console.log.xz | Bin 31800 -> 32124 bytes 06-build_linux/console.log.xz | Bin 3188 -> 3092 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4572 -> 4216 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig updated (a015122e4a -> e035417448)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from a015122e4a 42: force: #459: boot: Success after llvm: 225 commits new e035417448 43: force: #460: 6223: Failure after working-10379-ge327b527 [...] 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 1772 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32224 -> 32124 bytes 04-build_kernel_llvm/console.log.xz | Bin 65660 -> 63800 bytes 05-build_abe-qemu/console.log.xz | Bin 32448 -> 32440 bytes 06-build_linux/console.log.xz | Bin 3524 -> 32044 bytes 07-boot_linux/console.log.xz | Bin 5828 -> 0 bytes 08-check_regression/console.log.xz | Bin 2900 -> 3772 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 19 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 477 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 19 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 17 +- 27 files changed, 553 insertions(+), 33 deletions(-) delete mode 100644 07-boot_linux/console.log.xz create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/interesting-commits] branch master updated (cabda4b5 -> 7f0dd3ae)

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 cabda4b5 Add entry 695ce48c63ec582a46bfbda9b066f4d3bcde143f from https [...] new 7f0dd3ae Add entry e327b52766ed497e4779f4e652b9ad237dfda8e6 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_kernel/llvm-master-arm-lts-defconfig}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../e327b52766ed497e4779f4e652b9ad237dfda8e6/tcwg_kernel/status.txt | 5 ++++- 4 files changed, 5 insertions(+), 2 deletions(-) copy llvm/sha1/{e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/llvm-master-a [...] copy llvm/sha1/e327b52766ed497e4779f4e652b9ad237dfda8e6/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e327b52766ed497e4779f4e652b9ad237dfda8e6/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch devel/omp/gcc-12 updated (c7734c6fbb5 -> 7bffe9d3e0c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from c7734c6fbb5 nvptx, libgfortran: Switch out of "minimal" mode adds 58e789b4617 Daily bump. adds 3ae7a822456 Daily bump. adds 6d307fda2b9 Backported from master: adds 6cc80436a93 Daily bump. adds 14207e5481e Daily bump. adds e1357577e6e PR 106101: IBM zSystems: Fix strict_low_part problem new 7bffe9d3e0c Merge branch 'releases/gcc-12' into devel/omp/gcc-12 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/DATESTAMP | 2 +- gcc/config/s390/predicates.md | 12 +++++ gcc/config/s390/s390-protos.h | 1 + gcc/config/s390/s390.cc | 27 ++++++++++- gcc/config/s390/s390.md | 36 +++++++-------- gcc/fortran/ChangeLog | 5 +++ gcc/fortran/trans-array.cc | 1 - gcc/testsuite/ChangeLog | 5 +++ gcc/testsuite/gcc.c-torture/compile/pr106101.c | 62 ++++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr106731.f90 | 58 ++++++++++++++++++++++++ 10 files changed, 185 insertions(+), 24 deletions(-) create mode 100644 gcc/testsuite/gcc.c-torture/compile/pr106101.c create mode 100644 gcc/testsuite/gfortran.dg/pr106731.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (070595ea28 -> ac64fbb0fd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. discards 070595ea28 177: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] discards 94c4eda7dd 176: onsuccess: #600: 6: Success after binutils/gcc/linux/gd [...] discards 43c6ba468e 175: onsuccess: #599: 6: Success after binutils/gcc/linux/gd [...] discards 73d061ec54 174: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] discards 97fc0d6591 173: onsuccess: #597: 6: Success after binutils/gcc/linux/gl [...] discards ec82d41653 172: onsuccess: #596: 6: Success after binutils/gcc/linux/gl [...] discards 533ab5aa5a 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] discards ae9261ee57 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] discards 390baf0260 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] discards da0b0a9eba 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] discards 76f26bd582 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] discards de85979b14 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] discards f0965a90f7 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] discards f88f267990 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] discards 1eb98730fe 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards dfaa4ab880 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 14d6b11a28 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 543b7e6c62 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards 8b6c8a068b 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards 7a73b1cbef 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards 8fcdb67e7e 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 1eb1d37825 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards d71d6176a3 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards 499cfbacc3 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards b1194e7ff4 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards 596be37fce 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards 031d54f76a 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards 3a4c4ad47d 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards 376c279898 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 540ee2102e 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards ad82be9c72 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards ce9ab58030 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards 833dbe8174 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards cef2db207c 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards 4394cb772c 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards e466eb503c 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 7d63fec716 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards 07a5f8fd32 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards de332f64ab 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards f651d8968a 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards 475a7f2058 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards 68e0917097 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards 7b133da78a 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards ee32f45a00 134: onsuccess: #544: 6: Success after binutils: 18 commits discards f0236ff65f 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards bd4aa93f4f 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards b0c336b95c 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards ad1c2a8b9b 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards 1e78a7343b 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards 32d068cb2c 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards 04945b937a 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 0b47e57bc6 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 17f09c973a 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards 523162ac2c 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards ff548920d4 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards 439551d6e3 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards f284ff20ad 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 7a0bf1dd60 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards 9348b07cbc 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards fb8503b242 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards 7ac5812beb 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards 31d56a1c95 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards b1d9c66f2f 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards 1f92805f14 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 87a9d08642 113: onsuccess: #522: 1: Success after gcc: 12 commits discards b1c082d791 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards a096dcadf9 111: force: #520: 6: Success after gcc: 9 commits discards 4400ff63cb 110: onsuccess: #518: 6: Success after binutils: 5 commits discards c07c1c106b 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 7b2ea28aaf 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 5e0aca03d5 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards eb12e4086e 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 069b6ec6e1 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards bf583413d0 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 6af9b2d0e4 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 4021d95998 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 9cf61d13cb 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards 9b3c7b5698 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 3ff31722b6 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards e278248d96 98: force: #504: 6: Success after gcc: 18 commits discards 3714942600 97: onsuccess: #503: 6: Success after linux: 11 commits discards 7a6a2d87a2 96: onsuccess: #502: 6: Success after glibc: 10 commits discards c710f1e44b 95: onsuccess: #500: 6: Success after binutils: 8 commits discards f1ffed4b6c 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards b0b1c5f547 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 3f3a46e576 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards 472f5fefdb 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 3ab3a9a316 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 775fc6c3ed 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards f7dc32af42 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 985b07e19d 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 5e32416dae 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards 4e5a497765 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards 476b3fca18 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards e9726de9ca 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 39858cce28 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards bf7d7c89da 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards c9ce31da20 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 52f78349b8 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards c880910816 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 97a2fcf174 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new 4ad97e96f2 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new 281e565538 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 3e8af41a32 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new da7b4120ca 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 5788c3e2e0 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 53bf6c9873 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 5ebecd7df0 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 62f30c2139 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new f56e6e376b 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new ab38d178ae 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 1c94c9c073 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 9a98059ee3 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new d616947ce7 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new c8ef2f7b16 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 45e8507983 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new ad023e5c32 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new f1d1a3bd5e 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 88a122f1ff 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new c1c1ad6aac 95: onsuccess: #500: 6: Success after binutils: 8 commits new f1c9a75a07 96: onsuccess: #502: 6: Success after glibc: 10 commits new 348fce54dc 97: onsuccess: #503: 6: Success after linux: 11 commits new aa0de6cbb8 98: force: #504: 6: Success after gcc: 18 commits new 6c5c157bca 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 8470f99d50 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 2cbec4ca4d 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 4f7a605797 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new a23c052e72 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 2c052bc3f5 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new da045d8251 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new d116c1ec06 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 06c5f80002 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 2ca494e25c 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 447dfab4c6 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 9c55f7c9e8 110: onsuccess: #518: 6: Success after binutils: 5 commits new 29a575bae1 111: force: #520: 6: Success after gcc: 9 commits new 549c5e93a1 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new 29f2ec9994 113: onsuccess: #522: 1: Success after gcc: 12 commits new 9f2ddc5561 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new be4a081fca 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new 13b2bcda1d 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new 5e094c4fb1 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new 2f0f23cc2d 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new 65cccc7a2e 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new 83ddfc3bd9 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new 8a7f75aded 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 597ec3f445 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new 4a9e0a03db 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new 9bd412a8c8 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 9e2ae70df5 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new 896f7abf37 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 121c5e57d6 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new a5b752fc49 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new 428754bf00 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new 3944009c4b 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new 17038b8f57 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new ab47fb9216 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 711ba1e3dd 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new 94df188cf9 134: onsuccess: #544: 6: Success after binutils: 18 commits new 2f078b8c79 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new 5c0ef4558a 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new b17a85cc7e 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new 623a12dc1f 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new d79abf4fee 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new a8593031f4 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 8addbbc3fa 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new 9b0ec5e720 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 275506e873 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new a03f63dd9d 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new d0486575bd 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new 9bb8b34f3b 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new 46c61b84a1 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new 6680f12a44 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new 6532bfc6ef 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 79ec1af579 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new 4fd4a8ea89 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new 218e5ed3cd 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new 449ce85f96 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 3b9d624d15 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new eb26804651 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new 05f7dfd34c 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new 3ff897f132 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new 9b6b29930d 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new 2f7c48ca0c 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new f4f1151c12 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new f486e3d73b 161: onsuccess: #578: 6: Success after binutils: 15 commits new 414ca3c949 162: onsuccess: #579: 6: Success after gcc: 11 commits new 4f6cd7c8e2 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new 6670b9f9d3 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] new 476cde70da 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] new 071bce79eb 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] new 584b1a6dad 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] new c5dbf423c4 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] new 3d331f0b34 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] new 699f00bbbd 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] new 71f0dc59c9 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] new dde7b9a6d2 172: onsuccess: #596: 6: Success after binutils/gcc/linux/gl [...] new a04af76cea 173: onsuccess: #597: 6: Success after binutils/gcc/linux/gl [...] new 8859759f39 174: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] new 89fb77d4d6 175: onsuccess: #599: 6: Success after binutils/gcc/linux/gd [...] new 1fed764dd2 176: onsuccess: #600: 6: Success after binutils/gcc/linux/gd [...] new 84d018cdde 177: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] new ac64fbb0fd 178: onsuccess: #602: 6: Success after binutils/gcc/linux/gd [...] 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 (070595ea28) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 51692 -> 51812 bytes 05-build_abe-gcc/console.log.xz | Bin 238380 -> 237192 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8452 -> 8672 bytes 08-build_abe-glibc/console.log.xz | Bin 236244 -> 236168 bytes 09-build_abe-gdb/console.log.xz | Bin 50428 -> 50140 bytes 10-check_regression/console.log.xz | Bin 3656 -> 4000 bytes 11-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++--------- 19 files changed, 56 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023