Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-aarch64 updated (c7c6ed8d634 -> 7b73d045fba)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from c7c6ed8d634 0: init: #1: 1: Success after baseline build: no new commits new 7b73d045fba 1: onsuccess: #5: 1: [TCWG CI] Success after binutils/gcc/l [...] 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 2260 -> 2256 bytes 01-reset_artifacts/patch-env.sh | 2 -- 02-prepare_abe/console.log.xz | Bin 2544 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27696 -> 27164 bytes 04-build_abe-stage1/console.log.xz | Bin 73092 -> 71032 bytes 06-build_abe-linux/console.log.xz | Bin 9028 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 243528 -> 240820 bytes 08-build_abe-stage2/console.log.xz | Bin 202840 -> 201268 bytes 09-build_abe-gdb/console.log.xz | Bin 34668 -> 34808 bytes 10-build_abe-qemu/console.log.xz | Bin 32524 -> 31144 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3836 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2168 bytes 13-check_regression/console.log.xz | Bin 2532 -> 5728 bytes 13-check_regression/mail-body.txt | 25 --------------- 13-check_regression/mail-subject.txt | 1 - 13-check_regression/results.compare | 11 +++++++ 13-check_regression/results.compare2 | 47 ++++++++++++++++++++++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 38 +++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 25 --------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 48 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 62288 -> 62524 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83968 -> 83956 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 107512 -> 107536 bytes sumfiles/ld.sum | 4 +-- 36 files changed, 134 insertions(+), 90 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh delete mode 100644 13-check_regression/mail-body.txt delete mode 100644 13-check_regression/mail-subject.txt create mode 100644 13-check_regression/results.compare create mode 100644 13-check_regression/results.compare2 create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (3da4adcab52 -> ac407681e3d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 3da4adcab52 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 0d94d8e6a2a 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards edf6aa9a1e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 6dc20ccc631 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 98bceb5a0e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 996c32068ba 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards faa6293b5d1 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards b523b7d335e 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 54ab6c39a5e 214: onsuccess: #26: 1: Success after binutils: 12 commits discards b62f293f2a0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards c40ca0c2b55 212: force: #24: 1: Success after binutils: 2 commits discards 2ba09d4a881 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards effc8ec0f75 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 713dfe7f517 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards bb80c5dfd3b 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a038ffc12f1 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b288ed9ea8f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards c823353a2bc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 192a8d2a0c0 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 039c9a078ca 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ea9dede1e7f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 67dd291584c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4b2c9e19509 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 1cd2730d504 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards df3dcba355a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c0faf349706 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ce0552ca16d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 8bc8ea72280 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5b3f9903fe8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9fb102550c8 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 1c8189e8d1c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 28011f6e09a 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2a9ec992007 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards cfaa043e637 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 5bffdff4c35 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards cdbf2af681c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 5019fdd3236 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 6d8917ee7b9 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 9e9d3e95bf1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 91ef39f2cfd 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards f0113369d4b 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 2f6a6a47565 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 292f6b54cd5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 9069a90e939 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 01af38a1e0b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards cfde8d602f1 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 65f110ea78a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 413824e18c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards d77b6a13946 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 8e4552d04cd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 0a9c50af9af 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 82354a06b96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 1600b5e132a 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 868c5f89558 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards eb1afa15712 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards b7fbe7ed605 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards fa874254d15 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards db51176a767 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 703db0a225c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 2b1a1c5b95f 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 5a647edfb99 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards d2658339427 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards b4ff12e437c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 93e44f75aac 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 4a534108718 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ba80d7ce826 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards b6ea428944e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 68bfcbd83e2 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 829666b1eab 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 5f10df012cd 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 23b40fd7d60 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 953c9cef35f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 4967a1340e2 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards b0a803452bf 149: onsuccess: #684: 1: Success after linux: 10 commits discards 8ef70b66b87 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 14d06284f09 147: onsuccess: #681: 1: Success after gcc: 6 commits discards ed9c5787dd3 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 068a9962d53 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 408b04c4b14 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards ccd9aa5116e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 9ad2636230d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards e398205ff04 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 1097d04a990 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards ba3c5111e24 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 498a0890f50 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 503e4edf1a8 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards eef4406ea24 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 1e40cf196d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards a8ed71f32d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 5e057514811 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards d35dd9cf5eb 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 12f7acf0b07 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards a16fab2f27c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d9633133adf 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 380f1edf3c7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards fe33cb079bf 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 142ed6aa719 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 6e6461ae5a3 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 6a121413d41 124: onsuccess: #657: 1: Success after glibc: 2 commits discards cd746593ff3 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 749744e782f 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 41200a18ea9 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 6d3176f3529 123: onsuccess: #655: 1: Success after binutils: 22 commits new 012f04484f2 124: onsuccess: #657: 1: Success after glibc: 2 commits new e8958a158f3 125: onsuccess: #658: 1: Success after linux: 3224 commits new 77f8c93bca8 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 5103aac4762 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new af0afc3a923 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 88fe92377a2 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new f809971da8b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9a968397ac2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 57f9fdefbc6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new a64e9229bb4 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 8dfd6941b91 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 8fe1cecab12 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new bbd6f983210 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new ac00e08ac24 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new c6fece24a39 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new b48a62a4a49 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new f36cb89854e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 82cb7a7b07f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 0d7f80c24b5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ae76367e7e0 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ba72ee4ab56 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 99131fb743a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new b85aa9ae533 146: onsuccess: #680: 1: Success after binutils: 20 commits new 37fec3247e4 147: onsuccess: #681: 1: Success after gcc: 6 commits new 2e3bce7cb59 148: onsuccess: #683: 1: Success after glibc: 9 commits new 448c33bf86a 149: onsuccess: #684: 1: Success after linux: 10 commits new f965faf0a08 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new ed0fdac1060 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 8c53cbce87e 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 2b49191a597 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 88ea2c06d92 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 3bc14dcd2d0 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 0d85970c317 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 7e4f8ca32ab 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 480b53d72f6 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new b8982d4383b 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 06f296da415 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 78d6e662173 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new aa12660ad3a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new da7bcea9077 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 287484b2b2b 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new e399ecf923f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new abc8e16f3cb 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 679746e5ada 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 3552abd186d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new eeab0c63239 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 07f08687078 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 229b01a5574 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 2e4f7c33b2e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new d10238118f9 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 034da0f0d44 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 8a5c0ed037e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new a427eb9b4a3 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new fbb804ddebc 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 93b59f7c805 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 3b74d79165c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new d3a326e27c1 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new d7017e02bbf 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 6b2141a28a1 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 4571d83ddfe 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 80010a483be 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 676b0d6795d 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 8712b2199fc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 4e614fc3673 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 84e372afb59 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 83ed7efd5f3 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 6cac9e2e195 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 8ad222a486b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a57c9dc05e2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6cc9e169b54 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 4c1502dfa5c 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 3f63d5fa1f4 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5986e8808bb 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f9b7609bfd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2147a03bf81 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new be9deb8db24 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a03a696582a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new fb21f90a38d 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 38861d54f9c 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7b1496a4d76 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 4f32b01b49f 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 335e7d66686 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 351cddc0cf2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new bf970344ce7 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bd72f356a50 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new b37fdaf4fcf 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 8a25f8aafc1 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new fb9cfd6c773 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 219adbc1269 212: force: #24: 1: Success after binutils: 2 commits new 2e430e4242f 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new f8a4c1787e9 214: onsuccess: #26: 1: Success after binutils: 12 commits new d0f8fdf958a 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new c8041bd69a9 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 2f8286e05f1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f165cd513e6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 367a8bcba5c 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 9eef6655014 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new cc9edfcee58 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new dad2d1dff07 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new ac407681e3d 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] 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 (3da4adcab52) \ 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 2028 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 35136 -> 35128 bytes 04-build_abe-gcc/console.log.xz | Bin 203396 -> 202888 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 241460 -> 241600 bytes 08-build_abe-gdb/console.log.xz | Bin 34636 -> 34512 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3800 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2120 -> 2184 bytes 11-check_regression/console.log.xz | Bin 4196 -> 5232 bytes 11-check_regression/mail-body.txt | 35 ------------------------- 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 40 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 ------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 +++++++++++++-------------- sumfiles/binutils.log.xz | Bin 62984 -> 63100 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83964 -> 83976 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122620 -> 122508 bytes sumfiles/ld.sum | 4 +-- 33 files changed, 88 insertions(+), 126 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-O3 updated (203c96b8366 -> 5b9ca3cdcbd)

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-O3 in repository toolchain/ci/base-artifacts. from 203c96b8366 1: onsuccess: #3: 1: [TCWG CI] Success after binutils/glibc [...] new 5b9ca3cdcbd 2: force: #5: 1: [TCWG CI] Success after gcc: 34 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 1996 -> 2132 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 27304 -> 27340 bytes 04-build_abe-stage1/console.log.xz | Bin 71184 -> 71808 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 241664 -> 241672 bytes 08-build_abe-stage2/console.log.xz | Bin 175940 -> 176440 bytes 09-benchmark/benchmark-build.log | 90 +- 09-benchmark/benchmark.log | 88 +- 09-benchmark/console.log.xz | Bin 3996 -> 3988 bytes 10-check_regression/bmk-specific-variability.csv | 148 +- .../compare-results-vs-first-internal.csv | 231 +- .../compare-results-vs-prev-internal.csv | 241 +- 10-check_regression/console.log.xz | Bin 16292 -> 16136 bytes .../csv-results-vs-first-1/md5sum.csv | 2000 +- .../csv-results-vs-first-1/perf.csv | 2535 +- .../csv-results-vs-first-1/results.csv | 2856 +- .../csv-results-vs-first-1/size.csv | 503042 +++++----- 10-check_regression/csv-results-vs-first-1/sve.csv | 15478 +- .../csv-results-vs-first-1/vect.csv | 4092 +- .../csv-results-vs-prev-0/md5sum.csv | 1992 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2584 +- .../csv-results-vs-prev-0/results.csv | 16274 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 926710 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 18374 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 908 +- .../csv-results-vs-prev-1/md5sum.csv | 2000 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2535 +- .../csv-results-vs-prev-1/results.csv | 2856 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 503042 +++++----- 10-check_regression/csv-results-vs-prev-1/sve.csv | 15478 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 4092 +- .../output-bmk-results/exe.improvement | 11 - .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression | 2 +- .../output-bmk-results/exe.regression.diff | 2 +- .../output-bmk-results/symbol.improvement | 11 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 17 +- .../output-bmk-results/symbol.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 2365 +- 10-check_regression/results-vs-first-internal.csv | 231 +- 10-check_regression/results-vs-first.csv | 231 +- 10-check_regression/results-vs-first.log | 1624 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 27 +- 10-check_regression/results-vs-prev-full.csv | 2641 +- 10-check_regression/results-vs-prev-internal.csv | 241 +- 10-check_regression/results-vs-prev.csv | 241 +- 10-check_regression/results-vs-prev.log | 1876 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 8 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 8 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../450.soplex/results-metadata.json | 8 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 8 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 8 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 8 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 20 +- mail/changes-list-short.txt | 2 +- manifest.sh | 27 +- results_id | 2 +- 105 files changed, 1019228 insertions(+), 1018526 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.improvement delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (ceef47994d1 -> bbfc4018b55)

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 ceef47994d1 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 2b3a720a528 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 22ff94ed266 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 69bd9c8715d 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 3504180fae4 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 4e741749d81 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 0a8d3b6a5aa 228: force: #74: 1: Success after gdb: 53 commits discards ed22e52f59a 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 1228697633b 226: force: #70: 1: Success after baseline build: no new commits discards 088e6516926 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 0d59d9e9417 224: force: #65: 1: Success after gdb: 50 commits discards 43ba0597417 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards 10f7b8fbe3c 222: force: #60: 1: Success after gdb: 16 commits discards 16288d3ffa0 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 8770ec5fff9 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards d865e59547a 219: force: #50: 1: Failure after linux: 2520 commits discards 15d4cd9e10a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 5549baf7fc4 217: force: #45: 1: Success after linux: 1 commits discards d50cc8d4753 216: force: #43: : Failure after baseline build: no new commits discards 6a8cf6a8714 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 7e42503ec28 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 23db9a84013 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 3ed856e9ea8 212: force: #27: : Failure after baseline build: no new commits discards a25dd297a45 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c7c44fa77ec 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 26ca4a4580a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards e2ff8e90007 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 0acd00324dc 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards ca899bf37b8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards e888a5238bc 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2c215b8bf1e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 77a1794af98 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 697524842ee 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 58254dcaf9b 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9d4e8c64ab5 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 14b9f279e52 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ba93010fad8 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f7931cbb25e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2d30c0bfeff 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 679ab1ea81a 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9c0dd9428fe 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards e0a92c36669 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1d7d17b7322 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards e09a9b1b897 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 9b6e96a637b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ac5f6c9bbc3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 0a802b5267c 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 244aefd4297 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards ec3471af239 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 5909aae0f20 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 952eceef36e 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 07a87d7d0a8 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 25ab6baf076 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 904f86ab0a5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 58bdcd09acf 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 6acefcd7e6c 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 09c27630ffa 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 3d243f166c5 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 6d7511dff68 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 43a764e70c3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards c71f2e24fac 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c02dcd6f5e6 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 0dce0d47dde 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 84281417fd7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards f908a51a903 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 013df36a749 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 638068883ce 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 3be99e99c14 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 897b8369acc 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 435984b53b5 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 30cf0297f8b 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards fea0cd4643b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 841ab09085e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards af2e4355dda 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 271869ee6f8 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 73ebefd8638 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 58d31635af7 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 07f20c70460 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f88ee05776c 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards f372a84e0ed 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 35f949f5381 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards fe5a5d2e652 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 0daa1de141b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 469a1f13c37 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 4209329e7c8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e083bb11147 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards a05be196643 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 0bbf062cb14 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards fcb9983fdbd 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards fc0cce9aa56 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards a7ead3ac2c8 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 3ee014b2938 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards b86758ebb1f 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards baaa5b58652 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 5d576cf6153 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards ffd48235b38 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 9a4d4de68ad 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 6af750d2e05 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards c8c9e505a6a 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 087ebac7905 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e846de3ee8d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 8c8105e413f 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new c1f144435db 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 74bcbaf9f59 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new bb7d446dae4 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new e075e6102a6 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 2d98de48760 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new efa49657c75 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 7b4f1869840 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 23a793a47b7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 1c45638eb69 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 7ac9cc3debf 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new c2622908e5a 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f8c83e9ad84 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new cb41d026352 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new aeae1a38ea2 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 3d8f72586c1 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 8f502054d08 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 68458c82fa6 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 553ae8031ab 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new c68d1dccd97 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 80b424899b2 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 048b807e243 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7419a7b452e 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 73790f9ba5b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 38f608ade58 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 78e7e08bf80 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 4098b2bbe7a 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 9b078512755 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 780ae10c69a 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 4773152cdd7 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new ab367f6f5a7 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 9174ac3e7cc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 86774d8b725 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 07bb12712c3 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new e8b858eb63f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 7c53c0a9721 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 3f55178a403 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 738bd2d8509 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 6b6bdcf99aa 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new d45a2efaf14 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new ae31806821f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 1beaf93b234 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 679deefe487 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new fec1d0ad2e2 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new c1d96e2fded 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 9300b5060ae 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 4badc68625e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 3226cb88689 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new e1e82299ac6 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ad04af1217c 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 94922fa541a 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 973b1a8bca9 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 9e6a508cc77 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new d2df3a56be7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 75766395a3d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 951f88cab8b 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 8860f87f5ae 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 749e7cb9d16 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new a339ccda78f 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new fba72a2f73e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 715772580d2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new e60ceddf781 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5c0a145b9be 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 6571b82c33f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0e219835234 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new b54b4c72ff2 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 780263c5796 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 59cf94fea3e 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 01ce401126a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 93a79a7314d 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new a66dd22ee76 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 30a9c869753 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 65913b6ea97 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 406c38be0b1 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 23523d961a4 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a73b639b31f 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1d8b860f5c4 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d263e18c326 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 17788aa2ec7 212: force: #27: : Failure after baseline build: no new commits new d5de066ff8c 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new c204aea037e 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 18204edd878 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new b271e3aa1d8 216: force: #43: : Failure after baseline build: no new commits new 42ab38735cd 217: force: #45: 1: Success after linux: 1 commits new ff1a92045f9 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new d2427358ec1 219: force: #50: 1: Failure after linux: 2520 commits new 255b5981478 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new fed1699c60d 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new d3d562bc480 222: force: #60: 1: Success after gdb: 16 commits new 9e678f5d019 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 09a3cf33f26 224: force: #65: 1: Success after gdb: 50 commits new d86b191236e 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new c600375facf 226: force: #70: 1: Success after baseline build: no new commits new 1c1b345cf49 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 7f4ee76ba70 228: force: #74: 1: Success after gdb: 53 commits new 8de34cccd68 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new 1ae111fa4f5 230: onsuccess: #78: 1: Success after gdb: 2 commits new 952afe39770 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new e43114544d0 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 3c7e8d29504 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 163278c0cf6 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new bbfc4018b55 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] 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 (ceef47994d1) \ 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 2272 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49304 -> 48468 bytes 04-build_abe-gcc/console.log.xz | Bin 235248 -> 235824 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 233448 -> 232416 bytes 08-build_abe-gdb/console.log.xz | Bin 47124 -> 46288 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4340 -> 4760 bytes 11-check_regression/console.log.xz | Bin 2440 -> 11748 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1093 ++++++++++++- 12-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 32 +- mail/changes-list-short.txt | 2 +- manifest.sh | 35 +- sumfiles/gdb.log.0.xz | Bin 2908432 -> 2965440 bytes sumfiles/gdb.log.1.xz | Bin 143892 -> 138384 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10272 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 10424 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 10292 bytes sumfiles/gdb.log.13.xz | Bin 0 -> 9964 bytes sumfiles/gdb.log.14.xz | Bin 0 -> 10196 bytes sumfiles/gdb.log.15.xz | Bin 0 -> 10364 bytes sumfiles/gdb.log.16.xz | Bin 0 -> 10064 bytes sumfiles/gdb.log.17.xz | Bin 0 -> 10232 bytes sumfiles/gdb.log.2.xz | Bin 11384 -> 16500 bytes sumfiles/gdb.log.3.xz | Bin 6604 -> 10288 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 10080 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10208 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10096 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10368 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10056 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10248 bytes sumfiles/gdb.sum | 1719 ++++++++------------ sumfiles/gdb.sum.0 | 1729 ++++++++------------ sumfiles/gdb.sum.1 | 958 ++++++----- sumfiles/gdb.sum.10 | 2192 ++++++++++++++++++++++++++ sumfiles/gdb.sum.11 | 2237 ++++++++++++++++++++++++++ sumfiles/gdb.sum.12 | 2161 +++++++++++++++++++++++++ sumfiles/gdb.sum.13 | 2183 ++++++++++++++++++++++++++ sumfiles/gdb.sum.14 | 2192 ++++++++++++++++++++++++++ sumfiles/gdb.sum.15 | 2189 ++++++++++++++++++++++++++ sumfiles/gdb.sum.16 | 2190 ++++++++++++++++++++++++++ sumfiles/gdb.sum.17 | 2166 +++++++++++++++++++++++++ sumfiles/gdb.sum.2 | 2789 +++++++++++++++++++++++++++++---- sumfiles/gdb.sum.3 | 2337 +++++++++++++++++++++++++-- sumfiles/gdb.sum.4 | 2160 +++++++++++++++++++++++++ sumfiles/gdb.sum.5 | 2172 +++++++++++++++++++++++++ sumfiles/gdb.sum.6 | 2203 ++++++++++++++++++++++++++ sumfiles/gdb.sum.7 | 2197 ++++++++++++++++++++++++++ sumfiles/gdb.sum.8 | 2176 +++++++++++++++++++++++++ sumfiles/gdb.sum.9 | 2173 +++++++++++++++++++++++++ 60 files changed, 38227 insertions(+), 3142 deletions(-) create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz create mode 100644 sumfiles/gdb.log.13.xz create mode 100644 sumfiles/gdb.log.14.xz create mode 100644 sumfiles/gdb.log.15.xz create mode 100644 sumfiles/gdb.log.16.xz create mode 100644 sumfiles/gdb.log.17.xz create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.log.6.xz create mode 100644 sumfiles/gdb.log.7.xz create mode 100644 sumfiles/gdb.log.8.xz create mode 100644 sumfiles/gdb.log.9.xz create mode 100644 sumfiles/gdb.sum.10 create mode 100644 sumfiles/gdb.sum.11 create mode 100644 sumfiles/gdb.sum.12 create mode 100644 sumfiles/gdb.sum.13 create mode 100644 sumfiles/gdb.sum.14 create mode 100644 sumfiles/gdb.sum.15 create mode 100644 sumfiles/gdb.sum.16 create mode 100644 sumfiles/gdb.sum.17 create mode 100644 sumfiles/gdb.sum.4 create mode 100644 sumfiles/gdb.sum.5 create mode 100644 sumfiles/gdb.sum.6 create mode 100644 sumfiles/gdb.sum.7 create mode 100644 sumfiles/gdb.sum.8 create mode 100644 sumfiles/gdb.sum.9 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (525644affd2 -> cc4fc193d4b)

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 525644affd2 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards f56bbb960bd 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 4cbd4c4f6bb 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 31fe11c9593 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 0b3e415bbdf 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 46a83e6529e 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards e9e83308679 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 46436edd0eb 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 809c32129b6 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards c04ff7f96e3 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards f0324fdf335 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 83a4f05a5fd 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 0c5e2e2809b 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] discards 48ac2f1cbb0 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] discards 76016193bac 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards 761176ee174 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 41cb875d0ad 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 95159d682b4 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards 1cf935bda47 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 93b25ac07e4 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards b7d38d9ea9b 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 3aa57ee0e69 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards b92fda0aa07 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9f532d701d5 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards ee6ff56a427 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a6a6ddf978c 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 842311fcf7f 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 0e2144de1e1 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards 7e8612b6db1 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a1693bc9ec3 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b2301dd0493 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 227a211947f 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 4c152fec373 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 891c800342d 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 15ed622f673 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards 21779efc1ba 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards 823bceef543 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 558f5b11618 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards 71f6373130c 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 58a248b4647 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards 670c7a91d69 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards af55412d463 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards 37805d5e396 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards 0e0af6b65bd 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 0755d41d819 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 69f832b237c 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 1e51c278e71 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 35fbd8a05e9 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards 876af6ffe96 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards ed64f70a378 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards c0378c1b81a 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards e02327b79d4 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards ddd700b781b 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 4bdb8b280e8 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 41abd0d0a5f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards ae607fd1a44 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards fd00b134a14 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards ad6c0030e54 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards f70ba8e53a4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards 13a18ee3f25 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards 43d236614d5 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards 5fa299d419a 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards 4a4d81c9ee5 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards 096fc5e40ed 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards 7f557ccfecd 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 00f9ec81612 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards a9ea900be66 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards d905e6a6526 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards 92997627538 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards d6c8f3d12f5 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards d1eb7d56920 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards f5f9e485817 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards f7573b9edf1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards 8fc64188a7b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 510508baa6b 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards 28788c0d3d7 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards ed222f32674 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards 68b139e6903 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards 96967d58983 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 09785b42f43 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards 234a41276a7 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 190f1841308 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards 7e6bb1bd359 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards dcf3c51aadd 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards cf3a75e4af1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards e6f001dcf17 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 9d1d96f50e0 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards c4a5fc7bb0d 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards ba427d490e5 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards f4eb6032ffc 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards e8c2a3a5dbe 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards f11a781c9c9 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards 6c502ef9beb 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 538b7d39802 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards 065adf20d68 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8916f3d5eaf 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards adb7e8107db 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards af95fe935bf 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 979957df6fc 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 6c57d6a49e7 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards cd6ab13c107 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new 0ed67635dc7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new 07a66c915ba 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new 3100bb755df 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 2ab1c736e4e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new f7fded46755 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new b362dc59b4c 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new fd98992658d 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 9896361bded 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new fe00e63f3d8 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 967478f7a4c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new a57c1da7ed4 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 46c8f099d89 387: onsuccess: #2208: 1: Success after gcc: 2 commits new dc6f0d02f4a 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new ac9d9f1783a 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new a22e717edc7 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new ba030b55496 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new 931b323cf8e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new 0f45ed7c035 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new 021f8ab2949 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new a0d615bf460 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new 974f96dd6df 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new e1480a53d3e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new bebf7e3b776 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new 8289e52c435 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new ee1120dab78 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new 0891b503ea1 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new c80ba889f20 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new 70bc0d5b7e0 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new 3c6700322c7 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new 83005edb14f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 32dde9e5a54 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new 2927c150df9 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new b2b3fbfbc26 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 03b27bea17f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new b8eb83a181f 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new b0a12e5a805 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2c66541e35b 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new c73cba0c175 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new 8fb3f5a9ae2 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new fe404ab427e 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new 0986c832229 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new 1d0814184ff 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new ed952ac9e11 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new 1b5ed88c7a2 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new 8dfa6368e50 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new e7e89219856 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new 7a03d53c47c 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 7ebe32799b6 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 55a1e68600c 424: onsuccess: #2248: 1: Success after gcc: 6 commits new bb9ce0bda6a 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new 17e3d6758f5 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new c7a138c1104 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 58bfa21306c 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 5a3f0064664 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 452de5e25ba 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new 3c234aaa0e2 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new 40ddbfd23b5 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 6e05c3709c1 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new 145d6bf7d00 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 68279fba432 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new 62c49174963 436: onsuccess: #2260: 1: Success after gcc: 7 commits new a46b15af3a4 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new c1fb85d1db0 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new 4aa379d68cf 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new 4d85ff41575 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new 82d89d09ac8 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new 92e81d4ecc3 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new 3eaa72796c9 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 5a0dc6be369 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 32e6b8dfd0e 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new e756b923dab 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new d488ccd0f51 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new bd82a13d9c9 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f3ef6109c8e 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 5f668402cdd 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new cf79d8593fa 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 630a3a40a3a 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c856cf5b20b 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new c4b4bb7f5ab 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c9aaa74e235 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 5e103916934 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 8e729d5a02e 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new dec52752b76 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 383b56fba8c 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new 29fb50de477 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 391bfd9bb59 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 2af836fcefd 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new 52f41968188 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] new d0205b68e9a 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] new 73788b19c6f 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 9932ee32b87 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 61b8a29e8c2 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new c8edfa13b4c 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new c40aee37b38 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new dbc941c83d3 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new c6e49190627 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new bfe9664daf7 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 7c6f9cdf351 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new f3b2df4a70d 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 58de071803a 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 2f1aa64ee7c 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new cc4fc193d4b 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] 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 (525644affd2) \ 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 2080 -> 2084 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 26884 -> 26700 bytes 04-build_abe-stage1/console.log.xz | Bin 88852 -> 89196 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8220 -> 8480 bytes 07-build_abe-glibc/console.log.xz | Bin 233684 -> 232408 bytes 08-build_abe-stage2/console.log.xz | Bin 224820 -> 225116 bytes 09-build_abe-gdb/console.log.xz | Bin 34088 -> 34444 bytes 10-build_abe-qemu/console.log.xz | Bin 30772 -> 30316 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6592 -> 6500 bytes 13-check_regression/console.log.xz | Bin 5200 -> 6540 bytes 13-check_regression/mail-body.txt | 43 - 13-check_regression/mail-subject.txt | 1 - 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 92 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 38 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 43 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 48 +- sumfiles/g++.log.sep.xz | Bin 112688 -> 118516 bytes sumfiles/g++.log.xz | Bin 2660560 -> 2656824 bytes sumfiles/g++.sum | 51 +- sumfiles/g++.sum.sep | 11637 +++----------------------------- sumfiles/gcc.log.sep.xz | Bin 122000 -> 217552 bytes sumfiles/gcc.log.xz | Bin 2239248 -> 2231220 bytes sumfiles/gcc.sum | 13 +- sumfiles/gcc.sum.sep | 7402 +++++++++++++++++++- sumfiles/gfortran.log.sep.xz | Bin 43428 -> 52240 bytes sumfiles/gfortran.log.xz | Bin 900700 -> 898796 bytes sumfiles/gfortran.sum | 5 +- sumfiles/gfortran.sum.sep | 5976 ++++++++-------- sumfiles/libatomic.log.xz | Bin 2280 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217128 -> 217208 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 14336 -> 12224 bytes sumfiles/libstdc++.log.xz | Bin 447520 -> 445448 bytes sumfiles/libstdc++.sum.sep | 360 +- 52 files changed, 11605 insertions(+), 14219 deletions(-) delete mode 100644 13-check_regression/mail-body.txt delete mode 100644 13-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (8dd57939c20 -> 36330e2e955)

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 8dd57939c20 tree-ssa-math-opts: Move PROP_gimple_opt_math from sincos p [...] new 36330e2e955 ipa/106124 - ICE with -fkeep-inline-functions and OpenMP 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/dwarf2out.cc | 1 + gcc/testsuite/g++.dg/gomp/pr106124.C | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+) create mode 100644 gcc/testsuite/g++.dg/gomp/pr106124.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (91293ffb6af -> 8dd57939c20)

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 91293ffb6af c++: alias ctad refinements [PR109321] new c9954996cd6 tree-optimization/109154 - improve if-conversion for vectorization new 8dd57939c20 tree-ssa-math-opts: Move PROP_gimple_opt_math from sincos p [...] 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/testsuite/gcc.dg/pr109301.c | 13 +++++++++++++ gcc/tree-if-conv.cc | 24 +++++++++++++++++++----- gcc/tree-ssa-math-opts.cc | 4 ++-- 3 files changed, 34 insertions(+), 7 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/pr109301.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (0c7dbcca0da -> 1597009f1fa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. discards 0c7dbcca0da 194: onsuccess: #35: 2: Success after binutils/gcc: 7 commits discards f8ccf16ed4c 193: onsuccess: #34: 2: Success after binutils/gcc: 3 commits discards f8a03c4a09e 192: onsuccess: #33: 2: Success after binutils/gcc: 35 commits discards 60fbc8daa2a 191: onsuccess: #32: 2: Success after binutils/gcc: 31 commits discards 9a75eae6dc8 190: onsuccess: #31: 2: Success after binutils/gcc: 30 commits discards 910ba284fbc 189: onsuccess: #30: 2: Success after binutils/gcc: 45 commits discards 618a04ff050 188: onsuccess: #29: 2: Success after binutils/gcc: 31 commits discards 2d7921f4d61 187: onsuccess: #28: 2: Success after binutils/gcc: 16 commits discards 37fd4253fb9 186: onsuccess: #27: 2: Success after binutils/gcc: 29 commits discards 6f31099394e 185: onsuccess: #26: 2: Success after binutils/gcc: 44 commits discards 32d29c456c5 184: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards a5ac4c68fc1 183: onsuccess: #24: 2: Success after binutils/gcc: 38 commits discards 673720ec19a 182: onsuccess: #23: 2: Success after binutils/gcc: 42 commits discards fc4f6e91f3c 181: onsuccess: #22: 2: Success after binutils/gcc: 59 commits discards f945f0e0c16 180: onsuccess: #21: 2: Success after binutils/gcc: 13 commits discards fd281e6bf85 179: onsuccess: #20: 2: Success after binutils/gcc: 14 commits discards 3a6edd40da9 178: onsuccess: #19: 2: Success after binutils/gcc: 60 commits discards 039c5be566b 177: onsuccess: #18: 2: Success after binutils/gcc: 34 commits discards c59955e3f48 176: onsuccess: #17: 2: Success after binutils/gcc: 42 commits discards cb789753fdd 175: onsuccess: #16: 0: Success after binutils: 24 commits discards 6f4b3ba5d86 174: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards a30a3b82a61 173: force: #14: 2: Success after binutils: 10 commits discards 8cfcf6f622c 172: onsuccess: #12: 2: Success after binutils/gcc: 41 commits discards 299189590e9 171: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 3badf261819 170: onsuccess: #10: 2: Success after binutils/gcc: 11 commits discards bfb6360b5f9 169: onsuccess: #9: 2: Success after binutils/gcc: 50 commits discards 3cf39086757 168: onsuccess: #8: 2: Success after binutils/gcc: 35 commits discards af8b533da49 167: onsuccess: #7: 2: Success after binutils/gcc: 395 commits discards 44d92826043 166: onsuccess: #581: 2: Success after binutils/gcc: 190 commits discards 46ed8035642 165: onsuccess: #575: 2: Success after binutils/gcc: 86 commits discards 70e95b36132 164: onsuccess: #574: 2: Success after binutils/gcc: 114 commits discards b612fb223b1 163: onsuccess: #572: 2: Success after binutils/gcc: 147 commits discards 31b837326e0 162: onsuccess: #571: 2: Success after binutils/gcc: 75 commits discards f88990aeea1 161: onsuccess: #570: 2: Success after binutils/gcc: 57 commits discards 37271592245 160: onsuccess: #568: 2: Success after binutils/gcc: 20 commits discards 807eb883fa9 159: onsuccess: #567: 2: Success after binutils/gcc: 28 commits discards 8ee0498d4ba 158: onsuccess: #566: 2: Success after binutils/gcc: 7 commits discards 68d53c174d0 157: onsuccess: #565: 2: Success after binutils/gcc: 79 commits discards 1475c7ce842 156: onsuccess: #562: 2: Success after binutils/gcc: 47 commits discards 29ad4d0794e 155: onsuccess: #561: 2: Success after binutils/gcc: 108 commits discards 1edbe0e916e 154: onsuccess: #560: 2: Success after binutils/gcc: 59 commits discards 0f42669883e 153: onsuccess: #558: 2: Success after binutils/gcc: 28 commits discards a3f1c74310b 152: onsuccess: #556: 2: Success after binutils/gcc: 129 commits discards 170448dd87e 151: onsuccess: #555: 2: Success after binutils/gcc: 27 commits discards 5cafc17b446 150: onsuccess: #554: 2: Success after binutils/gcc: 80 commits discards 477b3218eee 149: onsuccess: #553: 2: Success after binutils/gcc: 28 commits discards 587e4f50e21 148: onsuccess: #552: 2: Success after binutils/gcc: 35 commits discards e4db2e6162d 147: onsuccess: #551: 2: Success after binutils/gcc: 6 commits discards de53d16ca94 146: onsuccess: #550: 2: Success after binutils/gcc: 39 commits discards 4f6a38d0560 145: onsuccess: #549: 2: Success after binutils/gcc: 33 commits discards 9934fe788a2 144: onsuccess: #548: 2: Success after binutils/gcc: 35 commits discards 6db170fd751 143: onsuccess: #547: 2: Success after binutils/gcc: 77 commits discards 3b77970baab 142: onsuccess: #546: 2: Success after binutils/gcc: 37 commits discards a766f8ffc2b 141: onsuccess: #545: 2: Success after binutils/gcc: 123 commits discards cdb7244b6f4 140: onsuccess: #544: 2: Success after binutils/gcc: 46 commits discards 65c2c647a04 139: onsuccess: #543: 2: Success after binutils/gcc: 111 commits discards c4ea217de65 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits discards fb6ea6294e6 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits discards ea74c956fc7 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits discards 92d32f77f4c 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits discards e133ed5070f 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits discards 89373be80ed 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits discards c5dd183c4ff 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits discards 83201ff556a 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits discards 5bb88f74bff 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits discards 6c984ca119b 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 76f82b802c3 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits discards f74fd690c85 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits discards be34b284f08 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits discards 1612a753381 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits discards 73b95f0af23 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits discards 93a3b9e5278 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits discards a32837f0f2c 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits discards 45b122010af 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits discards 1029c9aca08 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits discards b85aa338576 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits discards dfc3f9ee57a 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits discards 64e2055b29d 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits discards 713d6cfb33e 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits discards b78d51f4c9a 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits discards bf29225904b 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits discards eded369923c 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits discards 7642782c5e6 112: onsuccess: #510: 2: Success after binutils/gcc: 3 commits discards e7ba6562139 111: onsuccess: #509: 2: Success after binutils/gcc: 36 commits discards fc67634144d 110: onsuccess: #508: 2: Success after binutils/gcc: 31 commits discards 408b95e2453 109: onsuccess: #507: 2: Success after binutils/gcc: 27 commits discards 078753b57f0 108: onsuccess: #506: 2: Success after binutils/gcc: 47 commits discards 69f31eb1b53 107: onsuccess: #505: 2: Success after binutils/gcc: 32 commits discards 3e0ff343706 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits discards 152c88b3025 105: onsuccess: #503: 2: Success after binutils/gcc: 8 commits discards ec88b575e0c 104: onsuccess: #502: 2: Success after binutils/gcc: 31 commits discards 4e41ebb2fc9 103: onsuccess: #501: 2: Success after binutils/gcc: 37 commits discards 94f891c875d 102: onsuccess: #500: 2: Success after binutils/gcc: 27 commits discards 1d29bcdc4b1 101: onsuccess: #499: 2: Success after binutils/gcc: 172 commits discards 3e80026e5cc 100: onsuccess: #498: 1: Success after gcc: 85 commits discards 9aebc033b2b 99: force: #497: 1: Failure after basepoints/gcc-13-4227-g0 [...] discards d45bd2087ee 98: force: #496: 2: Success after gcc: 9 commits discards 955a24dea7e 97: onsuccess: #493: 2: Success after binutils: 49 commits discards 3802d10990c 96: onsuccess: #484: 2: Success after binutils: 14 commits discards 67455b5936d 95: onsuccess: #482: 2: Success after binutils/gcc: 51 commits discards d8ce21f94f6 94: onsuccess: #481: 2: Success after binutils/gcc: 367 commits new b8eadd86e76 94: onsuccess: #481: 2: Success after binutils/gcc: 367 commits new 934695d7bce 95: onsuccess: #482: 2: Success after binutils/gcc: 51 commits new c748f380ff0 96: onsuccess: #484: 2: Success after binutils: 14 commits new 958522acc85 97: onsuccess: #493: 2: Success after binutils: 49 commits new e8a77573fa3 98: force: #496: 2: Success after gcc: 9 commits new 6a6cd517f8c 99: force: #497: 1: Failure after basepoints/gcc-13-4227-g0 [...] new d480ff05faa 100: onsuccess: #498: 1: Success after gcc: 85 commits new f37140e59d8 101: onsuccess: #499: 2: Success after binutils/gcc: 172 commits new 380ff89f6e7 102: onsuccess: #500: 2: Success after binutils/gcc: 27 commits new 5494022f32e 103: onsuccess: #501: 2: Success after binutils/gcc: 37 commits new bfe44b0991e 104: onsuccess: #502: 2: Success after binutils/gcc: 31 commits new 3b1e6e2ed9e 105: onsuccess: #503: 2: Success after binutils/gcc: 8 commits new 906fed4331c 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits new 156b47df944 107: onsuccess: #505: 2: Success after binutils/gcc: 32 commits new 1f3390e2d37 108: onsuccess: #506: 2: Success after binutils/gcc: 47 commits new d91a27a294d 109: onsuccess: #507: 2: Success after binutils/gcc: 27 commits new 20dfcd8208d 110: onsuccess: #508: 2: Success after binutils/gcc: 31 commits new 6b570938420 111: onsuccess: #509: 2: Success after binutils/gcc: 36 commits new d0a1ca55670 112: onsuccess: #510: 2: Success after binutils/gcc: 3 commits new 2472c746b2c 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits new 06c53955c04 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits new bba82a54254 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits new d8e3ff5dade 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits new 85ffa2400af 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits new 0f31ea6ff88 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits new 10978771cc3 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits new ca0f30950d7 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits new adc0f920cea 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits new 8397ff5f751 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits new 821946d5aa7 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits new 52304003968 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits new a3b493e93f8 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits new 975a74c96ce 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits new 1f80c5bfc21 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits new 096e31a701b 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits new 3a2ad0dd64a 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new 4b1c4402a8f 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits new dd0585eacc7 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits new 459ff2d3ce0 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits new 72814dc9dcf 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits new d23782f6cfa 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits new df486980edd 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits new fd445070df8 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits new c3cf4f43df7 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits new e078ecdb814 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits new 357f5716bbb 139: onsuccess: #543: 2: Success after binutils/gcc: 111 commits new 018bb5598c6 140: onsuccess: #544: 2: Success after binutils/gcc: 46 commits new 928ba8fc1a8 141: onsuccess: #545: 2: Success after binutils/gcc: 123 commits new d23f766739b 142: onsuccess: #546: 2: Success after binutils/gcc: 37 commits new e72a64d028c 143: onsuccess: #547: 2: Success after binutils/gcc: 77 commits new fd30024bc82 144: onsuccess: #548: 2: Success after binutils/gcc: 35 commits new 104dce7fdd4 145: onsuccess: #549: 2: Success after binutils/gcc: 33 commits new 53c6031e10a 146: onsuccess: #550: 2: Success after binutils/gcc: 39 commits new 5c13878d6be 147: onsuccess: #551: 2: Success after binutils/gcc: 6 commits new 2dc7deb3210 148: onsuccess: #552: 2: Success after binutils/gcc: 35 commits new 8d642c2e61a 149: onsuccess: #553: 2: Success after binutils/gcc: 28 commits new df7a24deb78 150: onsuccess: #554: 2: Success after binutils/gcc: 80 commits new 35c0e6cb32c 151: onsuccess: #555: 2: Success after binutils/gcc: 27 commits new 0fd1ced1c93 152: onsuccess: #556: 2: Success after binutils/gcc: 129 commits new e56b01b7e2f 153: onsuccess: #558: 2: Success after binutils/gcc: 28 commits new 2940ca5a76b 154: onsuccess: #560: 2: Success after binutils/gcc: 59 commits new 819659828c0 155: onsuccess: #561: 2: Success after binutils/gcc: 108 commits new d373c5290be 156: onsuccess: #562: 2: Success after binutils/gcc: 47 commits new afc67a2e757 157: onsuccess: #565: 2: Success after binutils/gcc: 79 commits new 2f9cd93c589 158: onsuccess: #566: 2: Success after binutils/gcc: 7 commits new 3b695541e9b 159: onsuccess: #567: 2: Success after binutils/gcc: 28 commits new 4f8125bcbbd 160: onsuccess: #568: 2: Success after binutils/gcc: 20 commits new 1fb64980aa2 161: onsuccess: #570: 2: Success after binutils/gcc: 57 commits new d92dd1c8f08 162: onsuccess: #571: 2: Success after binutils/gcc: 75 commits new 4d11a36be73 163: onsuccess: #572: 2: Success after binutils/gcc: 147 commits new 907d31a535d 164: onsuccess: #574: 2: Success after binutils/gcc: 114 commits new 34dbd1f1f15 165: onsuccess: #575: 2: Success after binutils/gcc: 86 commits new 5cb90eeb19e 166: onsuccess: #581: 2: Success after binutils/gcc: 190 commits new 831dfa6c720 167: onsuccess: #7: 2: Success after binutils/gcc: 395 commits new edebd5e1d4e 168: onsuccess: #8: 2: Success after binutils/gcc: 35 commits new 80d86f6b534 169: onsuccess: #9: 2: Success after binutils/gcc: 50 commits new e726e4e94a7 170: onsuccess: #10: 2: Success after binutils/gcc: 11 commits new dc8e55a76c4 171: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new 6ae0a2be8f9 172: onsuccess: #12: 2: Success after binutils/gcc: 41 commits new 3314dc25181 173: force: #14: 2: Success after binutils: 10 commits new 08550e8e575 174: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new 520593f8c69 175: onsuccess: #16: 0: Success after binutils: 24 commits new 36de74b1410 176: onsuccess: #17: 2: Success after binutils/gcc: 42 commits new 95d7cb3d768 177: onsuccess: #18: 2: Success after binutils/gcc: 34 commits new 07319c2b0ba 178: onsuccess: #19: 2: Success after binutils/gcc: 60 commits new aaf4ec36849 179: onsuccess: #20: 2: Success after binutils/gcc: 14 commits new bd6b4c5d403 180: onsuccess: #21: 2: Success after binutils/gcc: 13 commits new 722072d516f 181: onsuccess: #22: 2: Success after binutils/gcc: 59 commits new 9223f046ca5 182: onsuccess: #23: 2: Success after binutils/gcc: 42 commits new 0bd5ea52361 183: onsuccess: #24: 2: Success after binutils/gcc: 38 commits new e8430e87e45 184: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new ebce39742a6 185: onsuccess: #26: 2: Success after binutils/gcc: 44 commits new 33f9caf516a 186: onsuccess: #27: 2: Success after binutils/gcc: 29 commits new 0751b822e78 187: onsuccess: #28: 2: Success after binutils/gcc: 16 commits new 2a8a460a606 188: onsuccess: #29: 2: Success after binutils/gcc: 31 commits new fbe5bf23800 189: onsuccess: #30: 2: Success after binutils/gcc: 45 commits new cac8dae7126 190: onsuccess: #31: 2: Success after binutils/gcc: 30 commits new da31f37f6e9 191: onsuccess: #32: 2: Success after binutils/gcc: 31 commits new 27f3f79615d 192: onsuccess: #33: 2: Success after binutils/gcc: 35 commits new 8813ac42b6e 193: onsuccess: #34: 2: Success after binutils/gcc: 3 commits new 639261c0dbe 194: onsuccess: #35: 2: Success after binutils/gcc: 7 commits new 1597009f1fa 195: onsuccess: #38: 2: [TCWG CI] Success after binutils: 6 [...] 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 (0c7dbcca0da) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1932 -> 1940 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2488 bytes 04-build_abe-binutils/console.log.xz | Bin 49012 -> 48880 bytes .../console.log.xz | Bin 601384 -> 600840 bytes 06-check_regression/console.log.xz | Bin 2816 -> 2468 bytes 06-check_regression/mail-body.txt | 19 ------------ 06-check_regression/mail-subject.txt | 1 - 07-update_baseline/console.log | 34 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/changes-list-long.txt | 8 +++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 19 ------------ mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 19 ++++++------ 16 files changed, 38 insertions(+), 69 deletions(-) delete mode 100644 06-check_regression/mail-body.txt delete mode 100644 06-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (aec101ab066 -> af2724d676f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from aec101ab066 Sanity check section size in bfd_init_section_compress_status new 79260be4755 [gdb/testsuite] Fix gdb.guile/guile.exp for remote host new 7b193de63a5 [gdb/testsuite] Fix gdb.guile/scm-cmd.exp without readline new eb338e57ce4 [gdb/testsuite] Fix gdb.guile/scm-objfile-script.exp for re [...] new 7eb59fa2561 [gdb/testsuite] Fix gdb.guile/scm-objfile-script.exp for re [...] new 5fc60431a87 [gdb/testsuite] Fix /gdb.guile/scm-parameter.exp for remote host new af2724d676f [gdb/testsuite] Fix gdb.guile/scm-symbol.exp for remote host The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/testsuite/gdb.guile/guile.exp | 38 ++++++++++++++------------ gdb/testsuite/gdb.guile/scm-cmd.exp | 19 +++++++------ gdb/testsuite/gdb.guile/scm-objfile-script.exp | 4 +-- gdb/testsuite/gdb.guile/scm-parameter.exp | 11 ++++++-- gdb/testsuite/gdb.guile/scm-symbol.exp | 2 +- gdb/testsuite/gdb.guile/scm-symtab.exp | 13 ++++++--- 6 files changed, 53 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 updated (3f171878216 -> 8ab13284fff)

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_vect-spec2k6/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 3f171878216 9: force: #12: 1: [TCWG CI] Failure after basepoints/gcc-13 [...] new 8ab13284fff 10: onsuccess: #13: 1: [TCWG CI] Success after gcc: 9 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 2216 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27832 -> 27860 bytes 04-build_abe-stage1/console.log.xz | Bin 71444 -> 71168 bytes 06-build_abe-linux/console.log.xz | Bin 8424 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 242864 -> 241432 bytes 08-build_abe-stage2/console.log.xz | Bin 176288 -> 176180 bytes 09-benchmark/benchmark-build.log | 90 +- 09-benchmark/benchmark.log | 88 +- 09-benchmark/console.log.xz | Bin 3992 -> 3992 bytes 10-check_regression/bmk-specific-variability.csv | 152 +- .../compare-results-vs-first-internal.csv | 230 +- .../compare-results-vs-prev-internal.csv | 240 +- 10-check_regression/console.log.xz | Bin 16616 -> 15404 bytes .../csv-results-vs-first-1/md5sum.csv | 2139 +- .../csv-results-vs-first-1/perf.csv | 2576 +- .../csv-results-vs-first-1/results.csv | 6755 +- .../csv-results-vs-first-1/size.csv | 505601 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 15478 +- .../csv-results-vs-first-1/vect.csv | 4092 +- .../csv-results-vs-prev-0/md5sum.csv | 2130 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2564 +- .../csv-results-vs-prev-0/results.csv | 7565 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 487835 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 15464 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 3570 +- .../csv-results-vs-prev-1/md5sum.csv | 2139 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2576 +- .../csv-results-vs-prev-1/results.csv | 6755 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 505601 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 15478 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 4092 +- 10-check_regression/exe.regression | 1 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/mail-body.txt | 3 - 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.regression | 4 +- .../output-bmk-results/exe.regression.diff | 5 +- .../output-bmk-results/symbol.improvement | 10 +- .../output-bmk-results/symbol.regression | 11 +- 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 2519 +- 10-check_regression/results-vs-first-internal.csv | 230 +- 10-check_regression/results-vs-first.csv | 230 +- 10-check_regression/results-vs-first.log | 1528 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 6 +- 10-check_regression/results-vs-prev-full.csv | 2711 +- 10-check_regression/results-vs-prev-internal.csv | 240 +- 10-check_regression/results-vs-prev.csv | 240 +- 10-check_regression/results-vs-prev.log | 1910 +- 10-check_regression/results.regressions | 17 - 10-check_regression/trigger-bisect | 3 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 8 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 8 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 8 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 8 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 8 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/gcc_rev | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 11 +- mail/changes-list-short.txt | 2 +- mail/short-diag.txt | 2 +- manifest.sh | 22 +- results | 17 - results_id | 2 +- 109 files changed, 804014 insertions(+), 799457 deletions(-) delete mode 100644 10-check_regression/exe.regression delete mode 100644 10-check_regression/results.regressions delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-check_regression/trigger-notify delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023