Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (dfbf7be137 -> 0b42063425)

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 dfbf7be137 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards d7b9d9f8c5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards e36dfd3463 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 54c8117fa0 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 2132a24530 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 36ef04ed35 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 7d910d584a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 35bff9dcc5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 214e3c3d16 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 51ae77f1b5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 11e8ac1862 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 46164bc908 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 753aaa092b 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards e23596a42e 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards aa4f5a6e04 125: onsuccess: #614: 1: Success after linux: 12 commits discards efaccbb787 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 6687fe3169 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 7476edeb6f 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 4e337aa060 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 92f1cc8875 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 4e692740f7 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 8a13167688 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 65309dff44 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 2823851c7d 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 4553efce3f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 992c82bbd6 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 65aab1a39c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards d550a2cb09 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards acd6a89fa7 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards bfbc0bfa75 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 2687a29623 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 7f7efa361b 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards a88516416e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 9ea941995a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 24104032e7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards e00d5f8daa 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a6ed9bc753 103: onsuccess: #589: 1: Success after binutils: 3 commits discards da51d21523 102: onsuccess: #586: 1: Success after binutils: 5 commits discards f6ec28a9fc 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 8337b82aad 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ad64a03419 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards f106060165 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 928a55a40b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 85985bf71a 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards fd8d9d55df 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 073cefcdc9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 09a6477d04 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 1de75128aa 92: onsuccess: #575: 1: Success after linux: 34 commits discards 033e8fb57e 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 42aff41342 90: onsuccess: #572: 1: Success after binutils: 15 commits discards e0e93e46ec 89: onsuccess: #570: 1: Success after linux: 11 commits discards 4cb308e88a 88: onsuccess: #569: 1: Success after glibc: 10 commits discards da762d7665 87: onsuccess: #567: 1: Success after binutils: 8 commits discards a572e4cd8a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 114eec7324 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards afbac1392e 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 3c9f2dae7f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 0ec5be12cf 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards a28b092120 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards ef052d6ae4 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards edc1884ed3 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 31a4623ded 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 5f19f6d91d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 74b5eb501c 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 4a15220c8c 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 2f73678867 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 6b2463e220 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards f633870196 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards dc098f8189 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 0fc48c5274 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 6548a2ed5c 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 830a4ba928 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards f2d4aab95e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 0d8e3105ee 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 01e565adfd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards f4020a6178 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards c3d4130015 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards ebcec72911 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards bc489d4897 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 29d1ce91f4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 47ccd1d705 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards d14aee5266 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards e89fadd5e8 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards ff27b8ad07 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 880495ecec 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards cbcf3c90ef 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e4bf311de9 53: onsuccess: #531: 1: Success after binutils: 12 commits discards bc48da4b6e 52: onsuccess: #528: 1: Success after binutils: 8 commits discards c4fbe2b0cc 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 7e5e0a5e89 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 2a7ac1baff 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards d0cbc59bed 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 68ce37e110 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards a66ac10da2 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 67f771cb61 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 05fa1e7b91 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards dbaf1f1f9b 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 7bd227bc02 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 335100e686 41: onsuccess: #514: 1: Success after linux: 64 commits discards 1d30943c80 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 1ea40eda8c 39: onsuccess: #511: 1: Success after binutils: 8 commits new 07ced14c28 39: onsuccess: #511: 1: Success after binutils: 8 commits new 74460a2bc8 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 5cee24afaa 41: onsuccess: #514: 1: Success after linux: 64 commits new b1118a35af 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new b74e2b4d29 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 914a66e468 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new f96668197e 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new ab05001a2c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new bb0cb3ac97 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 58179a531e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 6fabf3ff2f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 63d5093d86 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new efc425cb3d 51: onsuccess: #525: 1: Success after binutils: 8 commits new 60e4c1e421 52: onsuccess: #528: 1: Success after binutils: 8 commits new c2f217fe77 53: onsuccess: #531: 1: Success after binutils: 12 commits new 99c3b040dd 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 0700ba89ea 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new b65ab0794d 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new fadde7f745 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 4dd6ab476a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 8115194ad7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new e1ad8993f7 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new cab55208e7 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new a19f6f4219 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 545fd6fbe4 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4ccb4f1b85 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 572f51e24b 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 16947bf0bd 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a6f0b35c07 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7c54dd3876 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new d8362768b0 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 75b053a0e4 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 66f31eff9f 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new b8dc101b11 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new a1a5ed6442 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 376879dcca 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 13e36a69f8 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new f8713e08b8 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 179c1e29a8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new e5f9b8d99c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new b42a5c1a72 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 9d6ec45abc 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new e84b9985bf 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 240303f589 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 6bba09f2c5 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 2c5d3c16c6 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 0719b78095 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new e7b2747504 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new bd493ce41b 87: onsuccess: #567: 1: Success after binutils: 8 commits new a12caf9b75 88: onsuccess: #569: 1: Success after glibc: 10 commits new 74c30a12f2 89: onsuccess: #570: 1: Success after linux: 11 commits new d85715678f 90: onsuccess: #572: 1: Success after binutils: 15 commits new ca5b11bdc4 91: onsuccess: #574: 1: Success after glibc: 3 commits new 57676e2879 92: onsuccess: #575: 1: Success after linux: 34 commits new 109f82100e 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 9d443a59f3 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 415f76110f 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new d9a7cdfb1d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 12da62cce2 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 180e0a43d2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 7334b6fb74 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 9b62dde9fd 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new ce30dd3afa 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new fd9d62ab55 102: onsuccess: #586: 1: Success after binutils: 5 commits new 3ecdb4ff67 103: onsuccess: #589: 1: Success after binutils: 3 commits new c128f963f4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 6eee4c13a0 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new a9cf92b785 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 82788eb731 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new d52ffff3d5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new df4ba9d74a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 660b4c3bda 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new b55d473bd1 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new e5c16170ad 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new d3f490a261 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new ec96862620 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new c28fe39fdd 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 87c40f6912 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 326d6cc8cd 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 8d6b087070 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new f8dcc5f3b5 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 1aff725078 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 4bc0cb4a70 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new ed0793ad23 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new efae546c00 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new b754f2c3a2 124: onsuccess: #612: 1: Success after binutils: 18 commits new 6db50daede 125: onsuccess: #614: 1: Success after linux: 12 commits new 8683849655 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new c25d0ac5ea 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 7541c1b9b9 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 3ccade06f4 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 8f5fc2a16a 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 34c8ceb5ee 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 174dda1ac6 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new f5090a0990 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 710ae600a2 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 8c4a0a0ef2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 55823a796f 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new ee8ce1d2b4 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new a3d9c775f8 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new e05c535c74 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 0b42063425 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] 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 (dfbf7be137) \ 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 1792 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53736 -> 53648 bytes 04-build_abe-gcc/console.log.xz | Bin 238704 -> 234652 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 9504 bytes 07-build_abe-glibc/console.log.xz | Bin 238564 -> 238060 bytes 08-build_abe-gdb/console.log.xz | Bin 52160 -> 52480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2368 -> 2256 bytes 11-check_regression/console.log.xz | Bin 13152 -> 11308 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 58 +- 11-check_regression/mail-body.txt | 178 +- 11-check_regression/results.compare | 87 +- 11-check_regression/results.compare2 | 4735 ++++++++++---------- 11-check_regression/results.regressions | 87 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 180 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results | 87 +- sumfiles/gdb.log.xz | Bin 1835104 -> 1817952 bytes sumfiles/gdb.sum | 7243 +++++++++++-------------------- 30 files changed, 5191 insertions(+), 7579 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (47e8e05c2d -> 722ff72037)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 47e8e05c2d 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 0de957ec09 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 663c196e1f 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 7e2b43a1d7 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 9a8e41aa9d 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 9701ecabcf 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 8e7cff81c0 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 642f0a939c 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 6dbdcaf49b 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 791ef86aa9 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 108ce44e11 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards a95515913c 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 27304dd198 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 6bd5e0c096 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 3dcb2f6b62 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 5c6eb8deec 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 978b61d5bd 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards de086431d9 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards b4b96a16fb 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards c44e551000 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 5b6f7c8f9d 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 3cb6307ca1 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 525b3e52bc 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards 5db5c8583e 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 9cabb9b72a 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 19fff7c9cc 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards c1cef809d2 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 8818e3d9d7 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards 9587d4a991 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 0eb3ee78fb 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 6a741574ba 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 036ee05e6d 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 8882ea2dda 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards b01166b02a 229: force: #1926: 7: Success after gcc: 7 commits discards 7f1ddae4da 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards fd9a51eeaa 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards c58e609b6d 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards a2480e39dd 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 37b3914994 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 8b4ff36577 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards 538e9b818b 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards 668367ed50 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 5b68452ede 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards bcf6e1fffe 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards 2bcc9b67a8 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 357ad9b031 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards c5b21680a5 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 3228042efb 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards e12b46aad1 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards bd3b9d5806 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 8b39208c6a 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 2446b247a6 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 93cdb44b62 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 7a7f32be16 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 0b345528be 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 7aaa244256 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 0002e0547e 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards d55ee58b79 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 889831fd0d 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] discards 61a45ec82f 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits discards bbea795a0b 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 1cf0d8f77f 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] discards 3d634f5e29 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 077b7362df 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] discards dcf688d4a6 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards b409711334 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] discards 2f5110d8a4 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] discards f253c76c7e 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] discards 006b4550de 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] discards b72b5ca16f 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] discards ab7e4054dd 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] discards ef13ece73d 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] discards 177d864f00 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 364638e221 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards 2cde14f8b0 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards c7345a5401 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] discards 299bb860fa 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] discards 6c2bc5ac1b 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 7408f430e9 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] discards 9f75b8f3da 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] discards 3e165d8f69 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards 9bcec60ad9 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards c532bb873d 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards de8b7d7f6b 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 3ee0c70def 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards dfc2a2057e 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 4c77c62414 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards 6e5c1e433e 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards e9b9e306c6 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards a1fd522441 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 23f5e4c24d 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards b234c20b40 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards 742ba54055 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 4c24995cf7 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards c6ee243058 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards 8806d0cde7 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards 3835155e55 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 35dff778d7 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards b43846431d 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 982cd43ef9 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards e2c462b787 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new db8a00a3b3 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new 91e1eaaf0a 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new 5e614d873d 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new aaaa2d00a5 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new e2877ecc7b 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new fbf6cab42e 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new 6bbe7a11b0 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new bbd1f532ee 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new 858d7afed6 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 568f20f80d 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new ef1a389c07 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 773128fb6c 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 98ce502529 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new 2ceab64b30 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new 801cb566f7 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new 2bab0d8612 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 73ce90b42e 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new 31ebbafd1d 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 3e74ad0fe1 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new b0962c198d 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new 4b638581c7 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new cc6cf516a7 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] new 0f8410812c 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] new bf8d4c1e1c 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 604a88ef35 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] new a7b93eb8fd 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new 3fd157c3af 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new b9eedbef9a 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new 58bdfd8c81 190: onsuccess: #1774: 7: Success after binutils: 10 commits new d7c9aa4df8 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] new dc7923c983 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] new 671176bacd 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] new 3ba9d42c6c 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] new bfe2617473 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] new 218d5783d3 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] new 4ff616d6dd 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] new 5aa2bf6b8e 198: onsuccess: #1852: 7: Success after gcc: 5 commits new 1c85b428ee 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] new 8f25acf354 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 3bcebaeb4c 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] new 65e2a35de2 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 0a3593ed54 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits new 06e2dd5b5f 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new 39b1cc2699 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 812d27032f 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 72d97b1c9e 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 711dd1672e 208: onsuccess: #1865: 7: Success after linux: 12 commits new b6b96c8c6b 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new ca6642f8cf 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 64084ab5d8 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new d5aa225f66 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new f7430a3b2e 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 5604a1531e 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 542ba4a66a 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new d4cf891aa5 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new ca7c5b9de7 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 77dc2d7d23 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 41c0f1ae33 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 828604b9e8 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new 7b04652423 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 5c0c574f31 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 6ab88b4f08 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new edd2dad0ce 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new d4faf839bf 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new 9cdc236118 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 6e9ac14697 227: onsuccess: #1906: 7: Success after binutils: 9 commits new f54da51b88 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new cd50c16b5a 229: force: #1926: 7: Success after gcc: 7 commits new 131a686acf 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new efe09b9114 231: onsuccess: #1928: 3: Success after gcc: 8 commits new ddc0d14a51 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 27146b11e1 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new dc4671cb72 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new f563197331 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new bca883301d 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 3bac37da7a 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 20dde50d29 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 269a29bd56 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 2f6a9f2ac1 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new c8d516968a 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new f82e48193b 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new bb15285237 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new e81e095c99 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 609252d0f8 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new ffa88f638a 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 1c2d59bd3b 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new f19b274779 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 2f5579bc51 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 443c9f0a6c 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 12b6bfe902 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new d4266e9eb1 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 21999726d6 253: onsuccess: #1950: 7: Success after glibc: 2 commits new f21c9a0f2d 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new 64bd2c2a78 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 855b6cdc60 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 86aec07a16 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new e50db98cc5 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 8344a649f4 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 4711b30b59 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 571bb4089b 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new dedfc77218 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 722ff72037 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (47e8e05c2d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1804 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2784 bytes 04-build_abe-binutils/console.log.xz | Bin 32404 -> 32408 bytes 05-build_abe-stage1/console.log.xz | Bin 74316 -> 73960 bytes 07-build_abe-linux/console.log.xz | Bin 8576 -> 9528 bytes 08-build_abe-glibc/console.log.xz | Bin 246136 -> 246924 bytes 09-build_abe-stage2/console.log.xz | Bin 206288 -> 205384 bytes 10-build_abe-gdb/console.log.xz | Bin 39552 -> 39640 bytes 11-build_abe-qemu/console.log.xz | Bin 31452 -> 31768 bytes 12-check_regression/console.log.xz | Bin 4564 -> 4920 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 ++++++++++++------------ 22 files changed, 66 insertions(+), 66 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (e5ac4d37e0 -> 9b97e6fafb)

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_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards e5ac4d37e0 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits discards 1c64ce1b1b 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits discards dc2e91f5bb 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits discards 6cbbca702d 441: onsuccess: #2403: 1: Success after gcc: 3 commits discards 5acda46d13 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits discards 85f859797b 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits discards d4789aba8d 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits discards e3fe8493cf 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits discards ef8c30ced1 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits discards 9b024aaa62 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] discards 572a6d13af 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits discards 7ecbc33fac 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits discards e9b7c4d4e4 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits discards 53b3728af5 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits discards 73920d92b8 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] discards 640c626ae7 429: onsuccess: #2391: 1: Success after binutils: 3 commits discards 9e2a2be9b1 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits discards fe296ecbc0 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits discards 76d5ce0978 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits discards 8daffa200c 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards 31d0331f37 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards 86b1a9be41 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards be4f0c6060 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards 5763f70af9 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards 54c135137f 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards 8bd9507af2 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards 2c0bbbbb09 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards ae1509e655 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards 72abb266d4 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 5fc5582b2f 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards 3e0b63aaab 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards 2540f8c3c1 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards a4e754192d 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards c60fcffbbd 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards df64a5f745 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards a446cb91c7 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards bff11036e9 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] discards 429417f07d 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 0c6ea568ed 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards 18a31ca15d 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] discards da063cc88a 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] discards e9735fe44f 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards 382f135dfc 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards afc8618548 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] discards 5ad78652e0 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 653b2b295b 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards 0c94751bcb 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards bbb80ed337 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards e50f376aa7 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards 192eb0cd5f 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 020173ad80 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards e2333b45eb 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards e89fbbb989 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 4c7ece90df 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards 745c633eb7 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 59cbdc6c45 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards b0dd090ef4 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 7431a5d743 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards ff451cc272 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards a6ebda29ad 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 486fe5eb13 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 40420f8b69 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 398bb1f13b 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards 31d4ad51bc 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards de6a17f9d7 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards d49740a692 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] discards 1836a575c3 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards f6a29d4fa1 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 8806694b3d 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 174d42d96a 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 9cd45065dd 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 39b7faec8e 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 46c5eb0b05 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards fd14114b5a 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards c998dfde37 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards b3931d9a57 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards cb7f6378f1 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards b35834185a 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards e67eb03906 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 48dc8166d8 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards ca392331ae 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 90dcb5dbca 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards a7725450cc 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 660437b5c3 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 1646b5b161 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards 93c2895235 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] discards 909e71026c 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 37a8173439 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards d5410cc657 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards eef40b34e8 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 38de39aa1c 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards b943cb37cb 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards bbcb9fe3f0 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards b502f9b753 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 7e64b34087 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards b7dd37e3fa 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 582f3ca80a 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 757fbb9c3d 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards fd57aa2a72 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 45128a4f38 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 122099efcd 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new a166286e0d 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 497e245b90 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new fba71fb3dd 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 9ffa7a15f2 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 757e296f9f 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 3ca3efc124 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new d1d55ca344 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 83c6f2548b 351: onsuccess: #2307: 1: Success after binutils: 2 commits new a5657db5cd 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 363d277539 353: onsuccess: #2309: 1: Success after gcc: 7 commits new ce8c6e015e 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 3f6c18db32 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 1c7d3a0578 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 38959b4c98 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 1845e6cd7a 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 964f88e97b 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] new d0c409212f 360: onsuccess: #2317: 1: Success after binutils: 4 commits new be1579f4b5 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 2153af09eb 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 91b6eb6ee8 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 87baef3839 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new edbd0992c2 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new bd496a3343 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 1ca26fd43c 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 8d96625eae 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 9cb7e02096 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new e0f8841690 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new e4cecef08b 371: onsuccess: #2333: 1: Success after binutils: 5 commits new de768a145d 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 3f526f6ab4 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new c66e4d4764 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 7b61c42bce 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 8c4621b783 376: onsuccess: #2338: 1: Success after gcc: 2 commits new b900d5b665 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new eb0bb2abd2 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 9977dba489 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] new 7d7c9cd1c2 380: onsuccess: #2342: 1: Success after gcc: 3 commits new 5b3f3c2c56 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 8108261453 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new 60262a9f16 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 9fc5816f83 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new 712e9e744a 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new c7e6c7a446 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new c64c38afa7 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new acea244fb7 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 7bd868aac1 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new 5e0e3478a2 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 003845177a 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new b4daa4d467 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 166d849eab 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new fc459611e1 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 485002a019 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new e5c00ad23f 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new 48fb05b2fe 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new fccd001c48 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new 5bbc9fdfca 399: onsuccess: #2361: 1: Success after gcc: 10 commits new f6bc8d5e5e 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new 5a5203fc8e 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] new 8df93814bc 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new d3c1839fca 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 581ceb5c94 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] new fb916a8dc4 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] new ad2e90d672 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new c1f5064af5 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new 36e3141b59 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] new df6776d050 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new 33b2a3abfd 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new d46f7f0e67 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new 42e955fc5a 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new b03fe7ee74 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new 079c9f229d 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new f3fc99db89 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new 3362afd629 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new efcbcfa88b 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 94007d0704 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new 3f593e20aa 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new 1f937acc42 420: onsuccess: #2382: 1: Success after gcc: 2 commits new ab4dfa5832 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new c44a4b7d2c 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new 05f10649b7 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new 50b6bc7405 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new 7c7a4b80c7 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new bffad8a64c 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits new 7fe6e3eb2a 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits new ae96de8c04 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits new e8da15a805 429: onsuccess: #2391: 1: Success after binutils: 3 commits new 988a804879 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] new 1505eef382 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits new b6bed117e6 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits new ef2059afa7 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits new 779ba0714f 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits new b13d19b591 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] new f16b52c4a8 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits new 732bffe622 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits new c9b1485cea 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits new 24ffdf12d1 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits new f1c6fcd1db 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits new 78dccf107a 441: onsuccess: #2403: 1: Success after gcc: 3 commits new 0911948aad 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits new 334d73bb61 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits new e3adc0a7fc 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits new 9b97e6fafb 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e5ac4d37e0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1732 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39488 -> 41156 bytes 04-build_abe-gcc/console.log.xz | Bin 215116 -> 216512 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3864 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2456 -> 2844 bytes 07-check_regression/console.log.xz | Bin 5048 -> 4648 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 19 +- 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3630000 -> 3605616 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3161684 -> 3158644 bytes sumfiles/gcc.sum | 4774 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1044788 -> 1047308 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2196 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219624 -> 219536 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457172 -> 455236 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2546 insertions(+), 2555 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allyesconfig updated (45d7a3f477 -> cc014342d6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 45d7a3f477 36: onsuccess: #411: all: Success after binutils/gcc/linux/q [...] new cc014342d6 37: onsuccess: #412: all: Success after binutils/gcc/linux/q [...] 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 1752 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 29944 -> 30072 bytes 04-build_abe-stage1/console.log.xz | Bin 86400 -> 87012 bytes 05-build_abe-qemu/console.log.xz | Bin 29988 -> 31516 bytes 06-build_linux/console.log.xz | Bin 3516 -> 3460 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4196 -> 4260 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (4852c0a0fb -> e8f81d1be0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 4852c0a0fb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 87ef2232e2 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards f371bb21ef 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 57777092c2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 5fb6a420fa 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 0b4f273127 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 5e1abaed8d 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards e8fe6b5d5e 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 67c3444a38 128: onsuccess: #876: 1: Success after binutils: 12 commits discards c8bc9aece5 127: onsuccess: #874: 1: Success after linux: 219 commits discards 4e9a0b5840 126: onsuccess: #873: 1: Success after glibc: 2 commits discards dbb15ba38b 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 8a4f559ceb 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards a82635fc5a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 85faa99a8a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards e185a41fe1 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 5241daf318 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 6a1d95fef5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards d087899ee4 118: onsuccess: #863: 1: Success after linux: 12 commits discards 2a0ed6604d 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 0483d68c65 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 113421da88 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 12ea372f7a 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 646ffb5450 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards d94259804d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 22351ffce7 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 80a464e9e6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards ab33270e1d 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards c5024ed3bc 108: onsuccess: #850: 1: Success after gcc: 2 commits discards af3dd8c212 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 8d76471cb6 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 4d76732893 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards eebc045425 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3cff428d6f 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards b3d01322b9 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 685365b17a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 2239cdff72 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards b1af2a728b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 0aaba906f3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 210b79e6bf 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 6cb131b129 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 0c0d83c957 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 2295a145e0 94: onsuccess: #832: 1: Success after binutils: 5 commits discards d1fd89573a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 6f371a0b3a 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards c0aaa7acb9 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards a56bd16b05 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 0b9ed8be8c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards e60a258ee3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 009f0b5bc5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 4c024cf639 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 1329f0df90 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards deb692688b 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards c8761d894b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards cbc695fb94 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards ff39528a46 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 9f44a2f7d1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards cca953d51a 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 06d39d87a1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d95533b0d8 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards f4f14675ba 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards c36f9d3fa1 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 80e13d6ae4 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards a6ccff0629 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 53a1712eb7 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 0ae719379a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 81afde358b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards bd02c699c2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards a9a41b5c1d 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 49db19ae1f 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards e204d8950f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards a0994fdd01 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards ea737a72bf 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 5cc028fc8c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 4e010a4c83 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 8f03bff3cd 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 6e91c01e67 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards ae39eb0745 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards c68f5c3ae6 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards aa4891fbab 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards db3c0d2d88 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards ee0e25efea 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 4ddb3725d2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 892eb16b8a 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 7f49cc1f8b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 23195152e8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards b8edd3a008 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards cdabf65332 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f15b0ddf49 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 2adac321a2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 86bcea1139 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 402fb35817 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 08c116273c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 0a9686de4b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 4ba75cecb4 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards ba5420889b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards bdc9fb4a3b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 409ff4e360 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 6a5db62df2 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards fb7ba70905 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 6c3dceee51 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new b2a82d7274 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 450c0edf51 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new fc018158a1 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new f5f059dee8 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 5a91d81e1a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new faf2445595 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 63a60e6ed4 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new b0990e1abd 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 66dce90bb2 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 0887c154dd 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 2c64400b8c 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new b533b2be25 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 46d42b2513 48: onsuccess: #782: 1: Success after binutils: 8 commits new e8a45235f0 49: onsuccess: #785: 1: Success after binutils: 12 commits new cc6ff012bc 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new cc4cc49f26 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 2383615453 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 339aad0822 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 7fa13394a6 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 26960cb92d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new d04ea1e255 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 7d5be59612 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new f736cc80db 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 786419d3ac 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a457d7dbc8 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 4c5ffde082 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 1c1ffc22f3 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 451843154e 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 4d20edf71a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 0278e06534 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 3316118a4e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8cf165e250 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 6d687b82a7 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 294a657991 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new cda0113100 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 44850dc4b6 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 95ae947f3a 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 6a169c8618 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 81a835c689 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1e42061b4c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new e58861795e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 742652f122 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new afee2272fb 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 0da3c41c29 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 9f188602d7 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 30a50e1a23 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 2b683515a1 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 7b76bc79b1 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new d631c0c4f3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 93c7aa3ae4 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new cba6617eca 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new c49c493174 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new b9e3671c17 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 09b90998d6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0d871eccdf 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 4d223d14b0 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5910570b0a 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e68cc41584 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 466fe9801f 94: onsuccess: #832: 1: Success after binutils: 5 commits new dd42f30a73 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7f966a39ad 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 038edeaa4d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new fae9eacb89 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new f8ac6b7589 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 5ed5d7c9cf 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new adf103462d 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new bc3640df7d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 33704110f7 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 158b403fcf 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new ed1646d920 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 348e0ef1c8 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new ee121f1c9b 107: onsuccess: #849: 1: Success after binutils: 5 commits new eb494cc0a8 108: onsuccess: #850: 1: Success after gcc: 2 commits new 1e4f2c2d55 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 96a3222275 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 37712a1878 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 81fd4ab698 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new e52d0520dc 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new b1fbd2520c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new cc0f7288f6 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new f90094b130 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 7f2ea69e41 117: onsuccess: #861: 1: Success after binutils: 18 commits new 9a249217a7 118: onsuccess: #863: 1: Success after linux: 12 commits new 3300d4ebb5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 94408cd458 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 0fedcfa10f 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 5ee57618bb 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new b60ed21bf4 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new c8cc98f1ca 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new ce5cc9ad37 125: onsuccess: #871: 1: Success after binutils: 26 commits new b9af00c977 126: onsuccess: #873: 1: Success after glibc: 2 commits new c8b025f052 127: onsuccess: #874: 1: Success after linux: 219 commits new 844f0d5810 128: onsuccess: #876: 1: Success after binutils: 12 commits new 2d904f38c1 129: onsuccess: #878: 1: Success after linux: 3008 commits new a2f16b3463 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new eece69599b 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 75d047485a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 91c6e95618 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new e14266a229 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 48924a518c 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 628ac87973 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new e8f81d1be0 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] 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 (4852c0a0fb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1768 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39872 -> 39936 bytes 04-build_abe-gcc/console.log.xz | Bin 215640 -> 215660 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8828 bytes 07-build_abe-glibc/console.log.xz | Bin 245640 -> 245476 bytes 08-build_abe-gdb/console.log.xz | Bin 39428 -> 39272 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3288 -> 2904 bytes 11-check_regression/console.log.xz | Bin 6788 -> 7200 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 10 +- 11-check_regression/results.compare2 | 142 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 62 +- 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/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 + sumfiles/g++.log.xz | Bin 3761124 -> 3741064 bytes sumfiles/g++.sum | 83 +- sumfiles/gcc.log.xz | Bin 3311640 -> 3322332 bytes sumfiles/gcc.sum | 4732 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1078032 -> 1083348 bytes sumfiles/gfortran.sum | 64 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233408 -> 233248 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 450176 -> 453984 bytes sumfiles/libstdc++.sum | 4 +- 42 files changed, 2741 insertions(+), 2536 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O2 updated (e1d854f4f4 -> 04387bde25)

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_llvm_fx/llvm-master-aarch64-cpu2017rate-O2 in repository toolchain/ci/base-artifacts. from e1d854f4f4 27: force: #159: 1: [TCWG CI] 557.xz_r slowed down by 7% aft [...] new 04387bde25 28: force: #160: 1: [TCWG CI] 557.xz_r speeds up by -5% afte [...] 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 1872 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32428 -> 32200 bytes 04-build_abe-stage1/console.log.xz | Bin 73840 -> 74268 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8008 -> 8004 bytes 07-build_abe-glibc/console.log.xz | Bin 245440 -> 245416 bytes 08-build_abe-stage2/console.log.xz | Bin 179348 -> 180444 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 62832 -> 60904 bytes 10-benchmark/benchmark-build.log | 84 +- 10-benchmark/benchmark.log | 82 +- 10-benchmark/console.log.xz | Bin 3972 -> 3980 bytes 11-check_regression/console.log.xz | Bin 11572 -> 11156 bytes .../csv-results-vs-first-1/md5sum.csv | 1062 ++-- .../csv-results-vs-first-1/perf.csv | 1989 ++++--- .../csv-results-vs-first-1/results.csv | 6185 +++++++++++++------- .../csv-results-vs-first-1/size.csv | 4009 ++++++++++--- .../csv-results-vs-prev-0/md5sum.csv | 1087 ++-- 11-check_regression/csv-results-vs-prev-0/perf.csv | 1959 ++++--- .../csv-results-vs-prev-0/results.csv | 2130 ++++--- .../csv-results-vs-prev-1/md5sum.csv | 1062 ++-- 11-check_regression/csv-results-vs-prev-1/perf.csv | 1989 ++++--- .../csv-results-vs-prev-1/results.csv | 6185 +++++++++++++------- 11-check_regression/csv-results-vs-prev-1/size.csv | 4009 ++++++++++--- 11-check_regression/exe.improvement | 1 + 11-check_regression/exe.regression | 1 - 11-check_regression/jira-body.txt | 4 +- 11-check_regression/mail-body.txt | 4 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-vs-first-brief.csv | 42 +- 11-check_regression/results-vs-first-full.csv | 1995 ++++--- 11-check_regression/results-vs-first-internal.csv | 139 +- 11-check_regression/results-vs-first.csv | 139 +- 11-check_regression/results-vs-first.log | 634 +- 11-check_regression/results-vs-prev-brief.csv | 42 +- 11-check_regression/results-vs-prev-compare.csv | 11 +- 11-check_regression/results-vs-prev-full.csv | 2103 ++++--- 11-check_regression/results-vs-prev-internal.csv | 139 +- 11-check_regression/results-vs-prev.csv | 139 +- 11-check_regression/results-vs-prev.log | 746 +-- 11-check_regression/results.regressions | 5 - 11-check_regression/skipped-symbols.txt | 8 +- 11-check_regression/trigger-bisect | 3 - dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../508.namd_r/results-metadata.json | 10 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 10 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../squad-vs-first/525.x264_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 74 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 15 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 5 - results_id | 2 +- 76 files changed, 23360 insertions(+), 14942 deletions(-) create mode 100644 11-check_regression/exe.improvement delete mode 100644 11-check_regression/exe.regression delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[linux] branch master updated (d264dd3bbbd1 -> 0a924817d2ed)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from d264dd3bbbd1 Merge tag 'for-linus-2022122101' of git://git.kernel.org/p [...] new 11933cf1d91d pnode: terminate at peers of source new 04065c12072b Merge tag 'fs.mount.propagation.fix.v6.2-rc1' of git://git [...] new bd6ae049b7be fs/ntfs3: Add comments about cluster size new 098250db5dfc fs/ntfs3: Add hidedotfiles option new ae6b47b5653e fs/ntfs3: Change destroy_inode to free_inode new a3a956c78efa fs/ntfs3: Add option "nocase" new 43f03acbc1ec fs/ntfs3: Rename variables and add comment new 0b6604626669 fs/ntfs3: Validate BOOT record_size new e19c6277652e fs/ntfs3: Add overflow check for attribute size new 6db620863f85 fs/ntfs3: Validate data run offset new 2681631c2973 fs/ntfs3: Add null pointer check to attr_load_runs_vcn new f27b92ec0926 fs/ntfs3: Fix [df]mask display in /proc/mounts new 6d5c9e79b726 fs/ntfs3: Fix attr_punch_hole() null pointer derenference new 92f017c4aee6 fs/ntfs3: Use kmalloc_array for allocating multiple elements new 51e76a232f8c fs/ntfs3: Fix memory leak on ntfs_fill_super() error path new caad9dd8792a fs/ntfs3: Avoid UBSAN error on true_sectors_per_clst() new 0a4e7ce6bc03 fs/ntfs3: Fix junction point resolution new c1ca8ef0262b fs/ntfs3: Add null pointer check for inode operations new 4f1dc7d9756e fs/ntfs3: Validate attribute name offset new e001e6086939 fs/ntfs3: Harden against integer overflows new 4d42ecda239c fs/ntfs3: Validate buffer length while parsing index new 54e45702b648 fs/ntfs3: Validate resident attribute name new 887bfc546097 fs/ntfs3: Fix slab-out-of-bounds read in run_unpack new d45da67caeda fs/ntfs3: Use strcmp to determine attribute type new 0d6d7c61ffee fs/ntfs3: Don't use uni1 uninitialized in ntfs_d_compare() new bfcdbae0523b fs/ntfs3: Validate index root when initialize NTFS security new 557d19675a47 fs/ntfs3: Fix slab-out-of-bounds read in ntfs_trim_fs new 0d0f659bf713 fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() new 59bfd7a483da fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() new 019d22eb0eb7 fs/ntfs3: Validate attribute data and valid sizes new 75b5e4720132 fs/ntfs3: Eliminate unnecessary ternary operator in ntfs_d [...] new 1d07a9dfa199 fs/ntfs3: Add windows_names mount option new d683c67c5f50 fs/ntfs3: Document windows_names mount option new 4c9ba192c73f fs/ntfs3: Fix hidedotfiles mount option by reversing behaviour new 66223324cba4 fs/ntfs3: Make hidedotfiles mount option work when renaming files new 19b424501d85 fs/ntfs3: Add hidedotfiles to the list of enabled mount options new 60adc860ca7d fs/ntfs3: Document the hidedotfiles mount option new dc0fcc99b175 fs/ntfs3: Rename hidedotfiles mount option to hide_dot_files new 0d19f3d71394 fs/ntfs3: Add system.ntfs_attrib_be extended attribute new d49436c34448 fs/ntfs3: Document system.ntfs_attrib_be extended attribute new 658015167a84 fs/ntfs3: Delete duplicate condition in ntfs_read_mft() new ecfbd57cf9c5 fs/ntfs3: Fix slab-out-of-bounds in r_page new 90c1cd540cc8 fs/ntfs3: Fix endian conversion in ni_fname_name new 88a8d0d2482f fs/ntfs3: Add functions to modify LE bitmaps new 095d8ce635c1 fs/ntfs3: Use _le variants of bitops functions new 08811ba59a61 fs/ntfs3: Add ntfs_bitmap_weight_le function and refactoring new 9144b4382061 fs/ntfs3: Fix sparse problems new 3929042111de fs/ntfs3: Remove unused functions new ba1189288905 fs/ntfs3: Simplify ntfs_update_mftmirr function new 2f56a3f8d824 fs/ntfs3: Fixing work with sparse clusters new c380b52f6c57 fs/ntfs3: Change new sparse cluster processing new 07f4aa9dd245 fs/ntfs3: Fix wrong indentations new 2b108260ea2c fs/ntfs3: atomic_open implementation new ad26a9c84510 fs/ntfs3: Fixing wrong logic in attr_set_size and ntfs_fallocate new 0ad9dfcb8d3f fs/ntfs3: Changing locking in ntfs_rename new 910013f7c7ba fs/ntfs3: Restore correct state after ENOSPC in attr_data_ [...] new 6f80ed14d76c fs/ntfs3: Correct ntfs_check_for_free_space new 0e8235d28f3a fs/ntfs3: Check fields while reading new e31195a3ac71 fs/ntfs3: Fix incorrect if in ntfs_set_acl_ex new 97a6815e5061 fs/ntfs3: Use ALIGN kernel macro new 60ce8dfde035 fs/ntfs3: Fix wrong if in hdr_first_de new ec5fc7201376 fs/ntfs3: Improve checking of bad clusters new 36963cf225f8 fs/ntfs3: Make if more readable new 6022ec6ee2c3 Merge tag 'ntfs3_for_6.2' of https://github.com/Paragon-So [...] new b248586a49a7 cifs: set correct tcon status after initial tree connect new 86fe0fa8747f cifs: set correct ipc status after initial tree connect new c877ce47e137 cifs: reduce roundtrips on create/qinfo requests new 9fd29a5bae6e cifs: use fs_context for automounts new abdb1742a312 cifs: get rid of mount options string parsing new 2301bc103ac4 cifs: remove unused smb3_fs_context::mount_options new 6d740164d890 cifs: set resolved ip in sockaddr new a73a26d97eca cifs: split out ses and tcon retrieval from mount_get_conns() new a1c0d00572fc cifs: share dfs connections and supers new cb3f6d876452 cifs: don't refresh cached referrals from unactive mounts new 6916881f443f cifs: fix refresh of cached referrals new 8332858569a0 cifs: refresh root referrals new 1d04a6fe75ee cifs: don't block in dfs_cache_noreq_update_tgthint() new a85ceafd4192 cifs: fix confusing debug message new 466611e4af82 cifs: fix source pathname comparison of dfs supers new 6fbdd5ab2404 cifs: optimize reconnect of nested links new 25cf01b7c920 cifs: set correct status of tcon ipc when reconnecting new 7ad54b98fc1f cifs: use origin fullpath for automounts new f60ffa662d14 cifs: don't leak -ENOMEM in smb2_open_file() new aacfc939cc42 cifs: update internal module number new 0a924817d2ed Merge tag '6.2-rc-smb3-client-fixes-part2' of git://git.sa [...] The 85 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: Documentation/filesystems/ntfs3.rst | 19 + fs/cifs/Makefile | 2 +- fs/cifs/cifs_debug.c | 8 + fs/cifs/cifs_dfs_ref.c | 255 +++------- fs/cifs/cifsfs.c | 6 - fs/cifs/cifsfs.h | 4 +- fs/cifs/cifsglob.h | 18 +- fs/cifs/cifsproto.h | 14 +- fs/cifs/connect.c | 899 ++++++------------------------------ fs/cifs/dfs.c | 544 ++++++++++++++++++++++ fs/cifs/dfs.h | 46 ++ fs/cifs/dfs_cache.c | 276 ++--------- fs/cifs/dfs_cache.h | 2 +- fs/cifs/dir.c | 21 +- fs/cifs/dns_resolve.c | 49 +- fs/cifs/dns_resolve.h | 4 +- fs/cifs/fs_context.c | 13 +- fs/cifs/fs_context.h | 3 +- fs/cifs/inode.c | 6 - fs/cifs/misc.c | 81 +--- fs/cifs/smb2file.c | 4 +- fs/cifs/smb2inode.c | 46 +- fs/cifs/smb2ops.c | 28 +- fs/ntfs3/attrib.c | 392 ++++++++++------ fs/ntfs3/attrlist.c | 5 + fs/ntfs3/bitfunc.c | 4 +- fs/ntfs3/bitmap.c | 168 +++++-- fs/ntfs3/dir.c | 4 +- fs/ntfs3/file.c | 203 +++----- fs/ntfs3/frecord.c | 40 +- fs/ntfs3/fslog.c | 62 +-- fs/ntfs3/fsntfs.c | 190 ++++++-- fs/ntfs3/index.c | 127 ++++- fs/ntfs3/inode.c | 203 ++++++-- fs/ntfs3/namei.c | 238 ++++++++++ fs/ntfs3/ntfs.h | 6 +- fs/ntfs3/ntfs_fs.h | 41 +- fs/ntfs3/record.c | 13 + fs/ntfs3/run.c | 28 +- fs/ntfs3/super.c | 143 ++++-- fs/ntfs3/upcase.c | 12 + fs/ntfs3/xattr.c | 158 ++++--- fs/pnode.c | 2 +- 43 files changed, 2422 insertions(+), 1965 deletions(-) create mode 100644 fs/cifs/dfs.c create mode 100644 fs/cifs/dfs.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (e54af2116f -> 78727ab147)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from e54af2116f 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 78727ab147 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] 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 1744 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39788 -> 39764 bytes 04-build_abe-gcc/console.log.xz | Bin 215672 -> 216220 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 9056 bytes 07-build_abe-glibc/console.log.xz | Bin 246760 -> 246596 bytes 08-build_abe-gdb/console.log.xz | Bin 40712 -> 39856 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3960 -> 3860 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2780 -> 2620 bytes 11-check_regression/console.log.xz | Bin 6248 -> 6036 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 9 +++++++++ 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14612 -> 14636 bytes sumfiles/gdb.sum | 34 ++++++++++++++++---------------- 26 files changed, 58 insertions(+), 49 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (91e0d22025e -> 193fccaa5c3)

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 91e0d22025e [PATCH] Use toplevel configure for GMP and MPFR for gdb new 193fccaa5c3 Fix PR 105532: match.pd patterns calling tree_nonzero_bits [...] 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/match.pd | 25 ++++++++++++---------- .../gcc.c-torture/compile/vector-shift-1.c | 8 +++++++ 2 files changed, 22 insertions(+), 11 deletions(-) create mode 100644 gcc/testsuite/gcc.c-torture/compile/vector-shift-1.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig updated (e998cd8e52 -> f663f1b3e2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from e998cd8e52 38: onsuccess: #449: boot: Success after binutils/gcc/linux/ [...] new f663f1b3e2 39: onsuccess: #450: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1780 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30308 -> 30208 bytes 04-build_abe-stage1/console.log.xz | Bin 86864 -> 86992 bytes 05-build_abe-qemu/console.log.xz | Bin 31192 -> 31048 bytes 06-build_linux/console.log.xz | Bin 3308 -> 3312 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 4076 -> 4152 bytes 08-check_regression/mail-body.txt | 8 ++++++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 10 +++++++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 19 files changed, 36 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022