Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (84ffb4358d -> 2b4e9e9d13)

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 84ffb4358d 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards d22bc12f2b 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards a2819fc021 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards dde4c8f4dd 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards 89b80b7b03 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards 67ee58a4e8 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards 2494f10db1 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 907b524e3c 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 2c23948778 152: onsuccess: #903: 1: Success after linux: 22 commits discards d01a190f19 151: onsuccess: #902: 1: Success after glibc: 8 commits discards a26e6b8f8b 150: onsuccess: #900: 1: Success after gcc: 11 commits discards cf99a26d6c 149: onsuccess: #899: 1: Success after binutils: 15 commits discards c9b4cce780 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 1d66b79d39 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 3a5dd6cd1b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 47c187b842 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 53cd5ce40e 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 31ffa86e3f 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 0271a7e9eb 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 3294b999a5 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 892c54bffa 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards d6215c4db5 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 36e26a30af 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards a6cd90f327 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 4e848c408c 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 5014823936 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards be79160d48 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 5eb52b38dc 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 35f07c984b 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 0d22769553 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards d06198f4c0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards de3f2df5f8 129: onsuccess: #878: 1: Success after linux: 3008 commits discards ed5ccbd84e 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 5e1dbc0218 127: onsuccess: #874: 1: Success after linux: 219 commits discards 1e54d085ee 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 3de80aa386 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 13625f66aa 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 2e3eedaf6f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 1d54685dee 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 4f8de6477e 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 37df0145cb 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards a8cc106a93 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards ec1b08701a 118: onsuccess: #863: 1: Success after linux: 12 commits discards f66f7afaa6 117: onsuccess: #861: 1: Success after binutils: 18 commits discards bae6ad8f8e 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards ebba0fecb2 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 91f6419a5d 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 2caf75372f 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 84abf2b4ab 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 35d5dc2b6e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards e4a43423dd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 0bac4a102a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards c4cf7b8049 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 6b18b7d65d 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 4e728ee1ad 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards c2133fdcc5 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 7110d4bc07 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards a753ab03dd 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 9217517024 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 4b7221bfe3 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards fd83051e55 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 6bb18ac4f1 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards f5fd278f2a 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 69ebb35e9c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 46143a21bc 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 36df8b917c 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 3695c6c89e 94: onsuccess: #832: 1: Success after binutils: 5 commits discards c5efa1dd26 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0fc7de7e72 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 126f7507d2 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards b2c824a866 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 6738f2a5fe 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards b92e954a23 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards f0bd3436f2 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards fc7ac96e8c 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 64f31f16dd 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards a52102953c 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 9255544ef1 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f9e5c401a4 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 8b4fda093e 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7518bd4c36 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 939be685c2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 429e2ab93d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 9c4494b6da 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 540447ab43 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 5a6068cb9d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 45f30c629e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 00699fc745 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 373ea1fbf5 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards dfe3d98dbe 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 9806640fb4 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 23f94a853a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 5808579ba0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards ccda432eeb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 5eec4b7fbc 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards b6513aa82e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards dfff7710db 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards d449e80f62 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 939dd28ef4 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 7cf7ae2019 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 7243210d85 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 2707bc5d8e 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new f064d2abba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 8ef8e16110 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 199a82387c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 67c5d53a90 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 50ef11400d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 779f68d894 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new c95577f810 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new d982ca11ea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 8224b31755 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new b2ddc84c39 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new a91592788a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new c64bc0439c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new c0a07f7818 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 7a9a6af5e4 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 2ef5a41eb7 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 79ca30e23f 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 90b57b6963 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 550c2d9b7e 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 79d65be530 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 65eaa6a1c6 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 665804dccd 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 88cb9b092a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new f3f5597602 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 94060ae909 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 35aebf7af3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 00e42c98e3 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 8dcf84603d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new df4ebae523 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 5b8d21aa42 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new f8d07bb418 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 1da0d24c6e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 76fb20ea0d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 36d2c8f6c6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new c6cc6a9616 94: onsuccess: #832: 1: Success after binutils: 5 commits new e70492e441 95: onsuccess: #835: 1: Success after binutils: 3 commits new c24a0e907d 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new cba9afed3a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 79353145ad 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new fab4f9fcc1 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 51f8d4f767 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 0b170f6ef9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new e284b83486 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 32ae7b4ac4 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new dd846699b5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new a801550d04 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new ab4ef0225a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 8b5901289b 107: onsuccess: #849: 1: Success after binutils: 5 commits new 68995e200f 108: onsuccess: #850: 1: Success after gcc: 2 commits new 2086219c8b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 1d53c830b6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 9e259ad04d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 4f29d3bc7f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 22ab264cb5 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 93edb679e5 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 9a35db0adc 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new f02485ac4d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new d5c19876a4 117: onsuccess: #861: 1: Success after binutils: 18 commits new 226e93f252 118: onsuccess: #863: 1: Success after linux: 12 commits new 489a9a885e 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new ad5c75ebd3 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 6002761119 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 097cc5fa0d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 15d16c8578 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new ebee22730c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 71c11cb05a 125: onsuccess: #871: 1: Success after binutils: 26 commits new cc8d975179 126: onsuccess: #873: 1: Success after glibc: 2 commits new 7e4e29aa8d 127: onsuccess: #874: 1: Success after linux: 219 commits new 8a026f43de 128: onsuccess: #876: 1: Success after binutils: 12 commits new cf7e88c4e1 129: onsuccess: #878: 1: Success after linux: 3008 commits new 11b533c443 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 9879482fcb 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 102090b3ff 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new fd65ce2fd1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 3ff506703b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new cb054b63a2 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 1aedeeb7c1 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 430efa85f3 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 52cb4d3dd7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 8401e35d97 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 9bce56f189 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 0ede901acd 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 9ee5416312 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 5f95bbe2ee 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 4b1c6fc16f 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 4ceb48628a 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 32237e602b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 3a124d7a03 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new cc5ddd7405 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 5114e16654 149: onsuccess: #899: 1: Success after binutils: 15 commits new 892d293ae2 150: onsuccess: #900: 1: Success after gcc: 11 commits new d36d6cd416 151: onsuccess: #902: 1: Success after glibc: 8 commits new f9dee73045 152: onsuccess: #903: 1: Success after linux: 22 commits new 4ab3613520 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new e2b9a413b4 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new baf7daf47a 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new ae1448e3ea 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new dc38b366fd 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 399b11fda9 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 6688cee79b 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 3e5342502a 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 2b4e9e9d13 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (84ffb4358d) \ 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39988 -> 39492 bytes 04-build_abe-gcc/console.log.xz | Bin 215132 -> 214216 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 246052 -> 245056 bytes 08-build_abe-gdb/console.log.xz | Bin 39532 -> 39196 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2448 -> 3448 bytes 11-check_regression/console.log.xz | Bin 7412 -> 12732 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 435 ++- 11-check_regression/mail-body.txt | 125 +- 11-check_regression/results.compare | 463 ++- 11-check_regression/results.compare2 | 948 +++++- 11-check_regression/results.regressions | 98 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 127 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 98 +- sumfiles/g++.log.xz | Bin 3770980 -> 3721936 bytes sumfiles/g++.sum | 282 +- sumfiles/gcc.log.xz | Bin 3305276 -> 3287360 bytes sumfiles/gcc.sum | 5295 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1082432 -> 1084364 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232160 -> 232388 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456676 -> 456056 bytes sumfiles/libstdc++.sum | 12 +- 43 files changed, 5259 insertions(+), 2817 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-defconfig updated (07b43e37be -> 2b8deb4235)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 07b43e37be 34: onsuccess: #419: boot: Success after gcc/linux/qemu: 512 [...] new 2b8deb4235 35: onsuccess: #420: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 30824 -> 30492 bytes 04-build_abe-stage1/console.log.xz | Bin 87080 -> 87508 bytes 05-build_abe-qemu/console.log.xz | Bin 32200 -> 31436 bytes 06-build_linux/console.log.xz | Bin 3080 -> 3136 bytes 07-boot_linux/console.log.xz | Bin 5636 -> 5652 bytes 08-check_regression/console.log.xz | Bin 3804 -> 4052 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (edf64cd235f -> c777aa9765b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from edf64cd235f Ensure that libbacktrace/allocfail.sh is not deleted when c [...] new 5e8b4bbcc85 ctf: fix various dreadful typos in the ctf_archive format comments new e2dc08c6f06 libctf: skip the testsuite from inside dejagnu new c777aa9765b libctf: ctf-link outdated input check faulty The 3 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: include/ctf.h | 8 ++-- libctf/Makefile.am | 3 +- libctf/Makefile.in | 95 ++++++++++++++++--------------------- libctf/configure | 21 +++----- libctf/configure.ac | 7 ++- libctf/ctf-link.c | 35 +++++++++++--- libctf/testsuite/config/default.exp | 5 ++ 7 files changed, 94 insertions(+), 80 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch binutils-2_40-branch updated (7145c3f6100 -> 999e7ed7a2b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_40-branch in repository binutils-gdb. from 7145c3f6100 Ensure that libbacktrace/allocfail.sh is not deleted when c [...] new 999e7ed7a2b libctf: ctf-link outdated input check faulty 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: libctf/ctf-link.c | 35 +++++++++++++++++++++++++++++------ 1 file changed, 29 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (8814c231be -> 02c0e25477)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 8814c231be 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards c6870c9a7a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 18cdca8537 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7e1dcee376 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 13f9370e7c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 2f3bccb9d3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 61b1367c96 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 6052990780 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5ce507b6dd 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards cfd2c49ec7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards bf59315026 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 0877834bc7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards c975db6f7b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 324c1483c9 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d5f098d983 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4995faaa82 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b81883f0f8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 07b4f79657 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 6554c83ff7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8d54374ec8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 6a6acdf150 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards bd06e55048 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e3406b279b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 5af9de8091 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 01f1e772ea 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 58d1326417 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards c33337cbcb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards a0ad344cae 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 948e22ece1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 100a6b30a8 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f15708bf6f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 03fd1c1649 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards ce10c6d2d0 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards d4ef755e61 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b3a983375f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards fc6751a62e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 2304408033 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6e1406bade 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 7d6709ac80 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 264b6070c8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 7209e15d85 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 0ed9e52e6b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ce208149e5 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 66ebee1e9d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 99224ce984 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 087da8064f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a751ebbfb6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 32d8b1c36e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 11f2a7d560 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a23b7f9db2 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards a01e99dbf0 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 22a4034027 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards ad78cff61c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards d4028c7c39 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards ec2039f851 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 54999114c8 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 76b7ec9f94 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards a5e7312561 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards f417a2bb37 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 071eede2b0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards b6a6e4f90c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 75239af78d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0ea48c59f4 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 771d2cdc17 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 53cc5b7046 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f279d32f14 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards cfcc3dc229 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 4979046725 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 280b1636be 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards cd1492e873 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards eaf7aa629e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards d280e86226 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 265a22f6e7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 9804567c88 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 99a647a865 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards e22d3e6cdf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards cb8857245a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 3ab0a4a5a3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 5890bf8cc7 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 970eb63c12 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 8b930ad75d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 70e3aeee58 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards dafb365c7b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d4232b0c93 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 84d456b246 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 04b00c5752 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 2eaab2bae4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 57d68e49ff 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards b74e17af35 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 46da6b42ec 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 0235ee01f0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 8a90e9864f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d903fa451d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 394b9defc4 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards a2db70e6e6 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1f04812c80 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 434610c259 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 6d9eb76708 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 27a049f1f3 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 6076050cbe 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 4d42e7f695 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 3820fcbf4b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 6203907340 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new f6c5832dcf 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 582e5a102e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new c26e7934a3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new eebbbefc05 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 3b49915972 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new e63c73d9e6 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 391b71a89e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 3543b8fbfd 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 479a5ccdb0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 01d3f88f55 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 05f9e3af16 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new d5c269859e 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 13b3a91ff9 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new cb63b29f79 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 6e65d5e15c 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 25917ff1e7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 2f8ed2691b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new f3598d5eea 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 11a521144c 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new cd20565550 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b873d37ed8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 47e67d19bd 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 5a139db57c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new bb9496739b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 6834f86eef 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 1410411783 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 9feffa509c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 23c8ebf66b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 8e4d648cc6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 182a92c2f3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 68953a3cd0 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 7bba4fef91 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new fbc295bd1e 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 3a1d8c9619 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 0f05e0c962 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new f51956f217 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 1d655ad839 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 000e74fa19 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b8741c7140 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 7891277db1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new a7ee4e035a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new d96a70a05f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 995a26ba23 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 2750036f9a 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 1903ff6ec7 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new b93d82d7b6 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 4f6f47c31a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new b17e865bda 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 2ada35ef5a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 2ee3a7a32b 294: onsuccess: #2110: 1: Success after gcc: 17 commits new c63845edd7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 91586a6d1b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f40e3a08e8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 5fe09ed4bf 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ea4970f00f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 62514e7a2b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new d5092ae76a 301: onsuccess: #2118: 1: Success after linux: 16 commits new 8af80c6483 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new e98d5de71f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new acb259daf4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new bb5056e86b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 706bd6e528 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new dd409bfa47 307: onsuccess: #2124: 1: Success after gcc: 2 commits new cade1e53a8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 3971ce6f6c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 331bbbf28e 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 631e398778 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 5f273cfc05 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 90d5d3b4f9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 5345756547 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3f62da0584 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 8b88640f42 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 4362733bfe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 7a79eb7342 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f408c3d8b9 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 1ccae392ee 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new dc9a37bc30 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b91d6ff321 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 8328e94084 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 17f9482136 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 2b3612a2e5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d39ab7e888 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new fc46d42bb2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new dc32c5e4ed 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 509598bc9a 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 4c2484b532 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 59649dc5bf 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7565d110bb 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5db98d7f82 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 49cbd7eff7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new ea46232a81 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 63ef871612 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 37ea842f74 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 2283646b17 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 7286244547 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 365210a19d 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new eb05a81241 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 9dd844b8c1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 63eb5dba01 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 02c0e25477 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 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 (8814c231be) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31956 -> 32128 bytes 04-build_abe-stage1/console.log.xz | Bin 91504 -> 91796 bytes 06-build_abe-linux/console.log.xz | Bin 9296 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 236396 -> 236384 bytes 08-build_abe-stage2/console.log.xz | Bin 228052 -> 228092 bytes 09-build_abe-gdb/console.log.xz | Bin 39268 -> 39572 bytes 10-build_abe-qemu/console.log.xz | Bin 31476 -> 31228 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2612 bytes 13-check_regression/console.log.xz | Bin 5212 -> 5964 bytes 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 18 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2692244 -> 2691504 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2252124 -> 2253956 bytes sumfiles/gcc.sum | 2260 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 899100 -> 891828 bytes sumfiles/gfortran.sum | 7 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214192 -> 214024 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437496 -> 433640 bytes sumfiles/libstdc++.sum | 2 +- 37 files changed, 1228 insertions(+), 1215 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (a8cb8b0ef1 -> 004a30bca8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards a8cb8b0ef1 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 2afafb6adb 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 35ae5853e8 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 28f144af16 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards ed68ed5b67 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards c6e9d242e4 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards da6e0c248b 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 18fca5c9b6 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 3c3abcca41 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 05922613ea 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 08e2cc3b45 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 771f0957a0 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 411cefc6c3 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards cc0a40ce46 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards e9f6adf939 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards fddbbbdfed 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 9213323375 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 31d48ede65 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards f833a3d65f 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 50519c4498 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 17d73bd957 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 8e1276527a 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards fb93f2954c 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 0b3c004497 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards e6cc6f9b36 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 938eb25528 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 2b21cc7f05 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards d7b2efc908 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 1a18a51663 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 0113f8be66 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards f5b292cd5c 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards e8384fc62e 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 1d6f996359 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 8cb09757ec 321: force: #2055: 7: Success after gdb: 2 commits discards 105f619810 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 3c428a4b56 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 44c5525c0a 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 344d6b17f7 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards b68dd8d80b 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 57c2f207c9 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards d60cb22c2a 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 606971b6c2 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards d684d13826 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 9aa43ffdcf 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 075dd0332c 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 71f034de5c 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 029955bbb6 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 10bace0ce0 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 6287ce3837 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 9459bc36ce 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards a047c17964 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 37d183df5b 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 629d56cb36 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards d6ea2168be 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 1fa9d511a4 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 0573de2734 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards e0eaf3be7a 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 6a3696df4b 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 0e35d8e7ca 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards a1a26c4633 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 04c81438f6 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards 61412ac0a4 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 38b65a4f6d 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 1e12ae410e 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards aeb80bf2f7 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 2fd553b88b 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards 622196919c 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 6d1f46af35 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 99a7a2969a 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards d414069ac3 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards d5335d0ae8 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards d8cea1f5ec 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards cfe9416529 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards 0fe5349cfb 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards aa3e0e8ea5 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 7fc67fa2ed 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 524f4a7fae 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 771fcaa326 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 3ebbdf221c 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards 8525323086 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards ec5bfd5051 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards 973c388609 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 5814b660b8 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 4d989d0d3b 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 16f78e071e 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 9b5165613b 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards c62ebe9408 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 77a29703d1 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 8fee076c97 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards 11fe84f004 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 142828cb2d 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards d7042935a7 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards bc5eb48079 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards ef2ce6d71e 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards 97832239c4 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 42f480622b 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards 2f547665b4 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards b773309192 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 7e6addbd56 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards 035bcabf0b 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards 7c07fb5113 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 314ae6a737 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 7cf32385f1 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new 6c3d59d3fb 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new f0591c0baa 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 821277395d 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 0755734078 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new eee1363516 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new 54b7f0e9ef 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new 2eadcc297a 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 73d08cf5e7 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 3a8c1b5568 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new 5a0790a1c3 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 2e5116856a 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 88ad46212b 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new 6a5d932992 268: onsuccess: #1997: 7: Success after glibc: 2 commits new 8f2e89de1a 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new c1fce17a66 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new e004877f24 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new cafa899dd7 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new eada2f5b76 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 8295ea3425 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 0e1091b30a 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new dea9851545 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 154038a266 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 47ddf99317 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 7ff2a4977f 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 8cebe2b761 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new c9234b6c30 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new a67c982cad 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new 6fbbc74a5a 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 0ed5d8899b 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new b059cc27fc 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 31cb30bbfb 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new be3b0c3ee1 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new b0462c5700 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new be246a6e43 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 8557fc4c11 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 132ea2d7f6 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new 29a0beb353 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new be5b0ef6da 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 2ac89b8417 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 64535c7553 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new e0feacda8f 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 6d1e40f805 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 0a5f5c9a8f 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 019f11fc83 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 7c542e082b 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 7e921707c2 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new de9322b6b5 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new bd0b05c67c 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 9895c7fe15 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new dbefc0bdaf 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 18e77331cf 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 72f2f98ec6 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new fe98396b22 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new f1d853b2c6 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 6864cd7a6f 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 7d9daa19da 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 5b7a996ce3 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 704854c82d 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 7037093272 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new e51d8d0764 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 9d65d3f8a6 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new ec229a659c 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 3142abdea8 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new e5aa58a91d 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 533ac0a5ca 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 46ee0b8f62 321: force: #2055: 7: Success after gdb: 2 commits new 1bb8fea33a 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new bd4f236926 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 83676305b1 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new dd1cb78ca6 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new a3a12f2b0a 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 4139b8b324 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 052eed9812 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 48d65a7078 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 666f960b57 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 20d0f76d2d 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 1e14d1d78f 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new b6b0794669 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new f6ba2501f7 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new 93bf1dcdf3 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new ce0b44a340 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new a6108b50ad 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new ef46f8e3a7 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 6aaff3df0c 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new bfe0cd4a5b 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 7aed5f0e16 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 542f2aafd9 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 81e4a04a34 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new dc82f1d891 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 960e88acdb 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new c1d3b145fc 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 0d9cc655a2 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 6f0b2b947f 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new d512559794 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 804d8d35e4 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 59493e1f4c 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new 3b8d7dbcc7 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new da1899e6cd 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 272f97375d 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 004a30bca8 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a8cb8b0ef1) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1788 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2792 bytes 04-build_abe-binutils/console.log.xz | Bin 32652 -> 32048 bytes 05-build_abe-stage1/console.log.xz | Bin 92188 -> 92984 bytes 07-build_abe-linux/console.log.xz | Bin 9420 -> 8796 bytes 08-build_abe-glibc/console.log.xz | Bin 237684 -> 237428 bytes 09-build_abe-stage2/console.log.xz | Bin 230736 -> 231040 bytes 10-build_abe-gdb/console.log.xz | Bin 40176 -> 39676 bytes 11-build_abe-qemu/console.log.xz | Bin 31380 -> 31556 bytes 12-check_regression/console.log.xz | Bin 3548 -> 5088 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +++++++++++------------ 22 files changed, 68 insertions(+), 68 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch gdb-13-branch updated (86ac3f14012 -> 3cc048fc6b1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from 86ac3f14012 Automatic date update in version.in new 3cc048fc6b1 Set _WIN32_WINNT in common.m4 configure check 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: gdb/configure | 12 +++++++++++- gdbserver/configure | 12 +++++++++++- gdbsupport/common-defs.h | 4 +++- gdbsupport/common.m4 | 13 ++++++++++++- gdbsupport/configure | 12 +++++++++++- 5 files changed, 48 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (79c4cb2d6b -> 6e62ab740b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. discards 79c4cb2d6b 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] discards 4aaaf06002 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] discards 39ee595849 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] discards 23b990ed38 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] discards 2cdd14a069 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] discards a4f38de3ab 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] discards 5c4cb9064f 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards dd8f9efa6a 162: onsuccess: #579: 6: Success after gcc: 11 commits discards dd057cf7ec 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 39025c82c3 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards a008b708fe 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards fcaec2790a 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards da81084f83 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 0f2bb83bb9 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards c7951c3e6b 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards ffa67af888 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards 9d19f30809 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards e663e9fddb 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards ea308adaa6 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards 5cdc136758 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards 87cb523132 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 2231a92261 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards cc4dd584f5 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards 82069a4281 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards 968a608b57 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards 906cdcef78 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards bcb104c347 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards b50b2dc2f4 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 52be28963a 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards 4b61dff481 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 732996f967 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards a5d2fbbce1 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards 73f967f3a4 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards c4000225b0 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards ebbe5171d8 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards 96b801f151 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 178efd25ff 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards 39dc05b7f5 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards f23ef4b5b7 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards 2f14d86c0f 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards e08b4403ce 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards fc5e9007f5 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards 39a519e002 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 86dd66561a 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 46716565c9 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards 00499f5d8e 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 309f9a9f0a 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards d1838a15f1 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards 7ffa209a8b 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 75a2170b9b 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards f55860b3af 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards 4811d637dd 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards 459424d445 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards 6e2e296a5a 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards cde00e958b 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards 05da932276 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 726a3aa6cc 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 9dc1193e9c 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards d96d72f612 111: force: #520: 6: Success after gcc: 9 commits discards 77b5616286 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 6f2c0abb94 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards accdcaeec0 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 123d11fc57 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards 765a9c0549 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 7f5a2181c1 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards cff10e21cb 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 905f0ea023 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 1a1eeb2064 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 1ed3b4fa12 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards e5a4b31136 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 02cc8d8360 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards bf4f108dc2 98: force: #504: 6: Success after gcc: 18 commits discards 372bc9d57e 97: onsuccess: #503: 6: Success after linux: 11 commits discards 8d7031c401 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 933a71ccbf 95: onsuccess: #500: 6: Success after binutils: 8 commits discards e81d1c38b1 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 85609e0356 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 3c46673454 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards c35d7587b9 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 7deec6f3eb 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 1d5da1cefa 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 61ff1d48a8 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 06857f01ef 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 0aa392f892 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards abaf90ef82 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards 02bf19fa39 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 38849563cc 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards d9088ebb19 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards ff8eea27e1 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 15bb7b3200 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 04b1d82090 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 1ca0b2221a 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 4f07bb1886 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 918c1ef6ab 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards b210e1dbf0 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 955ea59780 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 618afc5043 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 72c616ad19 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 588ee2b9b2 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 9db427569e 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards cfcf36e7af 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 557d98bc4d 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new a720618d70 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new bb90359e9f 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 1ae6184e46 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 023e4d8eb2 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new f71ccbb4df 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 6280cade0c 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 818f462a9f 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new 4e38e15793 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new 1155179a5c 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 2c0de3788b 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new b04e412b12 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new b1eca5c6b2 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new ecaa78e214 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 4875baae5e 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new c323d537ab 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new ccc678c380 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 56e62b6222 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 836cb70fbb 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 4a0a1ec0f2 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new fe3e79d2e8 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 82029a0d60 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new a0e245495b 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 3a3b2fa947 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new 5cab52d1ac 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 39bf0f9962 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 76b38df206 95: onsuccess: #500: 6: Success after binutils: 8 commits new 9c3bc7bb24 96: onsuccess: #502: 6: Success after glibc: 10 commits new bb9a17c04b 97: onsuccess: #503: 6: Success after linux: 11 commits new 440a0043d8 98: force: #504: 6: Success after gcc: 18 commits new 65478396ff 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new f88efdc638 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 6d97ca30e2 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new ee7dceaa1e 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new c30155e80e 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 54d1db8495 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 4c82360471 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new ae69fd72cc 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 5bcfb9a701 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 999cbad3e1 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 5a1988438f 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 7832eecaaf 110: onsuccess: #518: 6: Success after binutils: 5 commits new a429a6d3e1 111: force: #520: 6: Success after gcc: 9 commits new 1dc35b3d47 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new 4bc8db0c96 113: onsuccess: #522: 1: Success after gcc: 12 commits new 0c1446a36b 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 8b890219dd 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new 872b82c4b9 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new 0f9066c504 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new c86b5b0ed5 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new 0efc2b5e29 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new 0a0595f950 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new 859de2283a 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 72dfcc0c8c 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new 369a15d6c9 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new b76659042f 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 75d4b1dfc7 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new dcdfd00e76 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 18d59080a5 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new d8bd2d6fca 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new 2f80f5ac75 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new a3fdcf279a 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new fd1e0b82a4 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new b8b30a02da 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new f83786b4ed 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new 99e3c7fe50 134: onsuccess: #544: 6: Success after binutils: 18 commits new a83e6cb913 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new 81801fc809 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new f19ee08bcf 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new 620818aad6 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 30711340ed 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new f41b098ddf 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new ba24623664 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new af671d7417 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new df7aa76444 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new 2f663c4396 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new 51cab6802e 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new 3d5ef38691 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new f2305d67af 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new 675181a3b0 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new a7b4a6e8c3 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 85a088fdd2 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new 723981cbe4 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new fbd2b3b4d9 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new c4ced55c65 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 9944722909 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 7bffa2d3a0 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new 8fcb05ab3b 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new a1163f6743 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new 57865bf165 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new fe0c6c6d14 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new 188bb66d67 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new c9d7b6f683 161: onsuccess: #578: 6: Success after binutils: 15 commits new f55664ada3 162: onsuccess: #579: 6: Success after gcc: 11 commits new 26c3ea4ca7 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new d8716a38fa 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] new 49d3ab9a56 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] new ec67fcf42f 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] new 88c2b890d0 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] new 9468309a62 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] new 2c75837e86 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] new 6e62ab740b 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (79c4cb2d6b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1728 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 52680 -> 52572 bytes 05-build_abe-gcc/console.log.xz | Bin 235688 -> 239116 bytes 07-build_abe-linux/console.log.xz | Bin 8696 -> 8728 bytes 08-build_abe-glibc/console.log.xz | Bin 236552 -> 236116 bytes 09-build_abe-gdb/console.log.xz | Bin 51992 -> 50928 bytes 10-check_regression/console.log.xz | Bin 4328 -> 4492 bytes 11-update_baseline/console.log | 38 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++++++++----------------- 19 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards ad90cfdf93 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 2d1ad4f2df 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 743ed6473f 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards dff96a054e 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 6ed507750b 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards df4dcf530e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 1e91a015c2 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 5153ed608c 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 102741d371 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 47e515a3e4 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 0011bb6f08 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 542ebcd4d9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 2b5f700c7a 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 09730d5401 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards f4ce19380a 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 25601045fa 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 1f03fc882a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 181abd18a0 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards fe44cdf6d7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 569d02b1d8 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards eb67cdf206 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 1a8885140f 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 4c4f672a04 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards d7848a046e 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 0c3f57fd51 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards d39f82921c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 57d1c8188d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards a788be6d5f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards d05ce0d54d 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 49a2c94d4a 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards c09fa3c006 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards c01a9f45fc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards b1fa00d544 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards cd9a584583 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 5ad07a04c6 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 16de6ccef0 125: onsuccess: #614: 1: Success after linux: 12 commits discards 99fe2cfeae 124: onsuccess: #612: 1: Success after binutils: 18 commits discards a5ef43d94b 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards aeba2c5c08 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards ea4188baa2 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 0625e87657 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 454a2b0b8f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 8418bc2ec2 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 51d541a03e 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 25e65e02ad 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 8e9f7ff2ad 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards deb91f1bb9 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 68b4f3b18a 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 8c1249c0ae 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 4099d4f19e 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards efcd3b4a37 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards d0050678e7 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 58eeb0d916 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards c83c54e7e5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards d0cd20687a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 889cb0b782 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards a32ec6f955 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a150d32b60 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 5152d441a4 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 2c41323713 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 2e51bc8397 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 174fa44d9e 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards c9addcb4c0 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards e55abd8191 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 15c6a5a33e 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards e939e44988 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards d6cb137025 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 0e506977cb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 47d7df45b4 92: onsuccess: #575: 1: Success after linux: 34 commits discards 08d9831a90 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 8360819c15 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 2b97b96b5e 89: onsuccess: #570: 1: Success after linux: 11 commits discards 0701789cc7 88: onsuccess: #569: 1: Success after glibc: 10 commits discards b7df781cb0 87: onsuccess: #567: 1: Success after binutils: 8 commits discards b5b7b4e0dd 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f607c372da 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 68e9c3f05c 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 774ade52c7 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 5ce039059f 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 3996b0941e 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards f331a26269 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 59e5fb93b4 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards d741f71da7 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 76f8f86d76 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards df59eec121 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards c5657237a6 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 02e0c89739 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 15e3fc4332 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 5fa7a7be37 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards a5b5319fe6 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 1f9877bee3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 126c3f9b87 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards bbe5df108d 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 95191315c1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 6a4cc28605 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 4eee5c87ea 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards dfef355a2a 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 6df0dee57b 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 5a3f53243e 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards d4125b0d1e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 346c2e196d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new ca9839040a 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new ff845d3d6f 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new f392f1c119 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new ef2e1744d6 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new cefda1b7fd 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 3bbbdc257f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new d60de99b42 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e174f49c8b 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new f8f7a8080b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new d1ec6b21cc 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 0fb7985b2f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 475cef5291 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 12de286102 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 57866eb1c5 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new acfc690e9b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 114a966517 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 477e459ad5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 295727a898 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new c2b560e16f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 64c63f537d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 46ba2b4653 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 00a193a229 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 828b07641e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 2cb431b40d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 7d6f46a110 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 5f60fdab08 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new bedeff50c0 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 386c544154 87: onsuccess: #567: 1: Success after binutils: 8 commits new bcc9c410ab 88: onsuccess: #569: 1: Success after glibc: 10 commits new 26bca6642a 89: onsuccess: #570: 1: Success after linux: 11 commits new b44d94e980 90: onsuccess: #572: 1: Success after binutils: 15 commits new b7408284a1 91: onsuccess: #574: 1: Success after glibc: 3 commits new ec2c1328b2 92: onsuccess: #575: 1: Success after linux: 34 commits new 2a1a0331f7 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 0b93f0ce7d 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 24f9d035f1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 5b18119f30 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 5bfda2eb18 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 23be897298 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 9889830071 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 4fc296280e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new a9b0b74c83 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 1acfeb13e6 102: onsuccess: #586: 1: Success after binutils: 5 commits new 62b3179357 103: onsuccess: #589: 1: Success after binutils: 3 commits new c40847f2e2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 169a8a6052 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new bb6d8623ef 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new ede04c3323 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 14ca662def 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new f24e577f8e 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 3804785317 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 2e395df91d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 58d377f1ab 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new ef7f42e6b7 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new d041ce1aa8 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 6487b4a433 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 65c9cd972e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 0d831e1225 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 13e9c049cf 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 69885dbacb 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new dc4030f649 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 24cfe3fecc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 95c40ac17b 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 191b119d12 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new d14392c666 124: onsuccess: #612: 1: Success after binutils: 18 commits new 291070d179 125: onsuccess: #614: 1: Success after linux: 12 commits new 2d3384c78f 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 4a280f4dd6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 8e911ab93b 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 8789aaa44b 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 589b9386e4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new bc14ec8a18 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 989b6ffafc 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 72d1d080be 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 20948a3cfb 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new eb60d6e7c6 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 718dbf5a95 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new f5c0dfc4ba 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new efd51058c1 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 02460a3747 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new b2d10062c5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 4d32d30a2b 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 2c381ace70 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new cd64bf104b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new dfab5fcc0f 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new bac1c5c1ea 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 69cf7ed163 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 1a84ed06b9 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 75051431da 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new e26c18163d 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new ea16b5132a 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 8af0fbda5b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 02bbcef193 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 3856496997 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 27481ebde6 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new f606903cb2 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new e56d7e5ac2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 9255685a12 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new f5fe0dc45e 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new b0e873353c 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 9d3930380b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new d2fe5a9747 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ad90cfdf93) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 52620 -> 53824 bytes 04-build_abe-gcc/console.log.xz | Bin 237276 -> 237612 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 236076 -> 236356 bytes 08-build_abe-gdb/console.log.xz | Bin 51924 -> 51708 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2024 -> 2348 bytes 11-check_regression/console.log.xz | Bin 8140 -> 8120 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 39 +- 11-check_regression/mail-body.txt | 155 +- 11-check_regression/results.compare | 75 +- 11-check_regression/results.compare2 | 247 +- 11-check_regression/results.regressions | 75 +- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 157 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 75 +- sumfiles/gdb.log.xz | Bin 1731512 -> 1818484 bytes sumfiles/gdb.sum | 5013 ++++++++++++++++--------------- 31 files changed, 2944 insertions(+), 3002 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Oz_LTO created (now 6f39263aff)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Oz_LTO in repository toolchain/ci/base-artifacts. at 6f39263aff 45: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] This branch includes the following new commits: new 6f39263aff 45: onsuccess: #1: 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page: