Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (e27aadb1e8c -> 3f3e618421f)

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_gdb/master-arm in repository toolchain/ci/base-artifacts. discards e27aadb1e8c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards b501e1fe4f2 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c60874571d8 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards eca4bd5af01 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e454b1e3e08 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 06b32a2ee59 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 83dbc1faead 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 24601174782 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bd960d697d8 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7e00d539f0f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ab3268bce36 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c15644cc51a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 19f8d229b0f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 3f2d1b294f4 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d7d1ca070b1 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 43f637acd56 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards eca5d866768 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b38a4f0eb75 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c66740cf985 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fcb8e43d007 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards f54b8e69251 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards b598502d351 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 6df3331d662 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 3e2e3cee547 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards ad4dfa4f123 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards d8172b89318 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 6db535e462c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards eb97fd468f5 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 1c5ee70fc14 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 516d844d3e9 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 1d0314e30de 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 81edd316a4c 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards a8f669f64d6 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards f30dd3101df 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards c713600e88a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards fab320fd2c1 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 85cf39b1e8b 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 0a26666bf17 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 422a37d0e07 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7c34444dcc9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards e7072affca9 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards ce16eb26885 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 2acc962fad1 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards bacace96583 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 0a8d0318e68 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards fa735bd9d12 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 60e7471807c 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards c75cb71b621 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 63e218d01ba 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 3fe0475958f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 01b6c2127b8 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 0af4c3fab1b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards d6b7d6cff62 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ced2a4ea7c2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 3467d7bf2ae 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8bd7446c4b7 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d03ba0dea76 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 25d96ed1909 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards b4ca68855cb 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 87b5d59b046 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards ac832597911 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5764d603efe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards d63d6bcf80c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 981152c84df 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 4e54a6f98d7 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards ff322691b57 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards d38af193d76 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 8dbd74aca79 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 592290e7340 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards ff549f546f7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 30c5b92e115 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 78ba52b3670 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 71d1e96bcbd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards f50bb18e367 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 48b8848a570 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards dd6d4b199a3 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 13a30c42c1c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 3360ee4b06d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 66f3758b7fd 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 1b7fb2bca99 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 8ce025a6460 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 164e19b9c47 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 268bc041d83 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards d601d2755b1 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b7e9a3f30bb 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 296552bf784 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 64a49412128 125: onsuccess: #614: 1: Success after linux: 12 commits discards bb524ca79ef 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 82f8f861cfc 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 6e0e6608b94 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 544b455fd5e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards a90eed535cf 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards b4465b90eac 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards f568c71b395 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards b2eeadce232 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards c3e89a6c412 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0b5004b16c7 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 07433011600 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 71ccd5d97d5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 1aad1c6ed29 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 81ae32652ae 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 86718c7c81b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 3de94cbbe73 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new d6a1c8c2eb0 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 2b69c8a4ff1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 6e5628faf95 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new cb9012d3ce3 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new b775f7bebe5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 36989457128 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 4c345492d37 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 362095951f9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 50520d08ed4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 04b4eb34bc1 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 2ec9e63e0cb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new bc7241e12a5 124: onsuccess: #612: 1: Success after binutils: 18 commits new 11f664acf87 125: onsuccess: #614: 1: Success after linux: 12 commits new e4276f24cbe 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 76d602248d3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 39fb1ba27de 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new dd6f401e943 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new a66cb6f5f17 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 0a86091fe36 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 60b80417284 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new b5d673e9283 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new c13aa8c4850 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 30052c5e450 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new f6af779a06e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new edc5ea91c0f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 28c8507f050 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new e049ed6f2de 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new bb8d211a465 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 4b3a9d6a78d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 323cf72d116 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 7d9388ccda9 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 9d00eec9dc2 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new ae3500a9799 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 7bf955523d6 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new b008e2acdf3 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 5d066f9b194 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4c653d9b665 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 2b9ad1e6c64 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9fe19be7d72 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new d3d114d5370 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 39e0837eb4c 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b4050b1cff0 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new b15baf0f1d8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new afbf343bf88 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 002e5f6da7b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new aa50b389acb 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new b515fa0ef23 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 3a89da45f25 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 025f9d5c8a2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 049bdebaea8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 50e9c4fae57 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 2fbcf8ce413 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 9acb487c76f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new f786d33352b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4c115ffc0e7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 7920d61bd72 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c51b332f020 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new fb3857e859f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 206d1d1f0c7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new d3d566c70d9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 2748d9befba 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 6caab166679 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new f5fad975d7d 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 591cf91d670 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a469757b724 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new a6d2e7da3f1 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 105edc34498 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new f8cf8f8bdde 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 8ae7e1bd613 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 9f3275a0951 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 2425c1d3949 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 27b1cdb8dee 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 2db0aa2f90c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 3dcdfa77a50 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new e4a5dbc7ff4 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new beabba48ea7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 0ecae54e53d 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new f4688a1c0ce 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 3c8cff479bf 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new a68d53bb77e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 5224a4a8ed1 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4be37f278e6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6521d1cbd35 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d1b8bd70805 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 52d529c6bb3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 88c2b1dd704 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 5fb219eca55 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new ba0cd1577a3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a03187fa5f1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new fa735011e21 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new cdaa087258b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1e1d6b1259b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 9b3a6924392 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ca7f695c5cc 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 3fd27b061dc 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 108b33b93d9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 621bc209147 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0d0957742da 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new c0e6bc41486 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3f3e618421f 212: force: #27: : Failure after baseline build: no new commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e27aadb1e8c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 1808 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 3444 bytes 03-build_abe-binutils/console.log.xz | Bin 52656 -> 52668 bytes 04-build_abe-gcc/console.log.xz | Bin 238028 -> 236000 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9080 -> 9236 bytes 07-build_abe-glibc/console.log.xz | Bin 235084 -> 235808 bytes 08-build_abe-gdb/console.log.xz | Bin 50268 -> 50308 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2016 -> 1052 bytes 11-check_regression/console.log.xz | Bin 7716 -> 2504 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 19 - 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 97 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 56 - 11-check_regression/results.compare2 | 202 - 11-check_regression/results.regressions | 58 +- 12-update_baseline/console.log | 72 +- dashboard/dashboard-generate.sh | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 97 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- results | 62 +- sumfiles/gdb.log.xz | Bin 2948932 -> 0 bytes sumfiles/gdb.sum | 99732 ------------------------------ 28 files changed, 96 insertions(+), 100337 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.compare delete mode 100644 11-check_regression/results.compare2 delete mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz_LTO updated (56f93ff3bdb -> 9112300a797)

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-aarch64-master-Oz_LTO in repository toolchain/ci/base-artifacts. from 56f93ff3bdb 57: onsuccess: #8: 1: [TCWG CI] No change after llvm: 197 commits new 9112300a797 58: onsuccess: #9: 1: [TCWG CI] No change after llvm: 462 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1964 -> 1768 bytes 02-build_bmk_llvm/console.log.xz | Bin 99564 -> 99268 bytes 03-benchmark/benchmark-build.log | 110 +- 03-benchmark/benchmark.log | 108 +- 03-benchmark/console.log.xz | Bin 3876 -> 3856 bytes .../compare-results-vs-first-internal.csv | 42 +- .../compare-results-vs-prev-internal.csv | 42 +- 04-check_regression/console.log.xz | Bin 5988 -> 6716 bytes .../csv-results-vs-first-1/perf.csv | 80 +- .../csv-results-vs-first-1/results.csv | 14649 +++++++------- .../csv-results-vs-first-1/size.csv | 14595 +++++++------- 04-check_regression/csv-results-vs-prev-0/perf.csv | 93 +- .../csv-results-vs-prev-0/results.csv | 4466 +++-- 04-check_regression/csv-results-vs-prev-0/size.csv | 19187 +++++++++---------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 18 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 80 +- .../csv-results-vs-prev-1/results.csv | 14649 +++++++------- 04-check_regression/csv-results-vs-prev-1/size.csv | 14595 +++++++------- 04-check_regression/results-vs-first-brief.csv | 41 +- 04-check_regression/results-vs-first-full.csv | 84 +- 04-check_regression/results-vs-first-internal.csv | 43 +- 04-check_regression/results-vs-first.csv | 43 +- 04-check_regression/results-vs-first.log | 624 +- 04-check_regression/results-vs-prev-brief.csv | 41 +- 04-check_regression/results-vs-prev-compare.csv | 1 + 04-check_regression/results-vs-prev-full.csv | 86 +- 04-check_regression/results-vs-prev-internal.csv | 43 +- 04-check_regression/results-vs-prev.csv | 43 +- 04-check_regression/results-vs-prev.log | 796 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 229 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 72 files changed, 42551 insertions(+), 42593 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (778271b31d6 -> ada0739fa87)

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 778271b31d6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards e4f7e5b92ed 213: force: #24: 1: Success after binutils: 2 commits discards 002aaa7883b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 0cd82e1e28a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c3d186fa24d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a29fbbee12d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9b010554ede 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6ae7d7de9e3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6d0d9cecad5 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c596744c17f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1ba8acec937 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 63cde9b65f4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d86a83dbfa3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2225bd9f11d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2777b0f279b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b8e82b6acbc 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ba9b1dfb9d0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0e929be06fd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 66c36ec06c9 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards a732b1c06b0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 73dfcfd4a6b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6193fca6b56 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c09621d0ba6 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 70e01510e7f 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d890f15d433 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards adb7bc862d5 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards fe84f13b1b3 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 2b6d23080bd 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards abfba539815 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 12134530046 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 582d99699e8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 58b4c3f8a35 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 5b683149c76 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 4267c058191 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 28f418fdd05 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 5aa709b385b 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 22f3ce00f43 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 431a897acfb 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 73e224ea8ce 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 004bc1d231a 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 5020ffa2b49 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards e69dd016b74 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 57d2c601249 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 9563a61371e 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 9d0006c05cc 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 72bc8ded71c 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards bb18e74b35d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 71d8b0782ee 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards c7ca67689d1 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 75606f029e9 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards e1463f3128d 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 62ad635d5f4 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2d375995102 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 4be0f164b5d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 6d58951f2e8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards b6501400aa3 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards e5728e48c8f 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 308df71f345 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 9438d301744 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards fd51c764f26 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 1471d58efc4 154: onsuccess: #583: 1: Success after linux: 10 commits discards 550528b0a5a 153: onsuccess: #582: 1: Success after glibc: 9 commits discards d95088bbf77 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f3b66865b0c 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 4e1afe0ec25 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 395cf70564b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 94bfc2d4f23 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 39e261533e0 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 500a97689a6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 16e0d7bcb35 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 30676abf8fa 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 47e82051645 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 2740fa07580 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards fc72cb3c111 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards bf4611290d0 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 98b13fb792f 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 82f4222a1ad 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards a443f22dce0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 353794cdce8 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 6578acdebe4 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 2a0d6082df1 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 51302d545e7 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards ae07401239c 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards f77f68cf175 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 37cf70e584d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 1234727f521 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 128369d528a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 5e7d56d5537 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards a7cb2435edd 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 2952fcdff02 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 961b78401fb 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 004388649d1 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards c321dd2c0c8 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards f2c342218ea 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 904793d7a9f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards f7ddb602295 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards c4badeaf942 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards f1eb43393cd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards a92792c063b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 4ee8720d752 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards ea342ddd214 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 9ef2967744e 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new f0b27a61235 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new b69d337474b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 22ec2f9f77a 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 83c9f9bc2dd 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 7abc67d593b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 03d76f3dfd9 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new f8146583d82 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 04cde5c1ec2 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new f74b520db6d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new aca9b78895e 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 4f2fe64acd2 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 0fc52fc9255 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 5e09d813d6b 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 91b6d23e16e 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 7bfa42f7bcf 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new d8d5ca9fc57 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 74fb4c7653a 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 0972d8f5e3a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new e6b9ccf34e6 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new a02dc39def2 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 7fc51ec040c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 58274a2596a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new b915d0c2c41 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 491663f67ce 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 0ba57ba8788 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 0b91e7c02d4 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 2191bdf144e 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 56471ee1688 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new e8e879272a6 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new d84407029d2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new df6d931941d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 8714612ccd6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new aca15795230 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new f02845ca41d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 7e038ecd2db 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 851c838b42d 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 5f75e912d1d 151: onsuccess: #579: 1: Success after binutils: 21 commits new 5a96e00948b 152: onsuccess: #580: 1: Success after gcc: 6 commits new 3df84144984 153: onsuccess: #582: 1: Success after glibc: 9 commits new 5b72e15bb6c 154: onsuccess: #583: 1: Success after linux: 10 commits new 137cfc14ca7 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new a5915d53343 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 1d3f145305c 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 3c421570302 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new cc709a6ec16 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 46a35d241ef 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 247dcd804ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2da0fc1bc95 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new afd793b198d 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new ccb14ec937b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 6903e8637b0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 6aa31190835 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new b96775bda8b 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 1de5b175f8f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 917ac0027e0 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new e1ced45e800 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 68b31d131db 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new b3e4f747dea 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 3d5b48a2be1 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 351a0808805 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 634e12ea426 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 4e9e2279e2c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 25f000d1296 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new d0d615866a4 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new b416c9d6485 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8fd78f1ce20 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d0c3c842179 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 6d05f31d4f7 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 6cd1e316041 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 20876accdcb 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 83f40fd5d56 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 31476480638 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e64a6612659 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 0079c36e9de 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 4a700141c83 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new f65075f8223 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 7426109c658 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 0f23256a651 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 78d6f11131d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 294629f7ed0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 73e5cd1f597 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a3615c56f5d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c4f785dec81 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c6a5d4ad501 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a183514316d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 6bb2022d469 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ed1ebe6a7fa 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 9c9b7800dcd 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 528fc877fd7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e66c4826668 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b283c83f75d 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 545578df10e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 37cc33591e8 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 7ae74c59eee 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new e1e0b01587a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new d61ab31e85f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b8462ed2579 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 69c01450d84 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 102cd60dc5c 213: force: #24: 1: Success after binutils: 2 commits new 107675619f7 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new ada0739fa87 215: onsuccess: #26: 1: Success after binutils: 10 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (778271b31d6) \ 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 1716 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 3480 -> 3432 bytes 03-build_abe-binutils/console.log.xz | Bin 54008 -> 53440 bytes 04-build_abe-gcc/console.log.xz | Bin 235796 -> 237816 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 235944 -> 235916 bytes 08-build_abe-gdb/console.log.xz | Bin 51628 -> 50624 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3764 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2604 -> 2520 bytes 11-check_regression/console.log.xz | Bin 4176 -> 3584 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 36 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 20 +- 11-check_regression/results.compare2 | 45 +- 11-check_regression/results.regressions | 19 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1085 ---------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 19 - sumfiles/binutils.log.xz | Bin 62716 -> 62612 bytes sumfiles/binutils.sum | 62 +- sumfiles/gas.log.xz | Bin 100580 -> 100572 bytes sumfiles/gas.sum | 274 +++---- sumfiles/ld.log.xz | Bin 132412 -> 132192 bytes sumfiles/ld.sum | 344 ++++----- 40 files changed, 473 insertions(+), 1581 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 delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (f1fe2ebd710 -> 3947a30d871)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards f1fe2ebd710 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] discards 71bec02d113 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] discards 19c8fc199f1 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards d53c54211ce 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 6c48d2ec2c8 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 9fd7cd55176 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards 2628dfe574a 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 54bf9ae38b2 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 00bb64d57d0 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards cfee629a8e1 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 78e8dbad8de 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1933376e38f 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards e9719c608e4 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 8bc1f7c00ba 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8cd06edff28 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards dc4d1956b5e 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards 272953d3102 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 838eedeaf69 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards e7081da93cb 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 2bcc5881e48 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards c94d0a02452 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards b352514271b 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 1c7e1add489 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards 0c82b4129c2 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards a701f10ac0e 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards c0b7ea6b3b0 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards be4fecdc5d8 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 8194d53f7a6 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards bcc74724da6 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards d6b0d601adb 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards a57646fa8d7 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards fd45771e634 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 98da98e6188 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 2d8e29a6c5f 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 8f0ed69bd11 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 84409d377f8 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards b8589346d5b 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 38999b48814 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards 0f6cf442a66 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 775c335ff75 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards d300f9857ed 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards d2fb4398846 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards cdbbffbcf71 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards 690ebc91997 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards 8d30ba59d48 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 2feef7cc393 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards f88fc94505b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards 639dfe955ce 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards f3136cf3b9d 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards d5d82ce65b1 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards cedd4bfa2ca 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards d7fc3e4cd05 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards 7e1c1647843 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 3a65fa5f781 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards c48f5939491 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards f861690645b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards 5e06cf9c0e3 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards 9af367ffae4 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards 6458e36f60e 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards aeb30ba3809 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 0cf3b662178 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards 545c67b0cb1 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 9232db1bd39 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards 7379ce8bc17 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards ae447cd444d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards 349f564c664 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards ddc3402844a 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 70d85542a8b 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards b4e5ac279d6 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards ca997e36119 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards 9ca616bbbef 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards aa0a4882c55 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards e05f0548eb7 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards 501511bc67b 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 79bb977da29 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards bce52d9b185 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards da9e6ffa39e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards e7faf342192 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 74648c3d5d6 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 8bfd62873ba 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards bece04c6d01 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 7373a9ff313 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards cbeb9a8c0eb 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 2ba298d24af 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards 9e3a07dd32c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards c1375dc02b6 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 99befab171f 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 619b301f2ff 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards 7fa4321cb79 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards f627a4eb9fd 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards 68766d0ad73 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] discards f7d9aec603d 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 4e1edd9872b 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] discards caade09daa5 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] discards bad41064b97 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards a3c3a899fe4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] discards e43a5ce7132 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] discards 66448228eec 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] discards 52d9dff1ed9 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] discards 1d864ad169b 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] discards e9d6f7ad3c9 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new d013e7a7d84 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new 45ddc9cb52b 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] new 349ee529a83 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] new d8add8eabf9 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] new 32609e2182d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] new ac0b59e152c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] new 83fdaeb8b64 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 3993dcf9e2f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] new d83d611e115 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new 36d69ebd8ed 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new acdc9d944f0 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new 9b7742e1612 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new c5c2ea4bbca 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new 414e149ae6f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new 17c88f400a3 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c428d3060b2 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new c4e9ffd3131 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new 4fbe149462b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new d3b4d949db6 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 45eebcd5174 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new 4093f80f40f 384: onsuccess: #2205: 1: Success after gcc: 2 commits new e5661ba76ff 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new bc570f37aea 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 14b6c4b1f2e 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 3e37b4311bf 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new 3752e53caec 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 2170624c7ed 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new c0ccfe9b8c6 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new a22d8460496 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new e1cc6006bcd 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new a70ee95df6f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new bdd7fa7ca55 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new 3cea1afd6c0 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new f76130bd7ed 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new 509ea060350 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new d02f625dd5c 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new d17c4c6af90 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new f760f3f0f78 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new 2390a9eb743 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new a896bc1473b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new d54e164dccc 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new 4b540753fb7 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new ce94a86a318 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new b5803d76da4 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new ac5cd45601f 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 451e5d9e4b7 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new eef2056205d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new 213c8842efa 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 43fb810f2a6 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new 3f106318d51 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new b13a192cddb 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new 3bd58639e6f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new 952484c6ba8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new fc03cdb9441 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new edc57d36a22 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new 947feb8f2a9 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new f8c5d32236d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new aae9f9137bd 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new 2d55e7a36df 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 53dc9213447 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 736508b4b9a 424: onsuccess: #2248: 1: Success after gcc: 6 commits new b16c3acfb6d 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new 34c00aad3f4 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new fde1869c3ab 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 245bfdfd465 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 3ba766e0857 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 9f4b3a09a00 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new ac20b20c6b0 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new 2cc62a1f356 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new f265fc09de4 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new af2558073d1 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new d14ae31f526 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new f0e26db3cdd 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 8f5793f90c2 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new 1ac519dd601 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new 85929d437c5 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new df8b3c265a3 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new 89e95c544a5 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new 728f65a0034 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new c6120311104 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new c41eac3b31c 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new baf1b993bd2 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new a6dc938e736 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 6622e98990f 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f25f9ca7ce1 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e746f903f97 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 106a9a9f295 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 7cffc3262c3 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4a7cda7a091 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new f4838449a58 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new d0a9f801d63 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new efa3031c75c 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new a1a587ca6b8 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 931e77a625a 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e947cc070e0 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 72c393aacc2 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new 41f5281fb85 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new b116961331e 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new f541da58b05 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new 7dc5cadf830 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] new 4bfde90a5e6 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] new 3947a30d871 465: onsuccess: #26: 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 (f1fe2ebd710) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1808 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 3496 bytes 03-build_abe-binutils/console.log.xz | Bin 30660 -> 31080 bytes 04-build_abe-stage1/console.log.xz | Bin 89220 -> 89832 bytes 06-build_abe-linux/console.log.xz | Bin 9068 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 236472 -> 236356 bytes 08-build_abe-stage2/console.log.xz | Bin 225252 -> 225616 bytes 09-build_abe-gdb/console.log.xz | Bin 38080 -> 38908 bytes 10-build_abe-qemu/console.log.xz | Bin 30700 -> 30592 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 7032 bytes 13-check_regression/console.log.xz | Bin 8056 -> 6916 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 13 + 13-check_regression/mail-body.txt | 33 + 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 291 +- 13-check_regression/results.regressions | 33 + 14-update_baseline/console.log | 44 +- 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 | 35 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 33 + sumfiles/g++.log.sep.xz | Bin 0 -> 105984 bytes sumfiles/g++.log.xz | Bin 2659072 -> 2661440 bytes sumfiles/g++.sum | 59 +- sumfiles/g++.sum.sep | 11513 ++++++++++++++++++++++++++++++ sumfiles/gcc.log.sep.xz | Bin 0 -> 128976 bytes sumfiles/gcc.log.xz | Bin 2234264 -> 2237668 bytes sumfiles/gcc.sum | 96 +- sumfiles/gcc.sum.sep | 1162 +++ sumfiles/gfortran.log.sep.xz | Bin 0 -> 30144 bytes sumfiles/gfortran.log.xz | Bin 896048 -> 900008 bytes sumfiles/gfortran.sum | 8 +- sumfiles/gfortran.sum.sep | 1852 +++++ sumfiles/libatomic.log.xz | Bin 2280 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217252 -> 217228 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 0 -> 14228 bytes sumfiles/libstdc++.log.xz | Bin 442188 -> 446452 bytes sumfiles/libstdc++.sum | 8 +- sumfiles/libstdc++.sum.sep | 396 + 51 files changed, 15445 insertions(+), 228 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions create mode 100644 sumfiles/g++.log.sep.xz create mode 100644 sumfiles/g++.sum.sep create mode 100644 sumfiles/gcc.log.sep.xz create mode 100644 sumfiles/gcc.sum.sep create mode 100644 sumfiles/gfortran.log.sep.xz create mode 100644 sumfiles/gfortran.sum.sep create mode 100644 sumfiles/libstdc++.log.sep.xz create mode 100644 sumfiles/libstdc++.sum.sep -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (af4f6816660 -> 0a07bfad125)

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 af4f6816660 Move target independent documentation files into subdir new adb70c2d106 Avoid random stmt order result in pass_waccess::use_after_inval_p new 0a07bfad125 tree-optimization/109123 - run -Wuse-afer-free only early The 2 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/gimple-ssa-warn-access.cc | 65 +++++++++++-------------- gcc/testsuite/c-c++-common/Wuse-after-free-6.c | 2 +- gcc/testsuite/gcc.dg/Wuse-after-free-2.c | 8 +-- gcc/testsuite/gcc.dg/Wuse-after-free-pr109123.c | 41 ++++++++++++++++ gcc/tree-dfa.cc | 48 ++++++++---------- gcc/tree-dfa.h | 1 + 6 files changed, 97 insertions(+), 68 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/Wuse-after-free-pr109123.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-Os updated (a0995a72ea3 -> 13f5b172760)

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/gnu-aarch64-master-Os in repository toolchain/ci/base-artifacts. from a0995a72ea3 75: onsuccess: #11: 1: [TCWG CI] No change after binutils/g [...] new 13f5b172760 76: onsuccess: #12: 1: [TCWG CI] No change after binutils/g [...] 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 -> 1908 bytes 02-prepare_abe/console.log.xz | Bin 2852 -> 3528 bytes 03-build_abe-binutils/console.log.xz | Bin 31424 -> 31820 bytes 04-build_abe-stage1/console.log.xz | Bin 73000 -> 72664 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 245544 -> 246052 bytes 08-build_abe-stage2/console.log.xz | Bin 179320 -> 180516 bytes 09-benchmark/benchmark-build.log | 96 +- 09-benchmark/benchmark.log | 94 +- 09-benchmark/console.log.xz | Bin 4008 -> 3944 bytes .../compare-results-vs-first-internal.csv | 221 +- .../compare-results-vs-prev-internal.csv | 231 +- 10-check_regression/console.log.xz | Bin 13760 -> 15512 bytes .../csv-results-vs-first-1/md5sum.csv | 1695 +-- .../csv-results-vs-first-1/perf.csv | 2607 ++--- .../csv-results-vs-first-1/results.csv | 3211 +++--- .../csv-results-vs-first-1/size.csv | 38 +- .../csv-results-vs-prev-0/md5sum.csv | 1722 ++-- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2622 +++-- .../csv-results-vs-prev-0/results.csv | 10239 ++++++------------- 10-check_regression/csv-results-vs-prev-0/size.csv | 7109 +++---------- .../csv-results-vs-prev-1/md5sum.csv | 1695 +-- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2607 ++--- .../csv-results-vs-prev-1/results.csv | 3211 +++--- 10-check_regression/csv-results-vs-prev-1/size.csv | 38 +- .../output-bmk-results/error_code-1 | 0 .../output-bmk-results/exe.regression | 1 + .../output-bmk-results/exe.regression.diff | 1 + .../output-bmk-results/symbol.regression | 4 + .../output-bmk-results/symbol.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 2641 ++--- 10-check_regression/results-vs-first-internal.csv | 227 +- 10-check_regression/results-vs-first.csv | 227 +- 10-check_regression/results-vs-first.log | 1108 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 21 +- 10-check_regression/results-vs-prev-full.csv | 2893 +++--- 10-check_regression/results-vs-prev-internal.csv | 231 +- 10-check_regression/results-vs-prev.csv | 231 +- 10-check_regression/results-vs-prev.log | 1120 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../434.zeusmp/results-metadata.json | 16 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 16 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 45 +- mail/mail-body.txt | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 93 files changed, 19336 insertions(+), 27706 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/error_code-1 create mode 100644 10-check_regression/output-bmk-results/exe.regression create mode 100644 10-check_regression/output-bmk-results/symbol.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (1c60231cba7 -> 778271b31d6)

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 1c60231cba7 213: force: #24: 1: Success after binutils: 2 commits discards ce0915780b1 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 829a1ad714a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 3c774a45276 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9d4297cbd4b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9fdb5af572e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f89081a832b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 30f54119510 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 2bd2f54619a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards be1da56c667 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b2cf729781a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 43f43cbbd8c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 43445161685 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f2ea457fa3d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 41017edf370 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 86475f0715b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards de4c7a24815 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 103cd9f39df 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 72ef2d065e0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 668984a803d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards b090748e5fa 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 59aef198d7c 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 556d5ff6377 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 54631dfd82b 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 7a7366b5ca0 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 4fb640db543 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards ecf970bb80c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 06db2aa8a05 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ea1e80e2085 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards eedab659d51 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6660bfe9597 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 68cd9ae5641 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 8caf9aadb79 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 82199722aaf 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 5b9ecdfbfb4 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 7e9f1265c05 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards bc396fbf7e7 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5c37a259756 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 530d2fefee9 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 7146d1b147e 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4948a62836c 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 9c00a31a50a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 29664a9cd55 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards dd84a694a8e 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 842de85df1e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 981c3ce6f4a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f119b31eaa6 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 82277251756 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 3f24fed0aa0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 973582ae8c1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 5b249d7b0f3 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards dc92098b11f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards fa1c1e13cdf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 39d0a5f354f 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0bcde9bef5c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 75b9abb2a0e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 6293bc36ecc 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards ae879913a68 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 9864bf4ddaa 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards e561fe471fa 154: onsuccess: #583: 1: Success after linux: 10 commits discards bc4fb832b26 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 3465f4f1efc 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 824a37cdde6 151: onsuccess: #579: 1: Success after binutils: 21 commits discards cdd239c2758 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 36bf3d07048 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 4fdeb620ce6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 309d79396ce 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 0df7f27e42f 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards f5623edff3d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 90ff893db34 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 736a0c6a347 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 477469588bf 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 22cd64ba22c 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 84531b51c58 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards d8b987f265c 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 0c7622ce489 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards a1bb92b4b7e 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 006298c86ac 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 0ab9cddb219 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards b0ebc669ecc 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 0243dcaa98f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 77d1d168424 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards e95df942bc4 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards d2c057dff0b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 55f291dfdf8 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards e0bb0abdf06 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 16a23d4c386 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 5344a87c34d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 9f5cc4edc2f 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards c0f4e2e8b56 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards fa1474f204d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 1c410ac3c33 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 101442b6358 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 7620d4a1e37 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 570ed5ac484 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 244da427af4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 9df08219cb4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 59ba16ed939 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 456e3c5858e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 31dbe5e92a2 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards a60a59c2e4b 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 489c1f87253 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new ea342ddd214 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 4ee8720d752 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new a92792c063b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new f1eb43393cd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new c4badeaf942 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new f7ddb602295 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 904793d7a9f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new f2c342218ea 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new c321dd2c0c8 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 004388649d1 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 961b78401fb 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2952fcdff02 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new a7cb2435edd 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 5e7d56d5537 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 128369d528a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 1234727f521 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 37cf70e584d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new f77f68cf175 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new ae07401239c 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 51302d545e7 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 2a0d6082df1 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 6578acdebe4 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 353794cdce8 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new a443f22dce0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 82f4222a1ad 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 98b13fb792f 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new bf4611290d0 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new fc72cb3c111 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 2740fa07580 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 47e82051645 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 30676abf8fa 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 16e0d7bcb35 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 500a97689a6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 39e261533e0 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 94bfc2d4f23 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 395cf70564b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 4e1afe0ec25 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new f3b66865b0c 151: onsuccess: #579: 1: Success after binutils: 21 commits new d95088bbf77 152: onsuccess: #580: 1: Success after gcc: 6 commits new 550528b0a5a 153: onsuccess: #582: 1: Success after glibc: 9 commits new 1471d58efc4 154: onsuccess: #583: 1: Success after linux: 10 commits new fd51c764f26 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 9438d301744 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 308df71f345 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new e5728e48c8f 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new b6501400aa3 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 6d58951f2e8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 4be0f164b5d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2d375995102 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 62ad635d5f4 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new e1463f3128d 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 75606f029e9 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new c7ca67689d1 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 71d8b0782ee 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new bb18e74b35d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 72bc8ded71c 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 9d0006c05cc 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 9563a61371e 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 57d2c601249 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new e69dd016b74 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 5020ffa2b49 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 004bc1d231a 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 73e224ea8ce 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 431a897acfb 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 22f3ce00f43 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5aa709b385b 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 28f418fdd05 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 4267c058191 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 5b683149c76 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 58b4c3f8a35 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 582d99699e8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 12134530046 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new abfba539815 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 2b6d23080bd 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new fe84f13b1b3 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new adb7bc862d5 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new d890f15d433 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 70e01510e7f 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new c09621d0ba6 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 6193fca6b56 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 73dfcfd4a6b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new a732b1c06b0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 66c36ec06c9 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 0e929be06fd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ba9b1dfb9d0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new b8e82b6acbc 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2777b0f279b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2225bd9f11d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d86a83dbfa3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 63cde9b65f4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1ba8acec937 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c596744c17f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6d0d9cecad5 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 6ae7d7de9e3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9b010554ede 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a29fbbee12d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c3d186fa24d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 0cd82e1e28a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 002aaa7883b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new e4f7e5b92ed 213: force: #24: 1: Success after binutils: 2 commits new 778271b31d6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1c60231cba7) \ 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 1944 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 3440 -> 3480 bytes 03-build_abe-binutils/console.log.xz | Bin 52632 -> 54008 bytes 04-build_abe-gcc/console.log.xz | Bin 236672 -> 235796 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 235404 -> 235944 bytes 08-build_abe-gdb/console.log.xz | Bin 50456 -> 51628 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2196 -> 2604 bytes 11-check_regression/console.log.xz | Bin 3156 -> 4176 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 21 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 14 +- 11-check_regression/results.regressions | 19 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1085 ++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 21 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 19 + sumfiles/binutils.log.xz | Bin 62720 -> 62716 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100656 -> 100580 bytes sumfiles/gas.sum | 2 +- sumfiles/ld.log.xz | Bin 132024 -> 132412 bytes sumfiles/ld.sum | 5 +- 38 files changed, 1236 insertions(+), 44 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-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, 8 months

[toolchain/ci/interesting-commits] branch master updated (9a00673f -> cd7a377b)

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 9a00673f Add entry 775451b66a4c726f1c3925f74be8cefcb308e4f8 from https [...] new cd7a377b Add entry 2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b 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: binutils/gdb-13-branchpoint-1445-g2d5783fad77 | 1 + .../tcwg_gnu_native_check_binutils/master-arm/build_url | 1 + .../tcwg_gnu_native_check_binutils/master-arm/last_good | 1 + .../tcwg_gnu_native_check_binutils/master-arm/summary.txt | 1 + .../tcwg_gnu_native_check_binutils/status.txt | 12 ++++++++++++ 5 files changed, 16 insertions(+) create mode 120000 binutils/gdb-13-branchpoint-1445-g2d5783fad77 create mode 100644 binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu [...] create mode 100644 binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu [...] create mode 100644 binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu [...] create mode 100644 binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-12 updated (29deac4ca7e -> cd425a35ec2)

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-12 in repository gcc. from 29deac4ca7e Daily bump. new cd425a35ec2 testsuite/108985 - missing vect_simd_clones target requirem [...] 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/testsuite/gcc.dg/vect/pr108950.c | 1 + 1 file changed, 1 insertion(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O3_LTO updated (3facfb695cf -> 758a5330661)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 3facfb695cf 9: onsuccess: #11: 1: [TCWG CI] No change after binutils/gc [...] new 758a5330661 10: onsuccess: #12: 1: [TCWG CI] No change after binutils/g [...] 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 1784 -> 1936 bytes 02-prepare_abe/console.log.xz | Bin 2856 -> 3544 bytes 03-build_abe-binutils/console.log.xz | Bin 30872 -> 31716 bytes 04-build_abe-stage1/console.log.xz | Bin 90428 -> 91240 bytes 06-build_abe-linux/console.log.xz | Bin 7924 -> 7900 bytes 07-build_abe-glibc/console.log.xz | Bin 237220 -> 237084 bytes 08-build_abe-stage2/console.log.xz | Bin 211484 -> 212016 bytes 09-benchmark/benchmark-build.log | 148 +- 09-benchmark/benchmark.log | 146 +- 09-benchmark/console.log.xz | Bin 4180 -> 4132 bytes .../compare-results-vs-first-internal.csv | 66 +- .../compare-results-vs-prev-internal.csv | 66 +- 10-check_regression/console.log.xz | Bin 7644 -> 8936 bytes .../csv-results-vs-first-0/results.csv | 4522 +- .../csv-results-vs-first-0/size.csv | 363340 +++++----- 10-check_regression/csv-results-vs-first-0/sve.csv | 25862 +- .../csv-results-vs-first-0/vect.csv | 284 +- .../csv-results-vs-first-1/perf.csv | 162 +- .../csv-results-vs-first-1/results.csv | 250972 ++++--- .../csv-results-vs-first-1/size.csv | 626938 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 26790 +- .../csv-results-vs-first-1/vect.csv | 933 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 160 +- .../csv-results-vs-prev-0/results.csv | 237406 +++---- 10-check_regression/csv-results-vs-prev-0/size.csv | 495342 +++++++------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 51144 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 1270 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 162 +- .../csv-results-vs-prev-1/results.csv | 250972 ++++--- 10-check_regression/csv-results-vs-prev-1/size.csv | 626938 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 26790 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 933 +- .../output-bmk-results/error_code-1 | 0 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 166 +- 10-check_regression/results-vs-first-internal.csv | 66 +- 10-check_regression/results-vs-first.csv | 66 +- 10-check_regression/results-vs-first.log | 968 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-full.csv | 178 +- 10-check_regression/results-vs-prev-internal.csv | 66 +- 10-check_regression/results-vs-prev.csv | 66 +- 10-check_regression/results-vs-prev.log | 1174 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../508.namd_r/results-metadata.json | 16 +- .../510.parest_r/results-metadata.json | 16 +- .../511.povray_r/results-metadata.json | 16 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../523.xalancbmk_r/results-metadata.json | 16 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../526.blender_r/results-metadata.json | 16 +- .../527.cam4_r/results-metadata.json | 16 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../538.imagick_r/results-metadata.json | 16 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../548.exchange2_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 45 +- mail/mail-body.txt | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 85 files changed, 1471038 insertions(+), 1523806 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/error_code-1 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023