Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[gcc] branch releases/gcc-12 updated (cd425a35ec2 -> 2ca6dba641f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from cd425a35ec2 testsuite/108985 - missing vect_simd_clones target requirem [...] new 2ca6dba641f d: Fix closure fields don't get same alignment as local var [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/d/d-codegen.cc | 5 +++++ gcc/testsuite/gdc.dg/torture/pr109144.d | 9 +++++++++ 2 files changed, 14 insertions(+) create mode 100644 gcc/testsuite/gdc.dg/torture/pr109144.d -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (63b25b80124 -> 46c4be98d1e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 63b25b80124 contrib: Update instructions regarding Unicode updates new 46c4be98d1e d: Fix closure fields don't get same alignment as local var [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/d/d-codegen.cc | 5 +++++ gcc/testsuite/gdc.dg/torture/pr109144.d | 9 +++++++++ 2 files changed, 14 insertions(+) create mode 100644 gcc/testsuite/gdc.dg/torture/pr109144.d -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (c33ddc2dedf -> 10af7021706)

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 c33ddc2dedf 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 7a432d64974 212: force: #24: 1: Success after binutils: 2 commits discards a530a7807ea 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards df2ed6d544d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 27c38271962 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards af9cfa355a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards fc54861cbd5 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards fac3770cb6a 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f49c804000e 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c5a720773da 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards adc4983f0fb 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a8c9fba7964 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a5f71ebef13 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 37cfa395c26 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 95cf83f2a9e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5835cfcce1c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 5d7a709f2a1 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b298c881365 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d1f4bd5c1fb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 17729f16a1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 49c88743b8b 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards afbff676ac5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 7460a826a6f 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 69d5db9e2fd 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards ce08332517c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 9d93b8fa3e8 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 3046a5270a9 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards aa763cf2aac 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards c90c775f1bc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 08c3ee7c4a5 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards eac8f58e8a5 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 1f7736b1c54 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 23b76df5ed6 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 503fd8b5803 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 33aba974c4a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards ffd37ae4fb7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards f74b66445b8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards c282506435d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 95b9fb3ddf4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards d65a4d46f6f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards d66cbdc5a00 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards c3fec961a3f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards ca97ab2a903 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 412f2606478 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 24192ffb6a5 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 891eff88efe 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 00e4afd2463 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards de2e6708a0a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 39acb3dbe1f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 30dc7df634c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 20740fcc725 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 3c657b081bd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 09ce3e43c41 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards beec1efe94c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 86a15886bbe 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 40cb2e4d5de 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 029451ba447 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards d639cfc8c56 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards bca39e2c31f 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 067c2bd8db8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards ec7b55e33ae 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 12315bbe4ee 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards dc937b90672 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 034e17dcadd 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards bf7795ceb7e 149: onsuccess: #684: 1: Success after linux: 10 commits discards 470c49369a4 148: onsuccess: #683: 1: Success after glibc: 9 commits discards ef57c8dc050 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 9bfc3b1e386 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 655b9d2eabf 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 51ea402a5c0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 7164a729fac 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards f23760bd2dd 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 63b52a68c4d 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 3dcb4b4955a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 653995a2765 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards c223f8106ae 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards a150d47c88d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 82aed5d51ab 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards a7b538ae1b8 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards b86ac82aad7 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards bd59464471c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards d34f9c4c6e5 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards f2d62813191 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 52b6f289456 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards ead57ef19a3 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9667406af13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards a8680985cec 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards c615e1986bf 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 30eb313a9a6 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 45f44240a7a 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 014464cc383 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 6762e0a33c7 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 934a7196418 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 16e65e367c8 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7cf8021a787 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b8492c80ce4 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 0e4a2c4e637 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 6538cc53b38 116: onsuccess: #647: 1: Success after linux: 3 commits discards d3df69e9481 115: onsuccess: #645: 1: Success after binutils: 27 commits discards ebe01a38def 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards d78616a09f8 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9a82961b270 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 90e3e1bca60 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new f36c41967a8 115: onsuccess: #645: 1: Success after binutils: 27 commits new 9a76600bffe 116: onsuccess: #647: 1: Success after linux: 3 commits new a0c178f20cc 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new a6dda4a5edf 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 4aed62677a9 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new dc7c60a85d0 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new bbb78ad2b9b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new db82c4e0beb 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 2c17786d4a5 123: onsuccess: #655: 1: Success after binutils: 22 commits new 5e0d4912681 124: onsuccess: #657: 1: Success after glibc: 2 commits new 2514ca68eba 125: onsuccess: #658: 1: Success after linux: 3224 commits new f887834bf07 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new e5bcf0caa2d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4f4045c3234 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 70314b7896f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a4fdf8810db 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 02a3d0c6347 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 1709654920d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new c95d71d0cea 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 09883fd08ca 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new c126d951bf1 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new b502bb4a675 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 5a4c0426760 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 2a220907f78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 73c586ab2b9 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 8917d998c9c 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 3d6808ef56f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new efde725deef 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new f942ee68ffb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new c8624b7c189 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 0939ce19f13 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 37362cddc4e 146: onsuccess: #680: 1: Success after binutils: 20 commits new 24ff4229145 147: onsuccess: #681: 1: Success after gcc: 6 commits new d13c53793ca 148: onsuccess: #683: 1: Success after glibc: 9 commits new 6de25999706 149: onsuccess: #684: 1: Success after linux: 10 commits new 025066de901 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new c4eecca5a25 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 9df74fae9e3 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 241db191392 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 98a5fdb37ca 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 840875f9ed1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new aa28f4e6df3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 2d29cfd88e8 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 80e5a0e3519 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 92a4d3d72d5 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new ebb4cb9ecb1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 6472f74f6a4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 68818eb0709 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 0c828908b6e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new e0c417c45fc 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new b1f45623c67 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new c7cb3d6ba68 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 8d574b66c43 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 61adeb07a58 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 2fbb1a5dbb1 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 50533a902bf 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new df09fd47fb7 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 999a2b828cf 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 5f1ae993473 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 4123f8b6d89 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 7054587238f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 96609513715 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 51586a0e3fd 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new edcfba747d2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 92e35330638 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 3446a2c0d56 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new db641d84680 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new b8db38d209e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 711b42693eb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new be9483c5644 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 1c901da95e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 6f4557cc609 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 87cd0daf3d5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 08b7881805e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new cbf164bb953 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 2ad0b45ad72 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 78dc008778b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5011984f696 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new c10ad2513d4 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 0e1bc8cdb21 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ebc2e4101e1 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 84338d1f2f9 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 98116901bd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 01c82984de5 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2a66b34169c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new fc0a01f06c7 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0545660e7c3 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 62af3970cc6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4990dba3071 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 1dfc5763c8a 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 25ceb198cb0 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 98480832c40 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 02e6c41e4e9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b59bf7e7fb2 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 4655373d4ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 595626e4046 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 422a8110028 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 029e4c50123 212: force: #24: 1: Success after binutils: 2 commits new 51397ec318e 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 10af7021706 214: onsuccess: #26: 1: Success after binutils: 12 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 (c33ddc2dedf) \ 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 1948 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 3456 -> 3448 bytes 03-build_abe-binutils/console.log.xz | Bin 39456 -> 39312 bytes 04-build_abe-gcc/console.log.xz | Bin 204556 -> 203992 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 244016 -> 243896 bytes 08-build_abe-gdb/console.log.xz | Bin 39332 -> 38992 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3784 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2608 -> 2652 bytes 11-check_regression/console.log.xz | Bin 4200 -> 3592 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 36 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 45 +- 11-check_regression/results.regressions | 19 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1085 ---------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 19 - sumfiles/binutils.log.xz | Bin 62924 -> 62888 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83964 -> 83976 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122428 -> 122464 bytes sumfiles/ld.sum | 4 +- 40 files changed, 124 insertions(+), 1232 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-dalvikvm/oriole-master updated (5c43ebc64f6 -> 1500cd0be01)

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_aosp-code_size-dalvikvm/oriole-master in repository toolchain/ci/base-artifacts. from 5c43ebc64f6 11: onsuccess: #12: 0: Success after llvm: 189 commits new 1500cd0be01 12: onsuccess: #13: 0: Success after llvm: 131 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 1732 -> 1744 bytes 02-build_aosp_toolchain/console.log.xz | Bin 10292 -> 10068 bytes 03-build_shadow_llvm/console.log.xz | Bin 130780 -> 131164 bytes 04-build_aosp/console.log.xz | Bin 20800 -> 20824 bytes 05-check_regression/console.log.xz | Bin 3604 -> 3520 bytes dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- size.csv | 2 +- 12 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

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

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 d23fc64eb8c 212: force: #24: 1: Success after binutils: 2 commits discards 641d032472e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 70ce1e38067 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards cc5da72c581 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 46ba31c02aa 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards e8635e71b05 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards dadfb86f0d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards b539d0bd059 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards ba03dee73b4 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1c82456e5ac 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards dcb958ed0a6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e2053fe5cf9 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 09e4d4601a1 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 88ecec7b88e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e29e16536ab 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 849a6126ceb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2387b97c180 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ded5d13d6f3 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 353096743a4 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 0a75f26d30c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 032e8dc0616 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4f44dd829be 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 9e3a7868daf 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards de633a93e5d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards f89b7876728 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 571100967a2 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards d0be0916d20 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 1d006334e80 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 8a15eb53173 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards c442ed3cb4a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 1cd67853286 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 77d39ce378b 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 894e8bbeff5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 0d287d2e855 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards d9898c420f7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 6d7e17575a9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 841350e3f62 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 4e77618cda6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 49862106505 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards c822e673451 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards e80882aa849 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards d8ccc02ab41 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards ca07a678831 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 25c0051a4e0 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 36bf25527d2 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards c5a637e41a3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 8f7de082f91 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 3e58e1c8b81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 32cbf082a56 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 258bd3b63e6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 8eac1321f28 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 3a227ecc9b5 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards e929e7f5826 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards be2fc8ad262 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards afe7988a0c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 9c98c7c9d34 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards d25f99a292f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards e6c56bf7dbf 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 64e8c9006c8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards cc0cbf52192 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 880ffacdc76 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards f411babb411 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards e0cdc06ceae 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 4b85f6b8dd9 149: onsuccess: #684: 1: Success after linux: 10 commits discards d5fd0c98213 148: onsuccess: #683: 1: Success after glibc: 9 commits discards fd8995bd76d 147: onsuccess: #681: 1: Success after gcc: 6 commits discards ec590be6ae6 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 1defbe9eb61 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 7d5d99cc8b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards fb9d574eb02 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards b37a6f3fa7e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards c4f9983aa57 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards d97848c944a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 8e6ceb6d505 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 738254df701 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards bd69f3d7f9a 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 4fb63b715ca 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 0cd17dafed5 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 7dd02395b17 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 4e5d027d446 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a71f458c3fa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 1353807f14b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 7cb72c85f73 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 8f93da18fdb 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9193b2345f0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 80bb862f25a 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 7c735ce988f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 711180fb93d 125: onsuccess: #658: 1: Success after linux: 3224 commits discards fca17e32a2b 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 67cf3e9f5f5 123: onsuccess: #655: 1: Success after binutils: 22 commits discards ce81bcc2498 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards da9214d5b3f 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4e7633f22af 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7a75dea3d2b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a947f6736e5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 4d7cf2ad040 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 3d5c6e260d5 116: onsuccess: #647: 1: Success after linux: 3 commits discards e71a85dc0eb 115: onsuccess: #645: 1: Success after binutils: 27 commits discards af6f1a6c701 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 890843da2b2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards dcbdab3a058 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new e030dcf3eda 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new d78616a09f8 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new ebe01a38def 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new d3df69e9481 115: onsuccess: #645: 1: Success after binutils: 27 commits new 6538cc53b38 116: onsuccess: #647: 1: Success after linux: 3 commits new 0e4a2c4e637 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new b8492c80ce4 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7cf8021a787 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 16e65e367c8 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 934a7196418 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 6762e0a33c7 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 014464cc383 123: onsuccess: #655: 1: Success after binutils: 22 commits new 45f44240a7a 124: onsuccess: #657: 1: Success after glibc: 2 commits new 30eb313a9a6 125: onsuccess: #658: 1: Success after linux: 3224 commits new c615e1986bf 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new a8680985cec 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9667406af13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new ead57ef19a3 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 52b6f289456 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f2d62813191 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new d34f9c4c6e5 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new bd59464471c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new b86ac82aad7 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new a7b538ae1b8 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 82aed5d51ab 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new a150d47c88d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new c223f8106ae 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 653995a2765 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 3dcb4b4955a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 63b52a68c4d 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new f23760bd2dd 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 7164a729fac 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 51ea402a5c0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 655b9d2eabf 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 9bfc3b1e386 146: onsuccess: #680: 1: Success after binutils: 20 commits new ef57c8dc050 147: onsuccess: #681: 1: Success after gcc: 6 commits new 470c49369a4 148: onsuccess: #683: 1: Success after glibc: 9 commits new bf7795ceb7e 149: onsuccess: #684: 1: Success after linux: 10 commits new 034e17dcadd 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new dc937b90672 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 12315bbe4ee 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new ec7b55e33ae 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 067c2bd8db8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new bca39e2c31f 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new d639cfc8c56 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 029451ba447 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 40cb2e4d5de 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 86a15886bbe 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new beec1efe94c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 09ce3e43c41 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 3c657b081bd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 20740fcc725 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 30dc7df634c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 39acb3dbe1f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new de2e6708a0a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 00e4afd2463 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 891eff88efe 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 24192ffb6a5 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 412f2606478 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new ca97ab2a903 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new c3fec961a3f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new d66cbdc5a00 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new d65a4d46f6f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 95b9fb3ddf4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new c282506435d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new f74b66445b8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new ffd37ae4fb7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 33aba974c4a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 503fd8b5803 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 23b76df5ed6 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 1f7736b1c54 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new eac8f58e8a5 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 08c3ee7c4a5 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new c90c775f1bc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new aa763cf2aac 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 3046a5270a9 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 9d93b8fa3e8 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new ce08332517c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 69d5db9e2fd 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 7460a826a6f 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new afbff676ac5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 49c88743b8b 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 17729f16a1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d1f4bd5c1fb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b298c881365 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 5d7a709f2a1 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 5835cfcce1c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 95cf83f2a9e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 37cfa395c26 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a5f71ebef13 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new a8c9fba7964 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new adc4983f0fb 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c5a720773da 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f49c804000e 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new fac3770cb6a 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new fc54861cbd5 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new af9cfa355a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 27c38271962 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new df2ed6d544d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new a530a7807ea 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 7a432d64974 212: force: #24: 1: Success after binutils: 2 commits new c33ddc2dedf 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (d23fc64eb8c) \ 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 1748 -> 1948 bytes 02-prepare_abe/console.log.xz | Bin 3468 -> 3456 bytes 03-build_abe-binutils/console.log.xz | Bin 39052 -> 39456 bytes 04-build_abe-gcc/console.log.xz | Bin 204252 -> 204556 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 244500 -> 244016 bytes 08-build_abe-gdb/console.log.xz | Bin 39216 -> 39332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3808 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2200 -> 2608 bytes 11-check_regression/console.log.xz | Bin 3060 -> 4200 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 21 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.regressions | 19 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1085 ++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 21 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 19 + sumfiles/binutils.log.xz | Bin 62956 -> 62924 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83944 -> 83964 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122252 -> 122428 bytes sumfiles/ld.sum | 6 +- 39 files changed, 1239 insertions(+), 48 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

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

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 cd7a377b Add entry 2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b from https [...] new f659d5f3 Add entry 2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../{master-arm => master-aarch64}/build_url | 2 +- .../{master-arm => master-aarch64}/last_good | 0 .../{master-arm => master-aarch64}/summary.txt | 0 .../tcwg_gnu_native_check_binutils/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu_native_check_ [...] copy binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu_native_check_ [...] copy binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b/tcwg_gnu_native_check_ [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017rate/gnu-arm-master-Os_LTO updated (373339a11e7 -> bb3f440df50)

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-cpu2017rate/gnu-arm-master-Os_LTO in repository toolchain/ci/base-artifacts. from 373339a11e7 1: onsuccess: #2: 1: [TCWG CI] No change after binutils/gcc [...] new bb3f440df50 2: onsuccess: #3: 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 1816 -> 1836 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 3464 bytes 03-build_abe-binutils/console.log.xz | Bin 31036 -> 31604 bytes 04-build_abe-stage1/console.log.xz | Bin 90816 -> 91736 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 237488 -> 238268 bytes 08-build_abe-stage2/console.log.xz | Bin 214496 -> 215660 bytes 09-benchmark/benchmark-build.log | 120 ++- 09-benchmark/benchmark.log | 118 ++- 09-benchmark/console.log.xz | Bin 4172 -> 4052 bytes .../compare-results-vs-first-internal.csv | 58 +- .../compare-results-vs-prev-internal.csv | 58 +- 10-check_regression/console.log.xz | Bin 7364 -> 9000 bytes .../csv-results-vs-first-1/perf.csv | 130 +-- .../csv-results-vs-first-1/results.csv | 153 ++-- .../csv-results-vs-first-1/size.csv | 10 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 128 +-- .../csv-results-vs-prev-0/results.csv | 339 ++++---- 10-check_regression/csv-results-vs-prev-0/size.csv | 240 +++--- 10-check_regression/csv-results-vs-prev-1/perf.csv | 130 +-- .../csv-results-vs-prev-1/results.csv | 153 ++-- 10-check_regression/csv-results-vs-prev-1/size.csv | 10 +- .../output-bmk-results/error_code-1 | 0 .../output-bmk-results/exe.regression | 8 + .../output-bmk-results/exe.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 50 +- 10-check_regression/results-vs-first-full.csv | 140 ++-- 10-check_regression/results-vs-first-internal.csv | 58 +- 10-check_regression/results-vs-first.csv | 58 +- 10-check_regression/results-vs-first.log | 796 +++++++++---------- 10-check_regression/results-vs-prev-brief.csv | 50 +- 10-check_regression/results-vs-prev-compare.csv | 2 +- 10-check_regression/results-vs-prev-full.csv | 146 ++-- 10-check_regression/results-vs-prev-internal.csv | 58 +- 10-check_regression/results-vs-prev.csv | 58 +- 10-check_regression/results-vs-prev.log | 878 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metrics.json | 2 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 16 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 16 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../squad-vs-first/519.lbm_r/results-metrics.json | 2 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../squad-vs-first/525.x264_r/results-metrics.json | 2 +- .../527.cam4_r/results-metadata.json | 16 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 16 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../548.exchange2_r/results-metadata.json | 16 +- .../548.exchange2_r/results-metrics.json | 2 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metrics.json | 2 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 86 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 45 +- mail/mail-body.txt | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 87 files changed, 2279 insertions(+), 2271 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/error_code-1 create mode 100644 10-check_regression/output-bmk-results/exe.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (bc582daf85d -> 6dcd555a552)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards bc582daf85d 616: onsuccess: #40: 2: Success after binutils/gcc: 19 commits discards fc0e6025d46 615: onsuccess: #39: 2: Success after binutils/gcc: 19 commits discards b2038a44670 614: onsuccess: #38: 2: Success after binutils/gcc: 32 commits discards 22194cd1aec 613: onsuccess: #37: 2: Success after binutils/gcc: 24 commits discards 17ceb496694 612: onsuccess: #36: 2: Success after binutils/gcc: 37 commits discards 84762ca41c1 611: onsuccess: #35: 2: Success after binutils/gcc: 5 commits discards e7559957819 610: onsuccess: #34: 2: Success after gcc: 8 commits discards a68b9475055 609: onsuccess: #33: 2: Success after binutils/gcc: 7 commits discards 975d3f00378 608: onsuccess: #32: 2: Success after binutils/gcc: 8 commits discards b7d73b3b996 607: onsuccess: #31: 2: Success after binutils/gcc: 6 commits discards 2ebca074e40 606: onsuccess: #30: 2: Success after binutils/gcc: 43 commits discards 0f18e4241c6 605: onsuccess: #29: 2: Success after binutils/gcc: 13 commits discards 13ac83267a4 604: onsuccess: #28: 2: Success after binutils/gcc: 23 commits discards 9611f722986 603: onsuccess: #27: 2: Success after binutils/gcc: 12 commits discards 3f70ba8a6f1 602: onsuccess: #26: 2: Success after binutils/gcc: 4 commits discards e256c049a46 601: onsuccess: #25: 2: Success after binutils/gcc: 18 commits discards 0732239a3a5 600: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards 5d22b1a1d6a 599: onsuccess: #23: 2: Success after binutils/gcc: 27 commits discards 3533d430cc0 598: onsuccess: #22: 2: Success after binutils/gcc: 14 commits discards ff2bc6b253a 597: onsuccess: #21: 2: Success after binutils/gcc: 13 commits discards 1e060fc3871 596: onsuccess: #20: 2: Success after gcc: 8 commits discards de32ca978f9 595: onsuccess: #19: 2: Success after binutils/gcc: 10 commits discards 6186a355a34 594: onsuccess: #18: 2: Success after gcc: 4 commits discards 06e6f615d06 593: onsuccess: #17: 2: Success after binutils/gcc: 13 commits discards 491870ae6c0 592: onsuccess: #16: 2: Success after binutils/gcc: 30 commits discards ef3f2f0dc0c 591: onsuccess: #15: 2: Success after binutils/gcc: 23 commits discards 94419d8a37c 590: onsuccess: #14: 2: Success after binutils/gcc: 21 commits discards 81cc819fc88 589: onsuccess: #13: 2: Success after binutils/gcc: 17 commits discards 6cd9eeea392 588: onsuccess: #12: 2: Success after binutils/gcc: 14 commits discards 0cd7782dd34 587: onsuccess: #11: 2: Success after binutils/gcc: 12 commits discards 61930b18ed9 586: onsuccess: #10: 2: Success after binutils/gcc: 23 commits discards d8d2fc4b583 585: onsuccess: #9: 2: Success after binutils/gcc: 23 commits discards c0f0f94dcdf 584: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 192ab5cbc45 583: onsuccess: #7: 2: Success after binutils/gcc: 4 commits discards e2b53b20e2a 582: onsuccess: #6: 2: Success after binutils/gcc: 3 commits discards 100b6de5507 581: onsuccess: #5: 2: Success after binutils/gcc: 2 commits discards 35d9eea1ff7 580: onsuccess: #4: 2: Success after gcc: 7 commits discards 1dc75d84ea2 579: onsuccess: #3: 2: Success after binutils/gcc: 3 commits discards 57d9261bcf9 578: onsuccess: #2: 2: Success after binutils/gcc: 42 commits discards 14af704fb70 577: onsuccess: #1: 2: Success after binutils/gcc: 5 commits discards 38023b57677 576: onsuccess: #2020: 2: Success after binutils/gcc: 35 commits discards 2fa2b604c14 575: onsuccess: #2019: 2: Success after binutils/gcc: 19 commits discards 7c16d4eabe5 574: onsuccess: #2018: 2: Success after binutils/gcc: 21 commits discards 0d502d4ed7a 573: onsuccess: #2017: 2: Success after binutils/gcc: 15 commits discards 8b7da12407a 572: onsuccess: #2016: 2: Success after binutils/gcc: 124 commits discards 4a7016c9e57 571: onsuccess: #2015: 2: Success after binutils/gcc: 11 commits discards cca1059dbb8 570: onsuccess: #2014: 2: Success after binutils/gcc: 11 commits discards 77b80e88328 569: onsuccess: #2013: 2: Success after basepoints/gcc-13-6 [...] discards 6becfbd04db 568: onsuccess: #2012: 2: Success after binutils/gcc: 31 commits discards 640611da126 567: onsuccess: #2011: 2: Success after binutils: 2 commits discards 07d8c607721 566: onsuccess: #2010: 2: Success after binutils/gcc: 4 commits discards ff814b3720b 565: onsuccess: #2009: 2: Success after gcc: 7 commits discards 205349f45c9 564: onsuccess: #2008: 2: Success after binutils/gcc: 13 commits discards e5eae818285 563: onsuccess: #2007: 2: Success after binutils/gcc: 5 commits discards ba1ceb58484 562: onsuccess: #2006: 2: Success after gcc: 4 commits discards 89dc405775d 561: onsuccess: #2005: 2: Success after binutils/gcc: 12 commits discards 3961d7c74c6 560: onsuccess: #2004: 2: Success after binutils/gcc: 5 commits discards 359d47f9370 559: onsuccess: #2003: 2: Success after binutils: 2 commits discards 185bf31fc39 558: onsuccess: #2002: 2: Success after binutils/gcc: 22 commits discards 2ee5b5feba2 557: onsuccess: #2001: 2: Success after binutils/gcc: 118 commits discards b0395b86b39 556: onsuccess: #2000: 2: Success after binutils/gcc: 36 commits discards 241aa6c2998 555: onsuccess: #1999: 2: Success after binutils/gcc: 92 commits discards 1f59ab5242c 554: onsuccess: #1998: 2: Success after binutils/gcc: 145 commits discards e8db65b94d6 553: onsuccess: #1997: 2: Success after binutils/gcc: 12 commits discards bd7df620ec7 552: onsuccess: #1996: 2: Success after binutils/gcc: 17 commits discards cff6c5c04df 551: onsuccess: #1995: 2: Success after binutils/gcc: 62 commits discards 962d46f8147 550: onsuccess: #1994: 2: Success after binutils/gcc: 21 commits discards ab581b94101 549: onsuccess: #1992: 2: Success after binutils/gcc: 41 commits discards db77444dd0c 548: onsuccess: #1991: 2: Success after binutils/gcc: 14 commits discards 209ad424249 547: onsuccess: #1990: 2: Success after binutils/gcc: 22 commits discards 0e0ee18b8b6 546: onsuccess: #1989: 2: Success after binutils/gcc: 6 commits discards 7748621bc81 545: onsuccess: #1988: 2: Success after binutils/gcc: 8 commits discards 45cfa4b2dde 544: onsuccess: #1987: 2: Success after binutils/gcc: 45 commits discards 94858e99bbc 543: onsuccess: #1986: 2: Success after binutils/gcc: 49 commits discards 70f54493f8b 542: onsuccess: #1985: 2: Success after binutils/gcc: 39 commits discards f854604cf1f 541: onsuccess: #1984: 2: Success after binutils/gcc: 98 commits discards f09faf22f98 540: onsuccess: #1983: 2: Success after binutils/gcc: 49 commits discards 90c4ef59ea5 539: onsuccess: #1982: 2: Success after binutils/gcc: 5 commits discards 7a490270b4c 538: onsuccess: #1981: 2: Success after binutils/gcc: 14 commits discards 1b196d39d5c 537: onsuccess: #1980: 2: Success after binutils/gcc: 54 commits discards 30f796226d5 536: onsuccess: #1979: 2: Success after binutils/gcc: 109 commits discards c7824184f75 535: onsuccess: #1978: 2: Success after binutils/gcc: 68 commits discards ec4a453e09f 534: onsuccess: #1977: 2: Success after binutils/gcc: 27 commits discards 466f955c493 533: onsuccess: #1976: 2: Success after binutils/gcc: 45 commits discards 8d3b136f6ee 532: onsuccess: #1975: 2: Success after binutils/gcc: 11 commits discards 11377085f73 531: onsuccess: #1974: 2: Success after binutils/gcc: 5 commits discards d763c1db069 530: onsuccess: #1973: 2: Success after binutils/gcc: 39 commits discards 54f82e75bcc 529: onsuccess: #1972: 2: Success after binutils/gcc: 17 commits discards 9c0a1719cde 528: onsuccess: #1971: 2: Success after binutils/gcc: 31 commits discards f2b4610e280 527: onsuccess: #1970: 2: Success after binutils/gcc: 11 commits discards 26fff374959 526: onsuccess: #1969: 2: Success after binutils/gcc: 20 commits discards dd65a49a84b 525: onsuccess: #1968: 2: Success after binutils/gcc: 45 commits discards 6185b06441d 524: onsuccess: #1967: 2: Success after binutils/gcc: 47 commits discards e89e91cd6c8 523: onsuccess: #1966: 2: Success after binutils/gcc: 113 commits discards 010a06b32a9 522: onsuccess: #1965: 2: Success after binutils/gcc: 49 commits discards da42ff90c2d 521: onsuccess: #1964: 2: Success after binutils/gcc: 24 commits discards 0a2ded57fc5 520: onsuccess: #1963: 2: Success after binutils/gcc: 19 commits discards 8906c92c33c 519: onsuccess: #1962: 2: Success after binutils/gcc: 97 commits discards e2f7bc7ff9d 518: onsuccess: #1961: 2: Success after binutils/gcc: 18 commits discards 835f6629e30 517: onsuccess: #1959: 2: Success after basepoints/gcc-13-5 [...] discards a65f909f545 516: onsuccess: #1958: 2: Success after binutils/gcc: 3 commits new 3bc64d02eff 516: onsuccess: #1958: 2: Success after binutils/gcc: 3 commits new b59950d9344 517: onsuccess: #1959: 2: Success after basepoints/gcc-13-5 [...] new 7d32f90ebef 518: onsuccess: #1961: 2: Success after binutils/gcc: 18 commits new bfd14674f15 519: onsuccess: #1962: 2: Success after binutils/gcc: 97 commits new c6b266b7076 520: onsuccess: #1963: 2: Success after binutils/gcc: 19 commits new 112b1ebdeb9 521: onsuccess: #1964: 2: Success after binutils/gcc: 24 commits new 93efc037ee2 522: onsuccess: #1965: 2: Success after binutils/gcc: 49 commits new a3cd28b8767 523: onsuccess: #1966: 2: Success after binutils/gcc: 113 commits new 4abdc2998d2 524: onsuccess: #1967: 2: Success after binutils/gcc: 47 commits new cb33fee296b 525: onsuccess: #1968: 2: Success after binutils/gcc: 45 commits new 880339fa37c 526: onsuccess: #1969: 2: Success after binutils/gcc: 20 commits new c20dc7f7a48 527: onsuccess: #1970: 2: Success after binutils/gcc: 11 commits new 88c9ae4ed33 528: onsuccess: #1971: 2: Success after binutils/gcc: 31 commits new a28a1ff11db 529: onsuccess: #1972: 2: Success after binutils/gcc: 17 commits new e8c20086e8c 530: onsuccess: #1973: 2: Success after binutils/gcc: 39 commits new 0de134346ba 531: onsuccess: #1974: 2: Success after binutils/gcc: 5 commits new cf6b6ae3f98 532: onsuccess: #1975: 2: Success after binutils/gcc: 11 commits new 9edac306419 533: onsuccess: #1976: 2: Success after binutils/gcc: 45 commits new 64c3218cdbd 534: onsuccess: #1977: 2: Success after binutils/gcc: 27 commits new c48fffd8875 535: onsuccess: #1978: 2: Success after binutils/gcc: 68 commits new 9d1a3049445 536: onsuccess: #1979: 2: Success after binutils/gcc: 109 commits new ec74bd5cad7 537: onsuccess: #1980: 2: Success after binutils/gcc: 54 commits new b26dfed0f49 538: onsuccess: #1981: 2: Success after binutils/gcc: 14 commits new 62923c22441 539: onsuccess: #1982: 2: Success after binutils/gcc: 5 commits new 106ba6156ca 540: onsuccess: #1983: 2: Success after binutils/gcc: 49 commits new 26de5b07bff 541: onsuccess: #1984: 2: Success after binutils/gcc: 98 commits new 3b891018226 542: onsuccess: #1985: 2: Success after binutils/gcc: 39 commits new 8cf1b7228ff 543: onsuccess: #1986: 2: Success after binutils/gcc: 49 commits new 17e2fbcc160 544: onsuccess: #1987: 2: Success after binutils/gcc: 45 commits new cacbfdd7abf 545: onsuccess: #1988: 2: Success after binutils/gcc: 8 commits new 31816c1e661 546: onsuccess: #1989: 2: Success after binutils/gcc: 6 commits new 40910afe527 547: onsuccess: #1990: 2: Success after binutils/gcc: 22 commits new 38d6c552f96 548: onsuccess: #1991: 2: Success after binutils/gcc: 14 commits new 351872892a9 549: onsuccess: #1992: 2: Success after binutils/gcc: 41 commits new f11f06273be 550: onsuccess: #1994: 2: Success after binutils/gcc: 21 commits new e347f7a0c0b 551: onsuccess: #1995: 2: Success after binutils/gcc: 62 commits new f3fa1ddc26c 552: onsuccess: #1996: 2: Success after binutils/gcc: 17 commits new 1bcc75c850f 553: onsuccess: #1997: 2: Success after binutils/gcc: 12 commits new 03abf26ca8f 554: onsuccess: #1998: 2: Success after binutils/gcc: 145 commits new 02a386dff8c 555: onsuccess: #1999: 2: Success after binutils/gcc: 92 commits new 3076c9215ee 556: onsuccess: #2000: 2: Success after binutils/gcc: 36 commits new d043e34075e 557: onsuccess: #2001: 2: Success after binutils/gcc: 118 commits new 8e6627a728d 558: onsuccess: #2002: 2: Success after binutils/gcc: 22 commits new 9ad55691a9e 559: onsuccess: #2003: 2: Success after binutils: 2 commits new 785e343e000 560: onsuccess: #2004: 2: Success after binutils/gcc: 5 commits new f2ea69b4fb2 561: onsuccess: #2005: 2: Success after binutils/gcc: 12 commits new bf8c4df2b32 562: onsuccess: #2006: 2: Success after gcc: 4 commits new d40a73f9621 563: onsuccess: #2007: 2: Success after binutils/gcc: 5 commits new 5f98a0e81ba 564: onsuccess: #2008: 2: Success after binutils/gcc: 13 commits new 15d61769951 565: onsuccess: #2009: 2: Success after gcc: 7 commits new 1746de50ca6 566: onsuccess: #2010: 2: Success after binutils/gcc: 4 commits new a585a47e140 567: onsuccess: #2011: 2: Success after binutils: 2 commits new d0d67aee7ea 568: onsuccess: #2012: 2: Success after binutils/gcc: 31 commits new 93543920b9e 569: onsuccess: #2013: 2: Success after basepoints/gcc-13-6 [...] new 3ece3026642 570: onsuccess: #2014: 2: Success after binutils/gcc: 11 commits new 438172abf2f 571: onsuccess: #2015: 2: Success after binutils/gcc: 11 commits new 0bf339fe018 572: onsuccess: #2016: 2: Success after binutils/gcc: 124 commits new f7086847bb7 573: onsuccess: #2017: 2: Success after binutils/gcc: 15 commits new 1cf272710e7 574: onsuccess: #2018: 2: Success after binutils/gcc: 21 commits new fc24ac4f128 575: onsuccess: #2019: 2: Success after binutils/gcc: 19 commits new 67e944c9b4d 576: onsuccess: #2020: 2: Success after binutils/gcc: 35 commits new 27ffdbbcf25 577: onsuccess: #1: 2: Success after binutils/gcc: 5 commits new aac52f319cc 578: onsuccess: #2: 2: Success after binutils/gcc: 42 commits new e9f5f0018f6 579: onsuccess: #3: 2: Success after binutils/gcc: 3 commits new 0a02e4bfffc 580: onsuccess: #4: 2: Success after gcc: 7 commits new cce30d96f86 581: onsuccess: #5: 2: Success after binutils/gcc: 2 commits new f1ea33428df 582: onsuccess: #6: 2: Success after binutils/gcc: 3 commits new c5aca77eb89 583: onsuccess: #7: 2: Success after binutils/gcc: 4 commits new 52b43c48988 584: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new 9d9f16eadd2 585: onsuccess: #9: 2: Success after binutils/gcc: 23 commits new c0aa43caa1f 586: onsuccess: #10: 2: Success after binutils/gcc: 23 commits new 9eff31d187a 587: onsuccess: #11: 2: Success after binutils/gcc: 12 commits new 56679d84b9c 588: onsuccess: #12: 2: Success after binutils/gcc: 14 commits new 61e306180cb 589: onsuccess: #13: 2: Success after binutils/gcc: 17 commits new 660e647a496 590: onsuccess: #14: 2: Success after binutils/gcc: 21 commits new 5f23270a901 591: onsuccess: #15: 2: Success after binutils/gcc: 23 commits new 3cf6bb5e184 592: onsuccess: #16: 2: Success after binutils/gcc: 30 commits new 3892d794ade 593: onsuccess: #17: 2: Success after binutils/gcc: 13 commits new f8293c3b115 594: onsuccess: #18: 2: Success after gcc: 4 commits new feacbed4b50 595: onsuccess: #19: 2: Success after binutils/gcc: 10 commits new 5d2f14c6943 596: onsuccess: #20: 2: Success after gcc: 8 commits new 514927759bb 597: onsuccess: #21: 2: Success after binutils/gcc: 13 commits new f397b6b70ed 598: onsuccess: #22: 2: Success after binutils/gcc: 14 commits new 8dee26a5b3c 599: onsuccess: #23: 2: Success after binutils/gcc: 27 commits new d6d6e10ae38 600: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new e53f1384fa9 601: onsuccess: #25: 2: Success after binutils/gcc: 18 commits new 385473fdb8c 602: onsuccess: #26: 2: Success after binutils/gcc: 4 commits new 76a790c5f5a 603: onsuccess: #27: 2: Success after binutils/gcc: 12 commits new 93dec6b32d2 604: onsuccess: #28: 2: Success after binutils/gcc: 23 commits new f21ca670746 605: onsuccess: #29: 2: Success after binutils/gcc: 13 commits new 371ff0444f8 606: onsuccess: #30: 2: Success after binutils/gcc: 43 commits new fe3f2f49dd7 607: onsuccess: #31: 2: Success after binutils/gcc: 6 commits new e0b5658b54f 608: onsuccess: #32: 2: Success after binutils/gcc: 8 commits new 0520c08741c 609: onsuccess: #33: 2: Success after binutils/gcc: 7 commits new 4e7e8097e84 610: onsuccess: #34: 2: Success after gcc: 8 commits new d7142895401 611: onsuccess: #35: 2: Success after binutils/gcc: 5 commits new fa7af1ff10a 612: onsuccess: #36: 2: Success after binutils/gcc: 37 commits new ae94c3fbafc 613: onsuccess: #37: 2: Success after binutils/gcc: 24 commits new f6ba65a3bc4 614: onsuccess: #38: 2: Success after binutils/gcc: 32 commits new 7f5f53af2c2 615: onsuccess: #39: 2: Success after binutils/gcc: 19 commits new dca0e90dc9b 616: onsuccess: #40: 2: Success after binutils/gcc: 19 commits new 6dcd555a552 617: onsuccess: #41: 2: Success after binutils/gcc: 15 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 (bc582daf85d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1744 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 3448 -> 3464 bytes 04-build_abe-binutils/console.log.xz | Bin 38916 -> 39384 bytes 05-build_abe-bootstrap/console.log.xz | Bin 262756 -> 263016 bytes 06-check_regression/console.log.xz | Bin 3096 -> 3040 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 +++++++++--------- 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (eea3f522797 -> 70c90fd2e44)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards eea3f522797 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 9a9cc9e2998 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 7697e87f25e 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 2f2b35bf7a7 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards d6078f5c3e7 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 21ea48d59fd 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 71cd68996e6 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 547feecf2fc 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards d8f8cf02098 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0c37d65c2a2 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards e3f89edccd0 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e7fa3afc7e0 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9bc06512d4b 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 113168c442d 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 35a5fe732b9 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d26b80fe3b8 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e361a323d3c 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e69f64d03d8 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 71b001a35b8 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards ac19828af38 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8bcb5383a15 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 3d4c42f8815 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 535f1129d44 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 44f75c3d6d1 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 7fda361afab 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 0c5f33918cd 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 765942fed1e 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards be98d420687 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 04a9ae29ace 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 409b123d1ac 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 66be085a5e4 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards ab024495d2e 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 23fedb0b7c2 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 3fe98e9a8fe 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 3c5b0e15138 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 51dcec1f28d 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 8aa2db60ed6 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 863b2c9ff39 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 4829544ba09 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards d35e10638c0 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards c4bc1727abc 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards ceab685939c 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 4eb546dbf5e 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 4874a4f94b9 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 306966820d2 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 1e20aa82bd5 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 7541f593e6d 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards decff2b3c6d 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 224e69b4082 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards b1fdabfec6f 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 28a0e612f90 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards af9ad9d21fc 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 2063b01016c 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards a8b8b8258b6 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards e8c6b0f66cd 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 40cb708d69f 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards b027f4a7dfe 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards d3014b625b9 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 6585bda02c6 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 5f0b84902b3 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 3fb773c1580 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards d28baf34705 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 60f9e54f534 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 985d58dd5ea 152: onsuccess: #903: 1: Success after linux: 22 commits discards 37e33c093be 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 7c591933de9 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 23b58c148a1 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 116e4ec9574 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards ee8ea5a92e4 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 7cc33050930 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards ae1b882fc87 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 40b78cfba4c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 3cd5fda920b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 004e5aa0815 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 1606f5dc671 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 196d8a9e6c7 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 001ccbc1264 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 9a9e2d34b70 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 27621b9f849 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 451abf3e419 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 6b3bf6c5850 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards af34fe5625f 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 2572a0675ed 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 7b45cde994a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards ddfc5f91eaa 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 7654cfddf95 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 2013078e46a 129: onsuccess: #878: 1: Success after linux: 3008 commits discards ba6820d0f30 128: onsuccess: #876: 1: Success after binutils: 12 commits discards d9583e73f54 127: onsuccess: #874: 1: Success after linux: 219 commits discards 78cc015b72f 126: onsuccess: #873: 1: Success after glibc: 2 commits discards ad9318fcc88 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 6e5802904ec 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 9e021fbadc6 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards a591c7a1387 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards c378048b444 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards edf9a351d8d 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 2b254d6e5cf 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 7727b186c8e 118: onsuccess: #863: 1: Success after linux: 12 commits discards 77450ac8d3f 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 7451b8f7e28 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 2dcc8a81913 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 620420e4fe3 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new fca174bb94c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 0d566b8d81a 117: onsuccess: #861: 1: Success after binutils: 18 commits new 42bde7837e7 118: onsuccess: #863: 1: Success after linux: 12 commits new 175af3b6ab3 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 045c2fc634b 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 99fa8b52b33 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new a355178a51b 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 0c7a76c38df 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 269d07748ed 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 4aca6cdc089 125: onsuccess: #871: 1: Success after binutils: 26 commits new b5ea0719085 126: onsuccess: #873: 1: Success after glibc: 2 commits new 9cfd97cc066 127: onsuccess: #874: 1: Success after linux: 219 commits new 17b1791f22c 128: onsuccess: #876: 1: Success after binutils: 12 commits new 8dc8820d522 129: onsuccess: #878: 1: Success after linux: 3008 commits new c67f6c81caa 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 18978993849 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new c2acc8b7960 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 5da685f53e4 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 8ee99ca1ce8 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 437d3c11b7f 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new fdb4f687cfb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new d3d0e03cc75 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 919868ce244 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new a37e76f0614 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new d03f0992220 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 918031c11f7 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new d5233fd50a7 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new e24a8501a53 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 73bcbf546bd 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 123cf354bb7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 2b224bb2b6b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new c60efb3d31a 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 67eee476656 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 2e3fb7316bd 149: onsuccess: #899: 1: Success after binutils: 15 commits new 2e5f6a6676c 150: onsuccess: #900: 1: Success after gcc: 11 commits new 597bddef481 151: onsuccess: #902: 1: Success after glibc: 8 commits new 9c99e6b6416 152: onsuccess: #903: 1: Success after linux: 22 commits new 34d57cc55a3 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 7e962a10fb4 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 29861806368 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 2ad11d2bd8f 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new dd6514f31d2 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 09bd5a0dcdc 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 51e3df69586 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 408a7ec0ae6 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 5230d30a0c7 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new e4057d10d4a 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 08e5b90db90 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 8d0a6c4bdb3 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new dd0ab66cd95 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 3995eebe51f 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new a9618718e8b 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 1347c4cfb32 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new a157be169c5 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 2402e1b00cd 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 64ef754c41b 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new a79aac27e7c 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 4b071039391 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 781914b3eee 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 828551ad315 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new ba9e373971e 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 424cad60937 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 3f09e35e2ec 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4f961c08229 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 4f131cbe6a2 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 19bfc325240 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 5dded805d97 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 6536bda1370 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 3e119696413 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 2bb789c4ff3 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 693415cb464 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new e820c83914d 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 6b050bc40e4 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new e2d1dc6f9fc 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 488b8e2faa9 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 81cc23e7a70 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 8eb693939a3 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 9ec78ec9885 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new beb3f600360 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 16aec4efe26 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new c4dc31b2f33 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f15f9b1655b 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ed8ebad5d73 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a6585005bc1 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 602a5cb86c4 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d378abc5250 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8703393d6e3 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e88a7772182 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e2ba479e95f 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 46bb73efbb1 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 1dfaf4b1357 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new f660a0761fc 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3096966845c 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new ae2eb7d023c 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new a73ab44a643 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c6a8faa8a47 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 4f39e57dc7f 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c5f8ecccc65 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new a1d30d36841 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 0be3119bf2e 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 70c90fd2e44 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (eea3f522797) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1832 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 3436 bytes 03-build_abe-binutils/console.log.xz | Bin 38824 -> 39272 bytes 04-build_abe-gcc/console.log.xz | Bin 204900 -> 205432 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9064 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 245900 -> 246684 bytes 08-build_abe-gdb/console.log.xz | Bin 38388 -> 39036 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3812 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2692 -> 9572 bytes 11-check_regression/console.log.xz | Bin 7408 -> 6112 bytes 11-check_regression/results.compare | 32 +- 11-check_regression/results.compare2 | 273 +- 12-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 | 34 +- sumfiles/g++.log.sep.xz | Bin 0 -> 67848 bytes sumfiles/g++.log.xz | Bin 3682944 -> 3694464 bytes sumfiles/g++.sum | 163 +- sumfiles/g++.sum.sep | 5094 +++++++++++++++++++++++++++++++++ sumfiles/gcc.log.sep.xz | Bin 0 -> 86276 bytes sumfiles/gcc.log.xz | Bin 3229688 -> 3207656 bytes sumfiles/gcc.sum | 432 +-- sumfiles/gcc.sum.sep | 2684 +++++++++++++++++ sumfiles/gfortran.log.sep.xz | Bin 0 -> 21328 bytes sumfiles/gfortran.log.xz | Bin 1081712 -> 1086252 bytes sumfiles/gfortran.sum | 44 +- sumfiles/gfortran.sum.sep | 1332 +++++++++ sumfiles/libatomic.log.xz | Bin 2296 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235400 -> 235544 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2680 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.sep.xz | Bin 0 -> 19096 bytes sumfiles/libstdc++.log.xz | Bin 446320 -> 444864 bytes sumfiles/libstdc++.sum | 8 +- sumfiles/libstdc++.sum.sep | 31 + 45 files changed, 9753 insertions(+), 482 deletions(-) create mode 100644 sumfiles/g++.log.sep.xz create mode 100644 sumfiles/g++.sum.sep create mode 100644 sumfiles/gcc.log.sep.xz create mode 100644 sumfiles/gcc.sum.sep create mode 100644 sumfiles/gfortran.log.sep.xz create mode 100644 sumfiles/gfortran.sum.sep create mode 100644 sumfiles/libstdc++.log.sep.xz create mode 100644 sumfiles/libstdc++.sum.sep -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (8fc752f4a7f -> d23fc64eb8c)

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 8fc752f4a7f 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 6e29ca0aacb 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c4671904831 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards fe877fde434 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 389dd206062 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 4844673247c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards af4a79973c9 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4e16e917e1b 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e43cfd5a8f1 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 816da92c5ad 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 71ef8715419 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 20db68e578a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bbd90fe1da4 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7fc2377602e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 69ec791e373 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards da8a8f64d1a 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f226ba89553 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 11463fbca1f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards d36ea1ea08f 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 2c08910eb84 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 483a126dcf2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards cedffcb76ef 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 26d7de5eee1 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards d5a4c481d36 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 535d872abf5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 914107ba15e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 336345dbee6 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards ec787a19098 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 91eeabdc936 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 06823571ed6 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards e150e6a60d9 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 73e550d7bb3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards c4cc654f216 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards e4399ef1f27 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards bac75dba64b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 1fdf69f746c 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 9850111eb3e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards ad5b8befc9d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 0e53beff629 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 0c681492c18 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards e228d83656a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards b81e68889e1 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 1b62a037602 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 46f3eba0a1a 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards cd65dac47da 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 56f6a48e588 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards e0dfc9dc128 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 3401a7e39a7 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards ef21c1e1124 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards ef181f5049e 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 3b259478351 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards dbe9e257065 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards a9729f54ba8 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 2f3786b8451 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 0ddc4d6b50c 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards e1dba2bdd66 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards de788c83b09 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 839d55420dc 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 0ad01e52d32 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 488dd1f84c7 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards cf8a827e66b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 68e7599faa1 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards eecdfe721c8 149: onsuccess: #684: 1: Success after linux: 10 commits discards cea081b7c76 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 5a8e1f6afb1 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 78957721937 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 077fc89a5ce 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 4a6b0422a7e 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 95d6b98eac0 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 19f60ebcdc9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards d5836656c91 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 52f68b2aa83 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards aa25579c0d5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 73f97305c78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 1d60c1c86f4 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 552b89547a3 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 2bf408ec596 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 63deda6d649 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 99c60f3e158 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 62bf32abc62 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards cabaf79a1cf 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards bd8d0a8507e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 1058829ca9d 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6efd84e0d13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards a663192d15f 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5028611a72c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards dd8e83f5343 125: onsuccess: #658: 1: Success after linux: 3224 commits discards fa455300ce1 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 43dca4c83ec 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 2c53acf8866 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 771c964a31d 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 0cd6b4485b4 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 6c31814f27f 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d15dab9ac58 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 96c83646e18 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 2debe2f1360 116: onsuccess: #647: 1: Success after linux: 3 commits discards c720e550082 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 3968e2a12be 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards d00a674cb21 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 91a724754b1 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards df97b734f88 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 999ec8d79aa 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new dcbdab3a058 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 890843da2b2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new af6f1a6c701 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new e71a85dc0eb 115: onsuccess: #645: 1: Success after binutils: 27 commits new 3d5c6e260d5 116: onsuccess: #647: 1: Success after linux: 3 commits new 4d7cf2ad040 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new a947f6736e5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7a75dea3d2b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4e7633f22af 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new da9214d5b3f 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ce81bcc2498 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 67cf3e9f5f5 123: onsuccess: #655: 1: Success after binutils: 22 commits new fca17e32a2b 124: onsuccess: #657: 1: Success after glibc: 2 commits new 711180fb93d 125: onsuccess: #658: 1: Success after linux: 3224 commits new 7c735ce988f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 80bb862f25a 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9193b2345f0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 8f93da18fdb 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 7cb72c85f73 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 1353807f14b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new a71f458c3fa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 4e5d027d446 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 7dd02395b17 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 0cd17dafed5 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 4fb63b715ca 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new bd69f3d7f9a 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 738254df701 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 8e6ceb6d505 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new d97848c944a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new c4f9983aa57 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new b37a6f3fa7e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new fb9d574eb02 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 7d5d99cc8b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 1defbe9eb61 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ec590be6ae6 146: onsuccess: #680: 1: Success after binutils: 20 commits new fd8995bd76d 147: onsuccess: #681: 1: Success after gcc: 6 commits new d5fd0c98213 148: onsuccess: #683: 1: Success after glibc: 9 commits new 4b85f6b8dd9 149: onsuccess: #684: 1: Success after linux: 10 commits new e0cdc06ceae 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new f411babb411 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 880ffacdc76 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new cc0cbf52192 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 64e8c9006c8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new e6c56bf7dbf 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new d25f99a292f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 9c98c7c9d34 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new afe7988a0c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new be2fc8ad262 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new e929e7f5826 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3a227ecc9b5 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 8eac1321f28 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 258bd3b63e6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 32cbf082a56 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 3e58e1c8b81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 8f7de082f91 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new c5a637e41a3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 36bf25527d2 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 25c0051a4e0 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new ca07a678831 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new d8ccc02ab41 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new e80882aa849 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new c822e673451 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 49862106505 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 4e77618cda6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 841350e3f62 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 6d7e17575a9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new d9898c420f7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 0d287d2e855 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 894e8bbeff5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 77d39ce378b 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 1cd67853286 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new c442ed3cb4a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 8a15eb53173 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 1d006334e80 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new d0be0916d20 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 571100967a2 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new f89b7876728 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new de633a93e5d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 9e3a7868daf 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 4f44dd829be 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 032e8dc0616 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 0a75f26d30c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 353096743a4 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ded5d13d6f3 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2387b97c180 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 849a6126ceb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e29e16536ab 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 88ecec7b88e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 09e4d4601a1 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e2053fe5cf9 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new dcb958ed0a6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1c82456e5ac 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new ba03dee73b4 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b539d0bd059 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new dadfb86f0d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e8635e71b05 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 46ba31c02aa 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new cc5da72c581 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 70ce1e38067 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 641d032472e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new d23fc64eb8c 212: force: #24: 1: Success after binutils: 2 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 (8fc752f4a7f) \ 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 1932 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 3536 -> 3468 bytes 03-build_abe-binutils/console.log.xz | Bin 40156 -> 39052 bytes 04-build_abe-gcc/console.log.xz | Bin 204944 -> 204252 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8616 bytes 07-build_abe-glibc/console.log.xz | Bin 244268 -> 244500 bytes 08-build_abe-gdb/console.log.xz | Bin 38952 -> 39216 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3796 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2080 -> 2200 bytes 11-check_regression/console.log.xz | Bin 4416 -> 3060 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 45 +--------------------------- 12-update_baseline/console.log | 46 ++++++++++++++--------------- 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 ++++++------- sumfiles/binutils.log.xz | Bin 62928 -> 62956 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83992 -> 83944 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122228 -> 122252 bytes sumfiles/ld.sum | 2 +- 26 files changed, 46 insertions(+), 91 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023