Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017fast/gnu-aarch64-master-Os created (now 56013cfb03)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-cpu2017fast/gnu-aarch64-master-Os in repository toolchain/ci/base-artifacts. at 56013cfb03 0: init: #1: 1: [TCWG CI] No change after baseline build: no [...] This branch includes the following new commits: new 56013cfb03 0: init: #1: 1: [TCWG CI] No change after baseline build: no [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (ba69665130 -> e8cd4a25d3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards ba69665130 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards c0b00585ed 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards f9382c27c1 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 48bfa8b0d9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards de7032c109 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 92fdc141d3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 9aa1558dd0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 934b57ef96 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 66471d169a 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 2699fd433d 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 700f4be0fa 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards b2f6eed0a0 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards be1bf1af0c 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards ad2ba69c35 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 0b68501b0b 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 8ffcf5830e 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards d2d87617e9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 31a8b145cc 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 73ada2764e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards e3e6376b31 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards a7418c8d6e 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards b618d80a50 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards d09ad2856e 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 6a020ff494 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 689c9d87c9 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 9c09dd9a1e 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 6b209c2226 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 43ea940a04 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards bba75055d7 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 8abc49e177 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards d20dac2f34 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards e8fae26046 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 1de3f02bd1 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 82f3d084cb 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 4ca2faaca6 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards b5ce8d6c0b 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 5212a865ee 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 6da23fbba9 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 59834ad18d 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards e9df14cf28 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 05f9e4464b 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 681395beff 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 95234b5792 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 252ce0e2d0 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 392f35c0e3 149: onsuccess: #684: 1: Success after linux: 10 commits discards bba15afda6 148: onsuccess: #683: 1: Success after glibc: 9 commits discards ffb52420c1 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 85eb3841a4 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 4b0e080833 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 7745f601bb 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 2ac8ca1c9b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 7a1247d55d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards a2a031cc78 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 1dee706ff4 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 304afd6e7b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 6b8dd3321f 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards d4d3366f73 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards c7ee1a0815 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards d88a6db3b8 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards bf9fae62be 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 47b15d59bd 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 371ced168f 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 89dc51c2d8 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 83e4ac6054 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards b82abd5cce 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 94304772fa 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 222e9189e4 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 3b681d023e 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards a9ff54651c 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 4b8be3cb8c 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 27bf1094b2 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 93d0f2e07d 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards c565d74292 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards fe508c17f1 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 64dd72769b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 4102242e96 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 5fdc39f52e 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 64c50126fb 116: onsuccess: #647: 1: Success after linux: 3 commits discards 4550d707ce 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 3092a28fdd 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards a0cdee1ecd 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 6ffeb789cb 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 45f49ea186 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 6ab5b1926a 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 0f2bc29d65 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 373df8b8e8 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 3cea7f003b 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards d716e6f3ca 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 06431ed1f7 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 1a6843bfd6 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 245f8a6221 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards e0f3866027 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards bce9a0a4c4 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards bef255cb8b 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 21640cf46b 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards a2d0e38834 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 47c46ec1b2 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards b9372dc230 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards d47f1b791a 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 7f418d1bda 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 7250cdfc04 93: onsuccess: #613: 1: Success after binutils: 19 commits new 747ed38dbe 93: onsuccess: #613: 1: Success after binutils: 19 commits new 4c1b14d243 94: onsuccess: #616: 1: Success after binutils: 2 commits new 1d0630f3a4 95: onsuccess: #619: 1: Success after binutils: 5 commits new 3fb354ff45 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new fc4b35f271 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 1c927eb893 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 10a6ee24d9 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 65a29d7ad5 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 62e11d62d0 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 9fa3a295f8 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 425bca998c 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new f318663df5 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 9f25eacfb3 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new c21a8fb7d5 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new ec9b43fe29 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new fd8f486c7e 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new df3b3e9b6c 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 5d23e12e2b 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new b74fedc75f 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new aadc74167d 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 4c2abd22ff 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 03208a8deb 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 0a524ed188 115: onsuccess: #645: 1: Success after binutils: 27 commits new 011133157f 116: onsuccess: #647: 1: Success after linux: 3 commits new 6f3cd41444 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 5121c46dcf 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 566f65decb 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new aa95aa129d 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 9ac7df01ec 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 88d00b2d3d 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 94b137c1f0 123: onsuccess: #655: 1: Success after binutils: 22 commits new 3b56acee18 124: onsuccess: #657: 1: Success after glibc: 2 commits new e0bd973e8e 125: onsuccess: #658: 1: Success after linux: 3224 commits new 6e705cf7a4 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 2d50463f19 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 5b0b479462 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 37e7583565 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new a20fbec435 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 3d27403929 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 43f1816d4c 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 08913e9adf 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new a92909d195 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 0ed4b75f29 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 660c5d2a5b 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new c79eda2cf1 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new cd03c0e773 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new c9214c7846 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new cdd06dab93 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new b9951fd629 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 667267142b 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new af134d5b7e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new d995ba5e69 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 936284a219 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 8753416eaf 146: onsuccess: #680: 1: Success after binutils: 20 commits new 67d691d06c 147: onsuccess: #681: 1: Success after gcc: 6 commits new 8b8530cd30 148: onsuccess: #683: 1: Success after glibc: 9 commits new 26ee8ac5b9 149: onsuccess: #684: 1: Success after linux: 10 commits new d3ddece2b3 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 3887c77dcf 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 17eb4ef506 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 6f11c2bf7f 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 0900b75892 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 953fc7a281 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 26b01d7406 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 15e965366e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 3f160bcaeb 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 112e881d35 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 3ef9208fef 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new c2626c8c54 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new abc57dd688 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 72713f5b09 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new f91b56641e 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 3164eddb91 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 2302c8c611 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 6e28eac0e5 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new b438fcc3fb 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 15c9e4aef2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 5743263caa 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 8c37e6d870 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new be2394166e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 2152f6353d 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 642e293736 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 1594a16115 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new d1f0b71fd1 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 4376a4455e 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new d33cd46840 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new f11a0a9db9 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new bbffb3321c 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 86ccb0ff6d 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new e132dd1e7a 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new d860416652 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new aa8c1e0aae 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 40480d1426 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 254d1e24ce 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new d6bdbf9b98 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new afea2df762 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new cf3168dc1a 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 83badc1df7 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 168a94aaf8 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 9a604e1d08 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new e6fec02cae 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e8cd4a25d3 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] 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 (ba69665130) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 38672 -> 38380 bytes 04-build_abe-gcc/console.log.xz | Bin 203848 -> 204332 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8756 -> 9488 bytes 07-build_abe-glibc/console.log.xz | Bin 243428 -> 244056 bytes 08-build_abe-gdb/console.log.xz | Bin 38896 -> 39044 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2024 -> 2028 bytes 11-check_regression/console.log.xz | Bin 5820 -> 5544 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 63028 -> 63044 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83876 -> 83892 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 122296 -> 122316 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 404 insertions(+), 404 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/jenkins-scripts] branch master updated (5bc3ecf8 -> b981a355)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/jenkins-scripts. from 5bc3ecf8 tcwg-report-stale-rr-jobs.sh: Fix after project renaming new b981a355 tcwg-benchmark.sh: Fix reboot sequence 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-benchmark.sh | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (8d3711801a -> 3e5e49fb48)

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 8d3711801a 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards dcfad8c588 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 0903f9169a 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards f1791fe97f 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 8eb4d7efb5 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 947f713654 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 8182f08791 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 35cf41dcd5 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards f1ab7e2521 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 8cf8057cc5 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 97f5d92158 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 8d6a184134 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards cd1ca5a134 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 6e65d1e97a 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 17439d6b91 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 87edefb503 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards de0a80c9ce 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards a8bb421173 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 0f900bd85b 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 2109352b46 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 00e8128bce 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards b275d030bc 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards d672b90ec5 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 866dfcff68 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards b48e395a04 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards ec86b4c1bb 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 02c8596127 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards c0dfe218aa 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards fb4316cd08 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 1369b40798 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards d2e9d83532 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 1b4d2d8915 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 37dd5c981f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards d85457391b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards c2fc8af697 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards ed5582f6dc 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 947cfc4ead 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 67f37b9176 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 2e5e6d8b32 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 3f6b07fedd 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 7c89168556 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 2e15827fcb 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards b6c6d821e9 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 11ed2447fc 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 897b2e4323 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards b60f809f12 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ab700410d2 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards c055bd9083 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 47e233cb46 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 9130f579ab 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 29b344de5e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 767c38f98c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 96b79189e0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards ec4ce8e7fc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards d422773094 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 0aaa1cf779 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 26c51b1f53 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards f879e31d05 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 62646f5156 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards cb6476c724 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards d110e67bbb 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 5eafa2d90f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards f7b4c9580a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ea5436ddeb 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 96cb788fe9 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards fb7b517555 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 6d4f973077 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 0052506390 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 4b7bcb94e5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 60a8b85a21 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards f8aceef42c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 1f27555ed7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards c2dc59b20a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 583dafd672 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 5ef0d3d076 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5a6591b882 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 39d64ecfba 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1ee76399bf 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 42a4420cda 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards ff1a0b19b5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards fda8235400 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 443856a9f0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards a3a8e9c052 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 7d4f4fd77e 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2c01716e5e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 9831156bdf 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 6d53c58e7e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards b32e9c9c87 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0b7606d5c4 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards da798451e4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 575c2940f1 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 76a23c6f91 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 1027209506 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards dd2cd3c961 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards d546004bc2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 3d7e52e659 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 71ef19d121 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 1b9130aed7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 9658622f56 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 919c5aa18e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards b12bf582ab 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 1e92681d5a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new b954a3d346 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 21fac27b70 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 36d1ca43d4 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new ee42407039 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 3682b14275 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2c15cbc582 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d473ffe654 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 3020a5cb37 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 36b3f024c8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2b1326ee36 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new dab80bb47e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 1f05bd8554 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new cd10a36fb7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 92c20b88bc 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new c0a27b3150 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 9b003a4be1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 38664a1a40 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b9c4d0e3d1 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new c765b6ce8c 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 0cdc015edb 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 25aeafb67e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 4b2e8168dd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new f470ba9e54 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ed9d52780a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8b31c243ce 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 4db2d14171 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4596f53424 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new afc799b8a2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new cf2296d12f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 9cf257b1ed 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new b462d08a30 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new f506d6f09c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 1fea9251b5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new bdc19c405b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 74e35ff265 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 1a89445186 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 4e4c94051e 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 7afb7a052b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 09004a953d 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5f56c59c5f 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 02b5eee781 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 65256a1686 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e7ac6ff32d 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 03c4a85235 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 7e14a3f8ac 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 064c4f229c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 90047851be 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new d13683d76d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new f3f170a561 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 77f0cd92f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new f3778e65d6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new f3fd1faef6 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new d5463f68cf 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ac7be1ca78 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 664b6ec677 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new bd95fdf48c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new b0d87a9fa2 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 0925ff0161 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 35044b25a2 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 750e709d3f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 947aa8c61a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new c7166b98fe 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new e9de695505 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 8a7aa8086c 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 5d8271700f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 3d3d9ecbe8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 8469f5da11 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 2aa7462e1f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new ccff250412 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 39f0a041da 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 97393c61c4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new e9f8a141aa 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 5b595b40be 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 5cd80859d9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 0e8497d13a 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new dfa41ea6c9 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 47e6814bac 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 0fffc0c751 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new c84c754079 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 0fdd349699 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 68cbbc3b72 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new c4151ad1fc 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 777e743ff8 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 2210744274 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new ff98fb8a63 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new ae8c0f0c59 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 305ab48f93 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 4ceab0b29c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new b03dfbf17c 436: onsuccess: #2260: 1: Success after gcc: 7 commits new fc08bbc3df 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 70f8356171 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new ef51cad9cc 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new fa139b8e73 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 99849c57ca 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 8cab5091bd 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new e841d7ad5c 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 0d30489dba 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fadcbd1a37 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 873e989676 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 8ed4b56a7f 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 3e5e49fb48 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] 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 (8d3711801a) \ 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 1804 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30572 -> 30576 bytes 04-build_abe-stage1/console.log.xz | Bin 89392 -> 89364 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 9444 bytes 07-build_abe-glibc/console.log.xz | Bin 235600 -> 236040 bytes 08-build_abe-stage2/console.log.xz | Bin 226308 -> 225760 bytes 09-build_abe-gdb/console.log.xz | Bin 38584 -> 38536 bytes 10-build_abe-qemu/console.log.xz | Bin 32052 -> 31684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3812 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2604 -> 3012 bytes 13-check_regression/console.log.xz | Bin 50028 -> 5832 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 5763 +-------------------------------- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2646524 -> 2670368 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2228808 -> 2205452 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 891408 -> 893788 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216916 -> 216992 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439080 -> 441292 bytes 37 files changed, 78 insertions(+), 5835 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-allyesconfig updated (f229c2a08a -> 4c7bc12ee6)

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-master-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from f229c2a08a 51: onsuccess: #567: 21184: Success after binutils/gcc/linux [...] new 4c7bc12ee6 52: onsuccess: #1: 21230: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30792 -> 30632 bytes 04-build_abe-stage1/console.log.xz | Bin 89140 -> 89128 bytes 05-build_abe-qemu/console.log.xz | Bin 32024 -> 32036 bytes 06-build_linux/console.log.xz | Bin 11592 -> 9264 bytes 08-check_regression/console.log.xz | Bin 4364 -> 4292 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-Os_LTO updated (013a887c8a -> 35c11a2ab5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-Os_LTO in repository toolchain/ci/base-artifacts. from 013a887c8a 49: onsuccess: #5: 1: [TCWG CI] No change after v6.1.13-4559 [...] new 35c11a2ab5 50: onsuccess: #6: 1: [TCWG CI] No change after binutils/gcc [...] 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 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31240 -> 30568 bytes 04-build_abe-stage1/console.log.xz | Bin 89864 -> 89548 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 7992 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 236880 -> 235732 bytes 08-build_abe-stage2/console.log.xz | Bin 213624 -> 211028 bytes 09-benchmark/benchmark-build.log | 99 +- 09-benchmark/benchmark.log | 97 +- 09-benchmark/console.log.xz | Bin 4052 -> 4052 bytes .../compare-results-vs-first-internal.csv | 70 +- .../compare-results-vs-prev-internal.csv | 70 +- 10-check_regression/console.log.xz | Bin 8428 -> 9980 bytes .../csv-results-vs-first-0/results.csv | 838960 ++++++++-------- .../csv-results-vs-first-0/size.csv | 838854 ++++++++-------- 10-check_regression/csv-results-vs-first-0/sve.csv | 28 +- .../csv-results-vs-first-1/perf.csv | 157 +- .../csv-results-vs-first-1/results.csv | 907302 +++++++++-------- .../csv-results-vs-first-1/size.csv | 910226 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 42 +- .../csv-results-vs-first-1/vect.csv | 33 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 162 +- .../csv-results-vs-prev-0/results.csv | 907303 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 910226 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 42 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 33 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 157 +- .../csv-results-vs-prev-1/results.csv | 907302 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 910226 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 42 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 33 +- .../output-bmk-results/exe.improvement | 5 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 169 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1018 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 2 + 10-check_regression/results-vs-prev-full.csv | 179 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1068 +- 11-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../410.bwaves/results-metadata.json | 16 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 16 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../482.sphinx3/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 336 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 30 +- mail/mail-body.txt | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- 91 files changed, 3567648 insertions(+), 3567642 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allnoconfig updated (9f0dfa2f51 -> ec9217d09c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 9f0dfa2f51 46: onsuccess: #448: all: Success after binutils/llvm/qemu: [...] new ec9217d09c 47: onsuccess: #1: all: Success after binutils/llvm/linux/qe [...] 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 1776 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30956 -> 30472 bytes 04-build_kernel_llvm/console.log.xz | Bin 65436 -> 64016 bytes 05-build_abe-qemu/console.log.xz | Bin 31748 -> 32144 bytes 06-build_linux/console.log.xz | Bin 3388 -> 3404 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3892 -> 4276 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (89633c13e9 -> cc0ea39d20)

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 89633c13e9 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 5423a23c51 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 416a173a93 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 97f0e05d38 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards a53ba76135 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 8bd5edea61 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 7508ca7312 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 872ad9fb6d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 2320713eed 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 6390ae03a9 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 9934c11e75 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 242fd2f242 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards d50d6378cc 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 203dbde21e 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards c157299e07 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards d12c7494fb 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 05f0ac78ab 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards fd280fa5f1 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards b1d1f188e3 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 34ef000954 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 65f8ee8765 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 1153487265 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 4628ae21f9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards a08ed2f836 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 65585c43ef 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 0e5125591d 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 7dc40ffae3 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 9c17688886 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 4b1368c5cd 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards be83512bff 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 14652fc2ed 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards c26bf2d919 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 84d2600061 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 1a4cd22a96 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards e797f76344 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards a548137bf1 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 20617314d5 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 063d07f1b6 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards bfd7de1fbb 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 2506bf96e9 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards f54f9f1908 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 030e3b2f01 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards e6e04917d8 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards ee5cba03fc 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 1aafe970bc 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 9ccb4105a9 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards f7eddc26f9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards a3d1f70aa0 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 4166706f8c 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 8f5d08492e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards ca70942a5c 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 9ffa89d0e6 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 05d5395463 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards d5acdd3286 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 7bda12ae5c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 3dbb526b29 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 7b28350cf2 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards dd3fd88b71 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 5338aa1211 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 79d884c01d 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards e57b0eec03 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 44c8e76f84 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 9e9f64d95b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 890cf4c61d 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 50e99f3e8a 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 6ecc466322 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8a61057b68 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 08c84af0ae 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 66812cacf4 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 69adf86f6e 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 9ff0e6ff70 125: onsuccess: #614: 1: Success after linux: 12 commits discards 636840b529 124: onsuccess: #612: 1: Success after binutils: 18 commits discards ff816d69e9 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 74fe5a4344 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards d690437f1e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards eed9740645 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards f13617fd83 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 07887a34b1 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards b7d32d2d17 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 8cce98a9aa 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 7cbdee3b9d 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 3148914642 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards cfbeafd157 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 10c35f54d2 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards c770ffe08c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards a27e2ccd15 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards f9ee83a0c1 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 4835393c67 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 6308be9e48 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards f667876275 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 6e7e835578 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 1f6caded77 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 7eea619c82 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 6895d813ec 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 62799975bb 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 75828ee6f1 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 9602ee7d74 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 43550c3633 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 9a486738c6 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 5755b45e32 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 59edaf55d3 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new c3bbf17757 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new aaff3da3dc 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 202d5592bd 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new f094832d02 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new c58fe8fba8 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 6b053fee39 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 0e1e744eba 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new ca7678c4c5 102: onsuccess: #586: 1: Success after binutils: 5 commits new 52333991c7 103: onsuccess: #589: 1: Success after binutils: 3 commits new 4b6aa1831d 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 8712f665f2 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new c631b90bfa 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 2cf5caf0c5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new a0c7e68ffe 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 769f4ad87a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 2f8957466e 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 98cd1b98f5 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 0764a62c11 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 3da62194b9 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 24a61b7c93 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 0007f215a6 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 52e5e45dc0 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 07e4ef1927 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new addbdeb92b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new ad37bdb51f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new eba4bcb095 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 2aaa2d8902 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 047c60e8d7 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 382ecd69b6 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 5f93131642 124: onsuccess: #612: 1: Success after binutils: 18 commits new da36ab8988 125: onsuccess: #614: 1: Success after linux: 12 commits new 6d46868900 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 9af718c8ef 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 9d51a32dd2 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 95cd0c664f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 0bed3ebbb2 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 5c3c852b9b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 2c4c04adfe 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 2348cd6981 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new d8ba6d7107 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 05a6bdb3f3 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 8e9e18b7be 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 3c44b00a85 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 12219fda2b 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 60ff5ea544 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 54d6d71b1b 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 9c16dde58f 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 0a91d5ace6 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new ca1c9278ad 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 4aca783531 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 85c132d528 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 50d3b14eea 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new a5f7c1a13c 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 30ca4999f0 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new cad5f23cc4 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 271c4d3816 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 683ac9c7b0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 9f71f61258 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 1bde905f2b 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new d9cebf3cfc 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 733bcf417e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 8f3ec6f6a6 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 46df86ccc1 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 98c0b8fd94 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new a820e1f176 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 5133c2e0f9 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 7b401895bb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 1a4a274767 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new f8c73f9786 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new d8114f7324 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 2762a516e6 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 3b2dc65ccb 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new bf9a33fd53 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 2f42d99f98 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 1cc45637be 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new cfc838cbb1 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 6247d717c3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new c65bced41c 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new dea42bb607 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new cf49786696 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 95bdd2a5a8 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new dc4319ab9d 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 9ff19c7d2d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new d85e848dd0 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new a8aa9cd29a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new e6f8a06520 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new e7afd8e9a2 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new a2e06d216d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 6e766d1042 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new bcc32a36b0 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 2471f5607f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 9309824f68 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new fdf03aa1c2 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 41cc0caf8f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 1010c3cd1c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 30544cd257 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new d79ff27146 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 1ab364af99 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new cc295817cc 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new d19971e44f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new d42765e020 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new cc0ea39d20 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] 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 (89633c13e9) \ 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 1756 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 53036 -> 52632 bytes 04-build_abe-gcc/console.log.xz | Bin 238040 -> 237692 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 9480 bytes 07-build_abe-glibc/console.log.xz | Bin 235308 -> 235420 bytes 08-build_abe-gdb/console.log.xz | Bin 50960 -> 51772 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3748 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2056 -> 1984 bytes 11-check_regression/console.log.xz | Bin 9032 -> 11156 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 45 +- 11-check_regression/mail-body.txt | 185 +- 11-check_regression/results.compare | 90 +- 11-check_regression/results.compare2 | 2350 ++++++++++-- 11-check_regression/results.regressions | 90 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 187 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 90 +- sumfiles/gdb.log.xz | Bin 2804788 -> 2798972 bytes sumfiles/gdb.sum | 6273 +++++++++++-------------------- 30 files changed, 4568 insertions(+), 4854 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017speed/llvm-aarch64-master-O2 created (now 8ca2fede3d)

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-fujitsu_speed-cpu2017speed/llvm-aarch64-master-O2 in repository toolchain/ci/base-artifacts. at 8ca2fede3d 0: init: #2: 1: [TCWG CI] No change after baseline build: no [...] This branch includes the following new commits: new 8ca2fede3d 0: init: #2: 1: [TCWG CI] No change after baseline build: no [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig updated (3e99bd2968 -> 8c9938acd7)

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-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 3e99bd2968 46: onsuccess: #404: all: Success after binutils/gcc/qemu: 3 [...] new 8c9938acd7 47: onsuccess: #1: all: Success after binutils/gcc/linux/qem [...] 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 1756 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30864 -> 30616 bytes 04-build_abe-stage1/console.log.xz | Bin 88716 -> 89852 bytes 05-build_abe-qemu/console.log.xz | Bin 31156 -> 30436 bytes 06-build_linux/console.log.xz | Bin 4296 -> 4284 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3924 -> 4112 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023