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 (ec8cd9c632 -> c6abf6c266)

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 ec8cd9c632 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards edd09ab43e 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards d3e73193f3 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 86e9cedf10 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 0dc027d853 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 7606adcb0d 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 2b08340c41 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards a3aa3c7af1 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards c5b49f3c73 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards a1cf15def4 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards bf058c8148 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 39375e3a8c 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 6d297d0eed 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards d3db6a0728 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards d8631d767e 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 2ba1b6c64e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8e6d3ce47f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards f50a8fae99 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards d63be7a0e5 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards f90a78763d 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 544466cd16 125: onsuccess: #614: 1: Success after linux: 12 commits discards 55c76e7e84 124: onsuccess: #612: 1: Success after binutils: 18 commits discards e3e457be33 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 761bf25890 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 58bb5b4b77 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards c8e309f216 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 65ff99af5c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 463605c7fd 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards bdfb28932c 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 41ffa61159 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards cda98befb6 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards fc34e4b4c4 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards aa5e9072cd 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 69ba8dc1ac 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards e2728ff33e 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 692697352d 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards bf1be2d546 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards f3169b1d16 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 610e2b9cf5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards fe5d644230 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards b67aee3144 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 91f5195b8d 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 87ff5faa5d 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 14c6ac0b47 102: onsuccess: #586: 1: Success after binutils: 5 commits discards eccae70401 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards cfaa0d9e64 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 0ce4d66332 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 8d6fe001a8 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards b2906bd2fd 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 8ea0c85717 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 7825ff1aba 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards e9d97f2a6b 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 12e1f0bf4f 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 4462f04682 92: onsuccess: #575: 1: Success after linux: 34 commits discards cca9dc2cb0 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 7abf2ca458 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 88069a937c 89: onsuccess: #570: 1: Success after linux: 11 commits discards fb8f2c04b6 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 1ad55f674a 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 5b467b1516 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 41d2c49628 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 300de68f1d 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards e799121468 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 5d9ba0d483 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards ed479a2f8c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 1f7ed8abe8 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 5bdbe237f8 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 374e92dbf1 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 654e1422fb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards fce752ae70 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards d596f99d42 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 3a52beac07 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards bb53f493e9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards e1f9ffa070 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 8547d56215 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards fd8211d448 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards f03e9641ed 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 0f030a1a91 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 289588318f 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 7dcd17b293 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards c33383e7e0 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 812b644d61 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards a1d8a02715 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards e86a96b21d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 96799c1a65 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 997e4ac187 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 8f9de2e6a5 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards d354fcc8db 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards a89968c721 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards cd3bbb0c93 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards b9c685b473 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 6249aa1387 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 9bbee2f662 53: onsuccess: #531: 1: Success after binutils: 12 commits discards ea46b9844d 52: onsuccess: #528: 1: Success after binutils: 8 commits discards b178b5aa37 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 95ce4fed05 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 963cbfaa0c 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 82a7c5d23f 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 87b48724d1 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 549ca84f76 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 33c19fb820 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 1c141f1292 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new eb974bb457 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 4a044fb10a 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new d235f318f5 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new a5b9132f92 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new c80434266c 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new c0079cb50f 51: onsuccess: #525: 1: Success after binutils: 8 commits new ac1ba41ba9 52: onsuccess: #528: 1: Success after binutils: 8 commits new d787f4eb18 53: onsuccess: #531: 1: Success after binutils: 12 commits new 9773b283f5 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new cf42ee7d3d 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 65ee98a3b7 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new c31d893b68 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 8f7247ed91 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 314946352e 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 5f0bfb5525 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 9bfff317e1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new fa41ef7242 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 6d9d81515b 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 1a2fe89874 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new e31a7d0bfb 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 2df0ace345 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e826ddd534 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new cbdad71f5b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 07df97eacf 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new bf53b2aca3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new e3083630d8 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new e16c011253 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new d689466501 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new b7a372a88c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 83023d8949 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new c48bc42638 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new b18057a710 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 8ce0cd4648 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new f3b49466a8 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new ce9c0ef526 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 4e425436b9 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 4a148b9a58 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 12b645fd7d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 8f3f1d19af 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 2d5750e04d 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new ec42947866 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 98c5545531 87: onsuccess: #567: 1: Success after binutils: 8 commits new c70fde1f75 88: onsuccess: #569: 1: Success after glibc: 10 commits new f66fa4f117 89: onsuccess: #570: 1: Success after linux: 11 commits new 6dba5ee925 90: onsuccess: #572: 1: Success after binutils: 15 commits new ced177c903 91: onsuccess: #574: 1: Success after glibc: 3 commits new 2a9f19ef3f 92: onsuccess: #575: 1: Success after linux: 34 commits new 0264229704 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 9c366c5012 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new b19080e64e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new a0417ccdf9 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 31dc1d7cbe 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new d467cbec40 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 91c5c27602 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 0281bc4b20 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new fa920464e8 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 081841d8be 102: onsuccess: #586: 1: Success after binutils: 5 commits new fbb8ff016c 103: onsuccess: #589: 1: Success after binutils: 3 commits new d5ba2eb99e 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 6e1040fadd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 046f9dec3a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new fd9d046e84 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 6ed155ce11 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 9a7bb00944 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 1931dbd71f 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 96f189219e 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new eb64b29da1 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 2fce7f0213 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 128f18a6ac 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 2a8e155eb0 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 88180832da 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 775a86a7d8 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 637454b2a6 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new de3c1803a3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 767f5357f7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 485fe4c56a 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 9fba1237f6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 30d47d082a 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 3859f6706c 124: onsuccess: #612: 1: Success after binutils: 18 commits new 5dbbd6a62d 125: onsuccess: #614: 1: Success after linux: 12 commits new 956d67fd49 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new bfff75fe82 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 736871257c 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new a3343d1b40 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new bc5c60f363 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new e13ecde9dd 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 517b6a2c83 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 6c58b29ded 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 533243d186 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new f521e59c9d 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new b35ce9c0e4 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new cc736445c5 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 6bc46cc92b 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new d1d4b9010d 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 7e275296c9 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new e583aec302 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 077dd52ca3 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 79c3fd2088 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 50d712d1e5 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 8a9aa90151 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new c6abf6c266 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 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 (ec8cd9c632) \ 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 1736 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 54388 -> 54128 bytes 04-build_abe-gcc/console.log.xz | Bin 243120 -> 240808 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8436 -> 8332 bytes 07-build_abe-glibc/console.log.xz | Bin 238588 -> 236608 bytes 08-build_abe-gdb/console.log.xz | Bin 52652 -> 51656 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2460 -> 2428 bytes 11-check_regression/console.log.xz | Bin 9992 -> 11112 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 43 +- 11-check_regression/mail-body.txt | 189 +- 11-check_regression/results.compare | 93 +- 11-check_regression/results.compare2 | 1797 ++++++-- 11-check_regression/results.regressions | 93 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 191 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 93 +- sumfiles/gdb.log.xz | Bin 1698740 -> 1716312 bytes sumfiles/gdb.sum | 6873 ++++++++++++++++++------------- 29 files changed, 5760 insertions(+), 3694 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/llvm-release-aarch64-stable-defconfig updated (b5f3beaeba -> 40826cca81)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from b5f3beaeba 30: onsuccess: #283: boot: Success after binutils/linux/qemu [...] new 40826cca81 31: onsuccess: #284: boot: Success after binutils: 4 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30536 -> 30396 bytes 04-build_kernel_llvm/console.log.xz | Bin 64992 -> 65212 bytes 05-build_abe-qemu/console.log.xz | Bin 31608 -> 31792 bytes 06-build_linux/console.log.xz | Bin 3400 -> 3408 bytes 07-boot_linux/console.log.xz | Bin 6228 -> 6256 bytes 08-check_regression/console.log.xz | Bin 3624 -> 2900 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 14 files changed, 15 insertions(+), 15 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_fast_check_gdb/master-aarch64 updated (74d1735455 -> 5dcd6eda9f)

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 74d1735455 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 5dcd6eda9f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1728 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39824 -> 40020 bytes 04-build_abe-gcc/console.log.xz | Bin 215868 -> 214588 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 244804 -> 246800 bytes 08-build_abe-gdb/console.log.xz | Bin 39524 -> 40448 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3876 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2804 -> 2864 bytes 11-check_regression/console.log.xz | Bin 5348 -> 5272 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14612 -> 14616 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 52 insertions(+), 43 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-aarch64-stable-defconfig updated (e04d090245 -> 2a9bd92e82)

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-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from e04d090245 32: onsuccess: #436: boot: Success after binutils/gcc/linux/ [...] new 2a9bd92e82 33: onsuccess: #437: boot: Success after binutils/gcc: 9 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30216 -> 30400 bytes 04-build_abe-stage1/console.log.xz | Bin 68348 -> 68684 bytes 05-build_abe-qemu/console.log.xz | Bin 31520 -> 31956 bytes 06-build_linux/console.log.xz | Bin 3324 -> 3348 bytes 07-boot_linux/console.log.xz | Bin 6220 -> 6244 bytes 08-check_regression/console.log.xz | Bin 3984 -> 3096 bytes 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 | 24 ++++++++++++------------ 15 files changed, 18 insertions(+), 18 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_bmk_gnu_apm/gnu-master-aarch64-spec2k6-Os updated (a70cb677c9 -> 1b280d881c)

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_gnu_apm/gnu-master-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from a70cb677c9 45: force: #338: 1: [TCWG CI] No change after gcc: 106 commits new 1b280d881c 46: force: #339: 1: [TCWG CI] 447.dealII:[.] _ZN16Constraint [...] 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 1824 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 33044 -> 32984 bytes 04-build_abe-stage1/console.log.xz | Bin 74692 -> 73512 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 246796 -> 245816 bytes 08-build_abe-stage2/console.log.xz | Bin 184444 -> 182740 bytes 09-benchmark/benchmark-build.log | 86 +- 09-benchmark/benchmark.log | 84 +- 09-benchmark/console.log.xz | Bin 3884 -> 3872 bytes 10-check_regression/447.dealII.symbols-regression | 1 + 10-check_regression/console.log.xz | Bin 13752 -> 14328 bytes .../csv-results-vs-first-1/md5sum.csv | 2781 +- .../csv-results-vs-first-1/perf.csv | 3645 +- .../csv-results-vs-first-1/results.csv | 6611 +- .../csv-results-vs-first-1/size.csv | 348512 +++++++++--------- .../csv-results-vs-first-1/vect.csv | 28 +- .../csv-results-vs-prev-0/md5sum.csv | 2111 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3514 +- .../csv-results-vs-prev-0/results.csv | 7932 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 4071 +- .../csv-results-vs-prev-1/md5sum.csv | 2781 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3645 +- .../csv-results-vs-prev-1/results.csv | 6611 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 348512 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 28 +- 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 3 + 10-check_regression/mail-body.txt | 3 + 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3538 +- 10-check_regression/results-vs-first-internal.csv | 252 +- 10-check_regression/results-vs-first.csv | 252 +- 10-check_regression/results-vs-first.log | 1294 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 12 +- 10-check_regression/results-vs-prev-full.csv | 3748 +- 10-check_regression/results-vs-prev-internal.csv | 252 +- 10-check_regression/results-vs-prev.csv | 252 +- 10-check_regression/results-vs-prev.log | 1366 +- 10-check_regression/results.regressions | 5 + 10-check_regression/symbol.regression | 1 + 10-check_regression/trigger-bisect | 3 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 10 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 10 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 10 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 10 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 10 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 10 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 128 +- dashboard/squad-vs-first/summary-annotation.txt | 1 + git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 516 + jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 5 + results_id | 2 +- 111 files changed, 374785 insertions(+), 378342 deletions(-) create mode 100644 10-check_regression/447.dealII.symbols-regression create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/symbol.regression create mode 100644 10-check_regression/trigger-bisect copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/trigge [...] create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/interesting-commits] branch master updated (ba738a8b -> ccdf440b)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from ba738a8b Add entry f124e59b2e515d65e0b941826467e08de5ba97b0 from https [...] new ccdf440b Add entry 9d549401ae8ab334c8cba1c1339dbd3c8e695685 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../tcwg_bmk_gnu_apm/gnu-master-aarch64-spec2k6-Os}/build_url | 2 +- .../gnu-master-aarch64-spec2k6-Os/last_good | 0 .../gnu-master-aarch64-spec2k6-Os/summary.txt | 0 .../{tcwg_bmk_gnu_sq => tcwg_bmk_gnu_apm}/status.txt | 4 ++-- 4 files changed, 3 insertions(+), 3 deletions(-) copy gcc/sha1/{e364e27b6636ba09755790358910f199d07194b3/tcwg_bmk_gnu_apm/gnu-relea [...] copy gcc/sha1/9d549401ae8ab334c8cba1c1339dbd3c8e695685/{tcwg_bmk_gnu_sq => tcwg_bm [...] copy gcc/sha1/9d549401ae8ab334c8cba1c1339dbd3c8e695685/{tcwg_bmk_gnu_sq => tcwg_bm [...] copy gcc/sha1/9d549401ae8ab334c8cba1c1339dbd3c8e695685/{tcwg_bmk_gnu_sq => tcwg_bm [...] -- 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-arm updated (ff78a50570 -> 6d65953d94)

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-arm in repository toolchain/ci/base-artifacts. discards ff78a50570 463: onsuccess: #2105: 1: Success after binutils/gcc: 10 commits discards 326f56f3bd 462: onsuccess: #2104: 1: Success after binutils/gcc: 2 commits discards 0a83950fd3 461: onsuccess: #2103: 1: Success after binutils/gcc: 2 commits discards 163b1c3879 460: onsuccess: #2102: 1: Success after binutils: 2 commits discards 8ac52543e8 459: onsuccess: #2101: 1: Success after binutils/gcc: 3 commits discards c90c8f66b4 458: onsuccess: #2100: 1: Success after gdb-13-branchpoint-1 [...] discards 4cd21c0b67 457: onsuccess: #2099: 1: Success after binutils/gcc: 2 commits discards 79c1424984 456: onsuccess: #2098: 1: Success after binutils: 10 commits discards 1c725be8af 455: onsuccess: #2097: 1: Success after binutils/gcc: 11 commits discards 81dab7b451 454: onsuccess: #2096: 1: Success after gcc: 4 commits discards ca03103596 453: onsuccess: #2095: 1: Success after gdb-13-branchpoint-1 [...] discards 04aa471d88 452: onsuccess: #2094: 1: Success after binutils/gcc: 4 commits discards 027e2e73d8 451: onsuccess: #2093: 1: Success after binutils/gcc: 4 commits discards 573409d91e 450: onsuccess: #2092: 1: Success after binutils/gcc: 28 commits discards 00e87da864 449: onsuccess: #2091: 1: Success after binutils/gcc: 29 commits discards 8eb46b5b1f 448: onsuccess: #2090: 1: Success after binutils/gcc: 28 commits discards 100724f05c 447: onsuccess: #2089: 1: Success after binutils/gcc: 10 commits discards b68364745c 446: onsuccess: #2088: 1: Success after binutils/gcc: 6 commits discards a3fd936f04 445: onsuccess: #2087: 1: Success after binutils/gcc: 15 commits discards dae64bad96 444: onsuccess: #2086: 1: Success after binutils/gcc: 12 commits discards b4191c26f6 443: onsuccess: #2085: 1: Success after binutils/gcc: 4 commits discards f2f86d1ead 442: onsuccess: #2084: 1: Success after binutils/gcc: 12 commits discards 8c3a0bc09f 441: onsuccess: #2083: 1: Success after binutils/gcc: 38 commits discards 2f043c9fdd 440: onsuccess: #2082: 1: Success after binutils/gcc: 11 commits discards 3a43db931b 439: onsuccess: #2081: 1: Success after binutils/gcc: 4 commits discards 038407e8fa 438: onsuccess: #2080: 1: Success after gcc: 3 commits discards f82074d2b9 437: onsuccess: #2079: 1: Success after binutils/gcc: 4 commits discards 230f344930 436: onsuccess: #2078: 1: Success after binutils/gcc: 6 commits discards 6c2a1a7080 435: onsuccess: #2077: 1: Success after gcc: 5 commits discards 5c8829e975 434: onsuccess: #2076: 1: Success after binutils/gcc: 30 commits discards 6551a5b8f0 433: onsuccess: #2075: 1: Success after binutils/gcc: 16 commits discards 1afac00f9b 432: onsuccess: #2074: 1: Success after binutils/gcc: 2 commits discards 0b2931bf68 431: onsuccess: #2073: 1: Success after basepoints/gcc-13-47 [...] discards d4672a1e2d 430: onsuccess: #2072: 1: Success after binutils/gcc: 3 commits discards 3b81627671 429: onsuccess: #2071: 1: Success after binutils/gcc: 5 commits discards 915d396fcc 428: onsuccess: #2070: 1: Success after basepoints/gcc-13-47 [...] discards 34eb065318 427: onsuccess: #2069: 1: Success after basepoints/gcc-13-47 [...] discards 8c654e6e44 426: onsuccess: #2068: 1: Success after binutils: 9 commits discards 937fa27083 425: onsuccess: #2067: 1: Success after binutils/gcc: 5 commits discards 7636e1cac8 424: onsuccess: #2066: 1: Success after gcc: 11 commits discards 215e87a79f 423: onsuccess: #2065: 1: Success after binutils/gcc: 21 commits discards 463867c837 422: onsuccess: #2063: 1: Success after binutils/gcc: 6 commits discards 31ca909330 421: onsuccess: #2062: 1: Success after binutils/gcc: 15 commits discards 88175794d6 420: onsuccess: #2061: 1: Success after binutils/gcc: 13 commits discards 94e5ae436a 419: onsuccess: #2060: 1: Success after gcc: 3 commits discards 67c95c6bc5 418: onsuccess: #2059: 1: Success after binutils/gcc: 2 commits discards e5f1456888 417: onsuccess: #2058: 1: Success after gcc: 7 commits discards 144c3b005b 416: onsuccess: #2057: 1: Success after binutils/gcc: 17 commits discards cf0ce7d6f6 415: onsuccess: #2056: 1: Success after binutils/gcc: 10 commits discards 9165a36b4e 414: onsuccess: #2055: 1: Success after binutils/gcc: 12 commits discards 7b9eee4901 413: onsuccess: #2054: 1: Success after binutils/gcc: 10 commits discards c587511920 412: onsuccess: #2053: 1: Success after binutils/gcc: 53 commits discards 190ec9d483 411: onsuccess: #2052: 1: Success after binutils/gcc: 6 commits discards 236daaa119 410: onsuccess: #2051: 1: Success after binutils/gcc: 5 commits discards febaef02f6 409: onsuccess: #2050: 1: Success after binutils/gcc: 6 commits discards 47694e8f21 408: onsuccess: #2049: 1: Success after binutils/gcc: 26 commits discards 93243d60d5 407: onsuccess: #2048: 1: Success after binutils/gcc: 12 commits discards 0d873c060a 406: onsuccess: #2047: 1: Success after binutils/gcc: 2 commits discards b9080ee8fb 405: onsuccess: #2046: 1: Success after gcc: 2 commits discards c8f0ac829d 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits discards 9f3b874da2 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits discards 0fc561150d 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-45 [...] discards 19c8de654b 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits discards 561e977617 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits discards 2b0f89e5cc 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits discards 4645a4689d 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits discards ac094191c8 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits discards e735eb91e6 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits discards 73b64f661d 395: onsuccess: #2035: 1: Success after gcc: 4 commits discards 7952582687 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits discards be68d75edb 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits discards eb698ba8ef 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits discards dc1bf744bd 391: onsuccess: #2031: 1: Success after binutils/gcc: 5 commits discards 8d10424d66 390: onsuccess: #2030: 1: Success after binutils/gcc: 8 commits discards 5388a4adb5 389: onsuccess: #2029: 1: Success after binutils/gcc: 13 commits discards ecf2c0541a 388: onsuccess: #2028: 1: Success after binutils/gcc: 15 commits discards 9604dd395f 387: onsuccess: #2027: 1: Success after binutils/gcc: 14 commits discards b6db493711 386: onsuccess: #2026: 1: Success after binutils/gcc: 5 commits discards 86745ba4e1 385: onsuccess: #2025: 1: Success after binutils: 8 commits discards 649882c5b1 384: onsuccess: #2024: 1: Success after binutils/gcc: 13 commits discards aa10b5ca19 383: onsuccess: #2023: 1: Success after binutils/gcc: 7 commits discards b117e2ac20 382: onsuccess: #2022: 1: Success after binutils/gcc: 3 commits discards 2d42842464 381: onsuccess: #2021: 1: Success after binutils/gcc: 6 commits discards 4e9e0964f6 380: onsuccess: #2020: 1: Success after gcc: 2 commits discards ebdcc25738 379: onsuccess: #2019: 1: Success after gcc: 3 commits discards 257c8c1387 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits discards e381c02783 377: onsuccess: #2017: 1: Success after binutils: 3 commits discards ac1e68fb2d 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-44 [...] discards 0c75882151 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits discards c425a536fd 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits discards d48b256fbc 373: onsuccess: #2013: 1: Success after gcc: 6 commits discards e342795ae8 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits discards 4986badb08 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits discards 12f4b2ddcf 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits discards dc9560e7cf 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits discards 553de945d2 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits discards 7341f5d282 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits discards 08ea09d0c9 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits discards c6cd824b40 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits discards 76b3abaff3 364: onsuccess: #2000: 1: Success after gcc: 5 commits discards f5f225b1b9 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits new 93c04aaf69 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits new 71960b5fce 364: onsuccess: #2000: 1: Success after gcc: 5 commits new 899cb1dc2e 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits new 0ddfff28a0 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits new f7be18a782 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits new cb77bb7cb4 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits new 4c714adbeb 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits new 4c12178182 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits new b596220d28 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits new 80077d8546 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits new 6b7fe7aac3 373: onsuccess: #2013: 1: Success after gcc: 6 commits new a6c234ac94 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits new 3af0bcbf87 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits new 3bb4c603da 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-44 [...] new a1f9c32867 377: onsuccess: #2017: 1: Success after binutils: 3 commits new 299ba25e1d 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits new 949f0fd1fa 379: onsuccess: #2019: 1: Success after gcc: 3 commits new 9c21c5f6ce 380: onsuccess: #2020: 1: Success after gcc: 2 commits new bb3e6f9581 381: onsuccess: #2021: 1: Success after binutils/gcc: 6 commits new d51798ca46 382: onsuccess: #2022: 1: Success after binutils/gcc: 3 commits new 2e93bb3455 383: onsuccess: #2023: 1: Success after binutils/gcc: 7 commits new 0df09cd460 384: onsuccess: #2024: 1: Success after binutils/gcc: 13 commits new aca8082248 385: onsuccess: #2025: 1: Success after binutils: 8 commits new c40339e6d9 386: onsuccess: #2026: 1: Success after binutils/gcc: 5 commits new ee71801d8d 387: onsuccess: #2027: 1: Success after binutils/gcc: 14 commits new 1984cde6f7 388: onsuccess: #2028: 1: Success after binutils/gcc: 15 commits new e6e4329726 389: onsuccess: #2029: 1: Success after binutils/gcc: 13 commits new 47030efe79 390: onsuccess: #2030: 1: Success after binutils/gcc: 8 commits new a63dfb181e 391: onsuccess: #2031: 1: Success after binutils/gcc: 5 commits new a762cc955d 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits new 52674124dc 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits new cb64de1ad1 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits new 486aef98f3 395: onsuccess: #2035: 1: Success after gcc: 4 commits new be0c793607 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits new f5b5214fdb 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits new ee2af7d348 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits new f4e27cc7be 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits new 4c0f55ca1e 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits new 7e0c3b0095 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits new 010f1ac0ed 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-45 [...] new a5b0843f49 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits new 09c98a344a 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits new a9ed62d3a0 405: onsuccess: #2046: 1: Success after gcc: 2 commits new 5f171df50c 406: onsuccess: #2047: 1: Success after binutils/gcc: 2 commits new 5cdd82ba40 407: onsuccess: #2048: 1: Success after binutils/gcc: 12 commits new 087923fb7f 408: onsuccess: #2049: 1: Success after binutils/gcc: 26 commits new c97a40b919 409: onsuccess: #2050: 1: Success after binutils/gcc: 6 commits new c7c443a1bf 410: onsuccess: #2051: 1: Success after binutils/gcc: 5 commits new 097015d1be 411: onsuccess: #2052: 1: Success after binutils/gcc: 6 commits new 65c27ebd52 412: onsuccess: #2053: 1: Success after binutils/gcc: 53 commits new f5fe046782 413: onsuccess: #2054: 1: Success after binutils/gcc: 10 commits new f1be05984f 414: onsuccess: #2055: 1: Success after binutils/gcc: 12 commits new 77fb97d4a1 415: onsuccess: #2056: 1: Success after binutils/gcc: 10 commits new c8b2a84478 416: onsuccess: #2057: 1: Success after binutils/gcc: 17 commits new b5bb29bca5 417: onsuccess: #2058: 1: Success after gcc: 7 commits new d37e728567 418: onsuccess: #2059: 1: Success after binutils/gcc: 2 commits new 892c0775c7 419: onsuccess: #2060: 1: Success after gcc: 3 commits new eff79504ff 420: onsuccess: #2061: 1: Success after binutils/gcc: 13 commits new eda597b249 421: onsuccess: #2062: 1: Success after binutils/gcc: 15 commits new b9f19d3187 422: onsuccess: #2063: 1: Success after binutils/gcc: 6 commits new ce72608e3e 423: onsuccess: #2065: 1: Success after binutils/gcc: 21 commits new fc826cd2e6 424: onsuccess: #2066: 1: Success after gcc: 11 commits new 8d1d538ceb 425: onsuccess: #2067: 1: Success after binutils/gcc: 5 commits new fb9ed955af 426: onsuccess: #2068: 1: Success after binutils: 9 commits new f0882c912c 427: onsuccess: #2069: 1: Success after basepoints/gcc-13-47 [...] new cc8ad11608 428: onsuccess: #2070: 1: Success after basepoints/gcc-13-47 [...] new 25833b1c46 429: onsuccess: #2071: 1: Success after binutils/gcc: 5 commits new 5cbe06e5cb 430: onsuccess: #2072: 1: Success after binutils/gcc: 3 commits new 3e3c825339 431: onsuccess: #2073: 1: Success after basepoints/gcc-13-47 [...] new 95be0d0371 432: onsuccess: #2074: 1: Success after binutils/gcc: 2 commits new d9d37cbd2d 433: onsuccess: #2075: 1: Success after binutils/gcc: 16 commits new 441521cac2 434: onsuccess: #2076: 1: Success after binutils/gcc: 30 commits new 5e13b7496a 435: onsuccess: #2077: 1: Success after gcc: 5 commits new 555a13956e 436: onsuccess: #2078: 1: Success after binutils/gcc: 6 commits new 5e054a4f05 437: onsuccess: #2079: 1: Success after binutils/gcc: 4 commits new a474299a8d 438: onsuccess: #2080: 1: Success after gcc: 3 commits new f0c858423b 439: onsuccess: #2081: 1: Success after binutils/gcc: 4 commits new 351e435311 440: onsuccess: #2082: 1: Success after binutils/gcc: 11 commits new 2eb6c7e6f7 441: onsuccess: #2083: 1: Success after binutils/gcc: 38 commits new ada83ce503 442: onsuccess: #2084: 1: Success after binutils/gcc: 12 commits new 56a3dbe293 443: onsuccess: #2085: 1: Success after binutils/gcc: 4 commits new 77beb6fe2f 444: onsuccess: #2086: 1: Success after binutils/gcc: 12 commits new 349adbdf06 445: onsuccess: #2087: 1: Success after binutils/gcc: 15 commits new 380f178737 446: onsuccess: #2088: 1: Success after binutils/gcc: 6 commits new bc9920ac60 447: onsuccess: #2089: 1: Success after binutils/gcc: 10 commits new ed2f412db5 448: onsuccess: #2090: 1: Success after binutils/gcc: 28 commits new f4e554ba0f 449: onsuccess: #2091: 1: Success after binutils/gcc: 29 commits new 6a2d0419be 450: onsuccess: #2092: 1: Success after binutils/gcc: 28 commits new 82db0fa66a 451: onsuccess: #2093: 1: Success after binutils/gcc: 4 commits new 0773c5a1f0 452: onsuccess: #2094: 1: Success after binutils/gcc: 4 commits new 74afe9db40 453: onsuccess: #2095: 1: Success after gdb-13-branchpoint-1 [...] new db369114d0 454: onsuccess: #2096: 1: Success after gcc: 4 commits new 43fc04207a 455: onsuccess: #2097: 1: Success after binutils/gcc: 11 commits new 146a33b68b 456: onsuccess: #2098: 1: Success after binutils: 10 commits new c149746116 457: onsuccess: #2099: 1: Success after binutils/gcc: 2 commits new b6bf2f040f 458: onsuccess: #2100: 1: Success after gdb-13-branchpoint-1 [...] new d027facc39 459: onsuccess: #2101: 1: Success after binutils/gcc: 3 commits new 5a37be3897 460: onsuccess: #2102: 1: Success after binutils: 2 commits new 7a5019d871 461: onsuccess: #2103: 1: Success after binutils/gcc: 2 commits new f710b8f494 462: onsuccess: #2104: 1: Success after binutils/gcc: 2 commits new bdcede797c 463: onsuccess: #2105: 1: Success after binutils/gcc: 10 commits new 6d65953d94 464: onsuccess: #2106: 1: Success after gcc: 9 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 (ff78a50570) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (6d [...] 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 1712 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 52412 -> 53412 bytes 04-build_abe-gcc/console.log.xz | Bin 237284 -> 240744 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3828 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3392 -> 2604 bytes 07-check_regression/console.log.xz | Bin 4572 -> 4512 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 2859320 -> 2843104 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2441248 -> 2468924 bytes sumfiles/gcc.sum | 4800 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 913972 -> 914288 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217552 -> 217424 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2536 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 479004 -> 480360 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2555 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_gnu_native_build/master-arm updated (d4d788c2c5 -> 4aee8ca845)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. discards d4d788c2c5 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards 2c6dad9b8b 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards cb506489e7 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards 2a2ce97761 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards 8ed8a06b82 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards f5d3dab33c 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards b50c702c87 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards 689ba63415 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards 01969988ca 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards be89bcce08 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards c26503aa94 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards a7b757b8bf 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards 395096b374 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards cb3789903e 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards 5df36951a7 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 4d4be003a3 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards ead645cd1f 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards b9eea13f11 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards 6abfcaf151 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards a6cd5197fe 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards c5b5f93908 134: onsuccess: #544: 6: Success after binutils: 18 commits discards b1f9d180ad 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards 790273c9fe 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards 16311f7002 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards ba121e9ff2 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards 76f6e2ee51 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards c36bd7a4e5 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards 19a88cb955 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 70431c338c 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 811becf910 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards 11ca1333d4 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 8438a28181 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards e6a8f119c4 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards 1cd53b4f32 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 2ae4373d00 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards 0eaf37d2e5 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards 6089ba2c4d 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards bb26b91a15 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards 69e3e31eb8 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards 8fc104a90c 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards 12874b3741 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 2b15641b53 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 0e425f6362 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 489521cb80 111: force: #520: 6: Success after gcc: 9 commits discards b9737d4ddf 110: onsuccess: #518: 6: Success after binutils: 5 commits discards c63326bdaa 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 58ad0a33cb 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 929dfbd38b 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards 600b447265 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 6946155ba7 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards f17053d7bf 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 9e38146ee0 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 17d4531d8a 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 4c1aa1a2c1 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards cdf64a21da 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 80867e5ad1 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards aa09d70d5b 98: force: #504: 6: Success after gcc: 18 commits discards 0ce967f953 97: onsuccess: #503: 6: Success after linux: 11 commits discards cf4f443b89 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 736a194802 95: onsuccess: #500: 6: Success after binutils: 8 commits discards fd7e3707ff 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 0f8e10af93 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 1e3b303b7a 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards 2907067c1a 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards fa541366bd 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 18cad89d46 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 4a8d6b86e6 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards a696b3b435 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 1d3b58c1c4 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards 99dbd7d14e 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards e6dbc630f4 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 1891af1021 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 8efbd0c40d 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards c6ea6b142c 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards a70389e7a8 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 8a2231f997 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards dff7fc70f6 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 95c5a4c404 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 7db51de7c5 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards f996410f52 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 0af0e133f5 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards accd7b1c33 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards ae5b36bfdf 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards fd19e7606e 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 095ee44ac4 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards 29d59bde57 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 6c9b473499 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards 1c9d40b034 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards cb6e5954bd 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 1e3c2a0b2e 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 19a74bd81e 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards acc52b5ccb 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards 5be0fe1cdd 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 7d2ad85108 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 03096ed4ae 60: onsuccess: #463: 1: Success after gcc: 10 commits discards f2a9e1c594 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 79d04be24b 58: force: #461: 6: Success after gcc: 29 commits discards 4ffec2a0fd 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 34080b4cc0 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards 82f7a56706 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards 5abfcd12c6 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 2caddfea60 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new efec3f8a56 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new baab9b3f45 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new 393f56b3ac 57: onsuccess: #459: 6: Success after binutils: 8 commits new 0607d069e2 58: force: #461: 6: Success after gcc: 29 commits new 1835d92584 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new 6759fa9df6 60: onsuccess: #463: 1: Success after gcc: 10 commits new f4fb1d8bfa 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new 0fc78bb5f4 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new d82b986139 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new d701377e90 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new e7d04d33a6 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 60b85b8c6a 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new baa8ffe7f1 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new effa73f40a 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new 11e56a3274 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 63a51c561b 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 3759a8ae07 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 73e2515db0 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 8268c2aa1a 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new ac27270e30 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 2e0d2a8b6a 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 318d16972f 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new a488ec00a9 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new fb27d29aed 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 8414f047e7 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new c206914f52 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new a3d3de0c46 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 9c94afb73d 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 47de70cf29 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new c4609779d9 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new 2c2bc2e6c8 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 24fce39033 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 478639615d 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 9403205a99 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 8079ec7fdb 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 20fb1d05b1 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 45c19a0e1d 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new c70204d879 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new 051b574fd8 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 96d758ed1a 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new c5cd9c1056 95: onsuccess: #500: 6: Success after binutils: 8 commits new d6a3ae80ad 96: onsuccess: #502: 6: Success after glibc: 10 commits new 8ea5e11eb1 97: onsuccess: #503: 6: Success after linux: 11 commits new ad2e463654 98: force: #504: 6: Success after gcc: 18 commits new f73d266721 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 57b62dda7c 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new fd89ef2ed8 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 555a6dd061 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 709ea819c3 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 4e609cc274 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 224070efa9 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new fa6abb1282 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new d11e6cc64d 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 03c1ca8699 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 764e77d48e 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 1a9f77a673 110: onsuccess: #518: 6: Success after binutils: 5 commits new 1baad0a533 111: force: #520: 6: Success after gcc: 9 commits new e6678253a1 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new 198e15f6cb 113: onsuccess: #522: 1: Success after gcc: 12 commits new 2eca7df6b9 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 9a2522bc17 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new 4cf7ec702f 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new 3df5001e76 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new 4c90968fb4 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new 84f155bef3 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new ffd10f2bef 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new da15314bf0 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 8c3254772c 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new dc1d654a28 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new 3a561b6c7e 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 623d8abf6a 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new 0ccc539321 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 9a7c3185cb 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 8c88b8f018 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new e800f6ec51 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new 165a18c29a 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new 5e367c8c20 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new 24d33af6d2 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 5bcc6f1fbe 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new 72c68fc478 134: onsuccess: #544: 6: Success after binutils: 18 commits new 11bfb5df0c 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new 176d89cfb1 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new 2bf1ef3816 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new 3cabf1bdbe 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 63eca5917c 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new a07d54f2cb 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 2a65ce2b4c 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new b22687d481 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 10e6e7cfa2 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new f46434d569 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new c2a7b7a65b 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new 83fc38e25a 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new eca78b3d1b 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new a5c5f7856d 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new 8118ae79e1 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 2c6e1c1d64 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new f620205ac8 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new 53a14d3877 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new df6399eeb2 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new c48d81f00f 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 4aee8ca845 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 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 (d4d788c2c5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 53916 -> 53292 bytes 05-build_abe-gcc/console.log.xz | Bin 237200 -> 237896 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8352 -> 8352 bytes 08-build_abe-glibc/console.log.xz | Bin 237020 -> 236716 bytes 09-build_abe-gdb/console.log.xz | Bin 52900 -> 52304 bytes 10-check_regression/console.log.xz | Bin 3680 -> 3588 bytes 11-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++++++-------- 18 files changed, 53 insertions(+), 53 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_check_gcc/master-arm updated (3ab1248295 -> 24d2f8e52e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 3ab1248295 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 4dc7040713 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards deb65b5e27 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards a2ae45f55c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 17431d68cf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0ae6157292 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards ce128832c1 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 4ecda5260c 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 1e8eab22da 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards af8374846c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 85fa3f51b5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 568d006dc9 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards e9e7aef7db 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards f0eba5881d 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 6d378ad050 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 7769594967 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 3c238f91c9 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards d52aa71991 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 92a7491370 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 132019323a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 116fe50e3c 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards bc67b2ec52 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 3c8b88c32e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 6cf2d03133 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 35316cff39 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 3545cc6f3f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 79a1147347 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 90dcadaeff 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 99e52672e5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 5fccff3bad 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards af3d515a0b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards c805e126ea 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 754e9b0e68 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 0e2c60fff5 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards cc77beffe7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 440a26dc85 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 58bdc25fe5 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards b085d60698 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1d767931d7 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 39ad4ff153 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 66d394f377 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 46a2590f1b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 25af2b4bc1 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 551cc94cea 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards d3c0ed87bb 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards f52537b7e1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards c2768b882a 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards af53f5556c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 680c7a52b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards b3ee3061d6 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 32028d7526 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 52670f677f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ca0fc9e6e5 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 25ec2ebc07 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 587696c03c 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 4dd5457991 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e9c6219946 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 835470197b 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 881958081c 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards ab3286ff2e 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 40db2a0220 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards be35b9b3ad 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 2838a69fc5 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards a38cfa88ec 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards dc7de0c314 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards b97bc193bc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards f33da0c49f 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 887df005e0 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards f72d877792 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 5a999bcb62 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 566ff8916d 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 49d5d4da33 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 3d0cbcb9bb 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 9e946f9ed7 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 925cbed3be 212: onsuccess: #2022: 1: Success after linux: 3 commits discards ee3b573ed8 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards a1433cb5e7 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 1806fc53d3 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 32ff99c2e6 208: onsuccess: #2012: 1: Success after linux: 12 commits discards ace8380bbe 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards e3507243a8 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 59d1eacfdd 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards d04d66384c 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 64a3028cd2 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 26f7e79c67 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 7ebb1977a3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards f82793ea22 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 3c3f82eec8 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 8ffdb77abb 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards c9ef01b1bc 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards e1f3ef0d08 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards a5205585c9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards f8e4e4a28f 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 89edf5749c 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards dafacd38ee 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 0959dea97b 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 0c33a1f9d3 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 00994bd11c 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 69e4fef357 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards f75cb0a63e 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards d66660384b 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 4825974e21 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 27fec9c85f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new d7c983afa2 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new c398717762 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 41eb3af501 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new e7b5da4252 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new d2ed7e6f0b 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 57a4bb527c 193: onsuccess: #1992: 1: Success after binutils: 151 commits new b1d638e2ae 194: onsuccess: #1995: 1: Success after linux: 517 commits new 35104207d4 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new eaff03f2d3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 1e94aa9e7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 3c5ca81bb8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 6ea2d123e3 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 33bd8fee69 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 1a99611e6f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 8f277b5992 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 7e418bb16e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 5b2b70be31 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new ca539dedb1 205: onsuccess: #2006: 1: Success after gcc: 3 commits new a2721c90de 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 13278fa766 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 55e4344ade 208: onsuccess: #2012: 1: Success after linux: 12 commits new 73efea1a30 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 1a571261b8 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 2eb08e9e58 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 505c9a76cb 212: onsuccess: #2022: 1: Success after linux: 3 commits new 51739e0630 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 2bd8e8ee47 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 7114f16ccb 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 013238137b 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new b460f25782 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 93cbfde7af 218: onsuccess: #2030: 1: Success after gcc: 5 commits new cf294a9e39 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 1e86141968 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 360a41a7ac 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 7858129674 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 1bb9f05857 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 58b59512fb 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 633170b04e 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 9a579e3b20 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 99f36ca52d 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new bb6087e721 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new e73d830656 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 0691c54a5c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 9f2ee5abb0 231: onsuccess: #2047: 1: Success after gcc: 4 commits new f74babcc09 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7fd1861b3e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 594360ad72 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 07d7b7f7af 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 2bfa65a5cd 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new c2f29f0f7e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 070bcae0a7 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new d5ae4af76d 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 508b112f59 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 1f4740a64e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 862d75da02 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new e6383de794 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 9b24908d9d 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 3129e06acf 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new a6e6706f89 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new bd824bf516 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 5d8ff77027 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 959efe3851 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new ee03965901 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 7c07c8a06f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new adc1db52f3 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d5593e1ed3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new ebc3d8c0bd 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 3593154949 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 7e7f38b9d7 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 1bb2ced902 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new abd1e0ef6f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 7ce64cb1c6 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 7f99478a9c 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d0a2dff8ca 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new fb68f0a758 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 23b74e697d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 3d459fc3fe 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 31a83351a8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 3cc0df6119 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b292a7fef6 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 561445de82 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new b4aafe461d 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new fd4eaa0635 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new ec2138152e 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 328978c2cf 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9f516865e9 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 8b4452e787 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 6ef5048c52 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 39234e79e9 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 98952bd617 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 13fab3adaf 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 84581d16ea 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 10026f2a5d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5e5f5f5213 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new b5f30b36b8 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 1b5f084072 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 99ecca3ca4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 740ae84354 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 0b0823540b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 24d2f8e52e 287: onsuccess: #2103: 1: Success after gcc: 9 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 (3ab1248295) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1784 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31912 -> 31812 bytes 04-build_abe-stage1/console.log.xz | Bin 91460 -> 91680 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8368 bytes 07-build_abe-glibc/console.log.xz | Bin 236964 -> 236896 bytes 08-build_abe-stage2/console.log.xz | Bin 228132 -> 228044 bytes 09-build_abe-gdb/console.log.xz | Bin 39140 -> 39224 bytes 10-build_abe-qemu/console.log.xz | Bin 31400 -> 31292 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2488 -> 2624 bytes 13-check_regression/console.log.xz | Bin 5604 -> 5460 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 - sumfiles/g++.log.xz | Bin 2649532 -> 2685168 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2262436 -> 2227740 bytes sumfiles/gcc.sum | 2368 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893536 -> 892732 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214076 -> 214140 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434040 -> 434140 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1322 insertions(+), 1374 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-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_gcc_bootstrap/release-arm-bootstrap_O3 updated (c813e6e0a7 -> 2f44ffedd7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. from c813e6e0a7 42: onsuccess: #151: 2: Success after binutils/gcc: 9 commits new 2f44ffedd7 43: onsuccess: #152: 2: Success after binutils/gcc: 7 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 52704 -> 53020 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 460412 -> 460184 bytes 06-check_regression/console.log.xz | Bin 2780 -> 2700 bytes 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page: