Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/bmk-scripts] branch master updated (4ce5abf -> 15ca72b)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/bmk-scripts. from 4ce5abf ssh-cc.sh: Add debuging support new 15ca72b ssh-cc.sh: Avoid resyncing on changes to make.out and make.err files 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: ssh-cc.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (0f2dc4e652 -> f0a62dca46)

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 0f2dc4e652 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards 7b91fba08c 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards d6e714b6d6 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards c95a8cd461 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards b7771dbc64 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards bf63249326 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 92c582e1b2 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards eefd502d9a 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards 8fc26c3842 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 99ab36bd33 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards bbeb32ded4 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards c74269333b 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 063e72ddb1 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards a2a883e4d0 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards 05cb4d7a22 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards 7da479d997 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards c969655828 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 0e7bd9108b 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards 11794b1f79 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards d0a04adcce 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards df257aaf25 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards 221d4b14e2 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 825f0a5952 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 1731021dcd 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards 7651f5fd3e 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 3344bb4973 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 7c3a773913 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards c97e106e59 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards c46227b0b5 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 4ad1ae9c53 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards 80251a177a 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 76cca785f9 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 7936f98fc6 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards b8e90a4dd6 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 0785417a0e 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 615514cb4b 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 4d8acb8319 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards 37ba06ff42 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 076a7816a2 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards dc5e1bad65 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards 133db03469 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 68e65fae93 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards af9418fbb3 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 6a5a6be35b 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 50b6b0c064 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards aba66cd16e 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards ea828cc4e7 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards ca54fed74a 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 31ee83fa28 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 812e4b34ee 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards d767bc8184 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 9ceb213ade 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards fbed15db24 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 60e9ccd0a5 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 473e21190b 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards c48baadb5e 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards c1db20e1f0 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards e8c08d0aa2 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 78b14949ed 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 45a933a022 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 14a625dce9 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards e7a9ff6954 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 3afb7f3b5e 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 32447a34ff 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 7689a301b9 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards e4e9a206f6 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 958a50c001 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 845b20a5d1 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards b114d5c42b 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 525b0000bf 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards f9c844e544 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 7814b7dddd 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards e292093022 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 9dcd5601c9 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 294a483670 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 77e4386a0b 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards ee14b74985 321: force: #2055: 7: Success after gdb: 2 commits discards d857cafc88 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards d282886de2 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 0c3cd72e86 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards dcf797e6e6 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards c6eb5e2776 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 0f051011ac 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 894955b5af 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 149f3c3c22 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards aa00e13e3a 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards ad0110dd8a 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards b9b504093c 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 275544b87a 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 3aae654379 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 96febca590 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 04de8a4f71 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 87460aaf56 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards 61e6db3aa5 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards d83a81c562 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 47a5452b6a 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards af3fac2f9d 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 01c0f07802 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 68894a4e7d 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 1ea495ec9b 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 234c53b20a 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 7bf5eb2e06 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 4066daa670 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 0b454634d8 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new cef4ee2892 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 06dc84cd03 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 3b1c1533a9 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 00d9c2659f 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 520486cadf 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new dd718c382b 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 60809a27fb 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new c639a7453c 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 44c577cb3d 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 2c7274d227 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 29b567eb99 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 22e3505936 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 944bc11725 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new c877cf6f10 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 0f68c57da4 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 80067b161b 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new a83fa5732d 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new dbc75912b9 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 2024339c4d 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new f64bcc2e00 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 3ecfdfc23d 320: onsuccess: #2050: 7: Success after gcc: 4 commits new d7d8be054f 321: force: #2055: 7: Success after gdb: 2 commits new 2ae1360a3c 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new a3ded36d5f 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new e4efc6ee5e 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new c2a3829176 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new eab3aca29f 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 7caceef0cd 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 1c1e6e90ec 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 436a21d9cf 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new b888775c76 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new fcdd537f09 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 19c52c7255 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 2a766aabb9 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 7d85bf09ed 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new 13898d8287 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 604b14afa0 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 896388a12c 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 54cc2f12da 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new d746ce1967 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 27ea6c1cb3 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 6d2414085a 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new f4bd78f525 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new f8e832021e 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new fe32f646bf 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 1db6052c13 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 0381062ad3 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 3636bf8f49 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 5067294932 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new 19b36a16cd 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new cf35098810 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new bdd52542a6 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new a683277868 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new dce3828dab 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new ee986845f3 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new c486627642 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 08c38e652b 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 96e9ade947 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new 9979612447 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new a21c9c4b53 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new c35bf3e925 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 949c459b8e 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new df5f332d04 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 869319effe 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 7fd99e6d02 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 3fb3dd7b06 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new cbf263999e 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new fe2b8862e0 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 557c1aef1f 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 0d51e2cbd7 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 3f2292e492 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new fb8ebe468c 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new a6a72cbab3 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new 55adac3eb8 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new e9001f11d9 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new cff18c6b87 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new 42e47cc0bb 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new b507597c3f 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new e57f3812cc 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 62cf015446 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 267ad207be 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new ce5aa8ebd2 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new 8b90ff0323 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new e3ae9f991b 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 0d29636287 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new 569cf43603 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 482de7d792 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 6e2164b471 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new af8bfacfc4 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new db8d6faf00 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new d742a94b1f 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 09f561599a 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 5cf761f526 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new f4a58c879e 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new f6ccf37c52 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new 356735a604 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new 0877b392d3 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new af9e5007c0 397: onsuccess: #2132: 7: Success after gcc: 2 commits new f0a62dca46 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/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 (0f2dc4e652) \ 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 1780 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 31308 -> 30720 bytes 05-build_abe-stage1/console.log.xz | Bin 92660 -> 91748 bytes 07-build_abe-linux/console.log.xz | Bin 8912 -> 8836 bytes 08-build_abe-glibc/console.log.xz | Bin 237308 -> 236008 bytes 09-build_abe-stage2/console.log.xz | Bin 229540 -> 227372 bytes 10-build_abe-gdb/console.log.xz | Bin 38492 -> 38256 bytes 11-build_abe-qemu/console.log.xz | Bin 31912 -> 31660 bytes 12-check_regression/console.log.xz | Bin 3300 -> 3860 bytes 13-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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (3704d60de9 -> 9c7f3788c5)

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 3704d60de9 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 379ead9abc 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 959f686bc5 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards c4184620ba 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 8a51b2d0f5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards d4fc045827 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 730eee0011 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 403865317e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards ce1fb4e83d 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 845fabac4c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 23439d1fad 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards d652ca631d 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 024c0dadd6 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards c84e9b38e0 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 66f05fc692 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 3239b93a1f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 305a312e7a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 5bc03839ae 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards fb907a9c6f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 97ea2f92aa 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 18c6d606ed 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards ac991379b2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 2e3cb485ae 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c780cc1b38 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards ec61a0be89 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards c2be404568 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards d1e688b753 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 531ffdfa0b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 85f60dd9b7 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 9bdabe2d10 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 4162e3088a 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 831d01016e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2642630b40 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 4169f56542 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 0ea048c8cc 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 29c31919a1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards deca9faec7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 2259c1d4dc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards bd648e2b25 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 9bf8235947 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards a1f9b3345b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 1ece9a1aba 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3ac0ccf5d1 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 897a5c1824 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards aadbf75a69 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ee83218be9 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 2b83277600 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards fd46c731a4 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 902993d933 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards e3a628f371 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 20fa5dc19a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards ed4d137627 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 4dda1ee7d0 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b162459284 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards b99d5790ba 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 0222376430 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards d87d5c445b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d03f2db5a7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards f0deac908c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cabd9dd1d4 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards b4226ce9d1 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards e65cc7b87a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 5f8f27c9ca 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 881673726a 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards a5d1276d3d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 6860334a7c 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7c04efd818 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f3d3e57e89 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 89035d23ba 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 3d5bf5e845 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 7e6a6a95d3 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards fc7aa9affa 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 06671450ca 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 8345c8e87a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 06e8b5ac48 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards ca9b586e7c 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 464f4d459b 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards f2aed25c41 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 221e1610b2 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards f5c034aa64 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 537a867ec5 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 7fe580a7f9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards d22f6d18d5 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards c1f306e9bf 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 49d3080f2c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 62ebde1b8b 301: onsuccess: #2118: 1: Success after linux: 16 commits discards c39d6bd39d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 2ee14c7b7d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 738eb98198 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 85a646db07 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards a58b343711 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 7c468e1a81 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 8ca7a33ffb 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards ff33fe92e2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 0bbdade0c6 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards db9042c0ea 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards fad431a6cf 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards d7aa25c051 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 64cc586cf6 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards c1b1421bd8 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 29a3758625 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 143227e973 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 443d4e469c 287: onsuccess: #2103: 1: Success after gcc: 9 commits new a0dc88e579 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 7fc5e60da9 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 64fcf1919f 290: onsuccess: #2106: 1: Success after gcc: 2 commits new d6ae511c45 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 03b805981a 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 1dea55fe22 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 368bc4e3d7 294: onsuccess: #2110: 1: Success after gcc: 17 commits new d597f07683 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 19d247c0c3 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 5bad19ef8b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8143ffcadc 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new f0948f1989 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new d9820ec5e0 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 33b4a8da1b 301: onsuccess: #2118: 1: Success after linux: 16 commits new 7b5093ea59 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 21c56a983d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 4a4aaa0909 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new d4fe17d0ae 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 4201461706 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 89122fa5b4 307: onsuccess: #2124: 1: Success after gcc: 2 commits new f5ce1d36e3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 238e045e99 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new a0f31508d5 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 576a416214 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 901fc76930 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new d75c09298b 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f3716b81af 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 43af47ade2 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new cbe05e487f 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new bf54922b5e 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new a7bf2c8af5 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6a4b524f0e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new a914c67202 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 531229ccde 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new dc40cc1d5b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new f93d71147c 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new bf9da095ff 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 079ce5424d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f260f66564 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new d741bd7e51 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8aee2ae131 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 932662d238 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fbdd5bc0b7 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7e1488c339 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new a8bbbadd8a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 62e7ccae94 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 1e66ed287b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b09dde12e5 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 291717fdc5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new b4f3f4dfad 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 4775597595 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 11f9aa03c5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 33f75d7bed 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 2957ddac4b 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 64bf8937e1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 18993f1aef 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 8dee653e9a 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 982de15822 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 1efec23b7b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 5ed45de44f 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new b8310806a9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new af63e35f8f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 366c558d97 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 967386f175 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 85de9b765b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new bc43b4a97e 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 19b88f7e7d 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new af0e9021de 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 2e7abee8e2 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new cc6e8eb5d0 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 77c8d149e2 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new b6be94c6d0 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 01a64abf13 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c980caad80 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new e74de1328e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 41c638d5ec 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 7e677b80d5 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 24d9650ee4 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new e4d6d74a2d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new f516eecf3d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 51fab58ae8 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new e9e788f9fa 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 18588e1abc 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new c928b21549 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new cf63238558 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 974af50ff1 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new f8896b18b2 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 4a7bed97b2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 59bfe7b238 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 6e8c1aeb0a 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 3becddac67 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c5b026e567 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 701d2707f7 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 7a74b9b95c 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new d05ab9f3c4 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new b2e8ee1ca3 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 47cfc34d57 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 48827225d1 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new c19983fa70 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 9c7f3788c5 387: onsuccess: #2208: 1: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (3704d60de9) \ 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 1812 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30904 -> 30920 bytes 04-build_abe-stage1/console.log.xz | Bin 91548 -> 92116 bytes 06-build_abe-linux/console.log.xz | Bin 8900 -> 8880 bytes 07-build_abe-glibc/console.log.xz | Bin 236488 -> 236232 bytes 08-build_abe-stage2/console.log.xz | Bin 228448 -> 229976 bytes 09-build_abe-gdb/console.log.xz | Bin 38212 -> 38280 bytes 10-build_abe-qemu/console.log.xz | Bin 32072 -> 31944 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2776 -> 3380 bytes 13-check_regression/console.log.xz | Bin 6388 -> 5500 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 21 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 + sumfiles/g++.log.xz | Bin 2643528 -> 2635444 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2194848 -> 2223556 bytes sumfiles/gcc.sum | 2262 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 889420 -> 889384 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214284 -> 214380 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437280 -> 435912 bytes sumfiles/libstdc++.sum | 33 +- 40 files changed, 1343 insertions(+), 1223 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (5321d53279a -> 295adfc9ed2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 5321d53279a ipa-split: Don't split returns_twice functions [PR106923] new 295adfc9ed2 tree-optimization/26854 - compile-time hog in SSA forwprop The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/gimple-fold.cc | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/bmk-scripts] branch master updated (99acbb7 -> 4ce5abf)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/bmk-scripts. from 99acbb7 ssh-cc.sh: Avoid potential timestamp comparison corner-case new 4ce5abf ssh-cc.sh: Add debuging support 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: ssh-cc.sh | 36 ++++++++++++++++++++++++++++++++++-- 1 file changed, 34 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/bmk-scripts] branch master updated (5b078f1 -> 99acbb7)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/bmk-scripts. from 5b078f1 Revert "spec2xxx-install,cpu2017_*cfg: Patch spec2017 makefil [...] new 99acbb7 ssh-cc.sh: Avoid potential timestamp comparison corner-case 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: ssh-cc.sh | 4 ++++ 1 file changed, 4 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/jenkins-scripts] branch master updated (c02a9d92 -> 591b01d7)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/jenkins-scripts. from c02a9d92 generate-cimonitor-dashboard: Add a new summary table new 591b01d7 tcwg_kernel-build.sh: Handle a corner-case when linux commit [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: tcwg_kernel-build.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (47c34fa992 -> 1ff3220519)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 47c34fa992 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards a278384bd6 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 86d02341a8 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 008b0a60b6 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 17b30081dd 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 4419ae2e10 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 69668a5f02 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards 2cb5f983ac 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards fd3cbc8e43 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 69eeefda36 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 3c9fa8ab5a 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards e4839e176d 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 1dc883a2a9 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 58468da045 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards fe86aac2a7 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 951136978f 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 3026d20340 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards a1b5b4a688 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 602693e88a 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 015734ad40 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards d114c27c8e 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards fe1d82e7eb 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards a8fd805743 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 8ea542b79f 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 585b8ad5c4 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 3abcee2f07 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 555027d539 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 4ff1165de6 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards 817214ff39 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 561ce6e589 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 7be75bb1d6 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards e47a82569a 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards f53867fe07 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 5c1a3cb3be 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards b8df10676e 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 2bace85456 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 671444c3c3 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards f61c9923ec 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards c0dc63924c 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 342da85b04 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards f4dedb95ea 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards f504037c9a 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 10b2a2b942 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 3c8732cf9f 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 7e46e188ac 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards efa5f4d9f4 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards f57ee35df3 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 6b8a071dcc 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 80c2700071 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 063bb04c87 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 5d1d26859b 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards aa0fa12a6f 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 9eedb11a0c 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards edd033872e 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards efe27212ad 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards e18ba3a4d5 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards e26d5973f3 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards a59f126bd0 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 11e38415a0 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 53c45ed778 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 6b4a6e9d97 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 35ed3ea7a0 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 93b3e0dd8d 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 86473b7dca 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 2c00f2e57c 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 15fd35de55 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 8673171cf5 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 9d1dc81965 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards adf6dd3187 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 005068063e 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards e7619fdc7a 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards b39fb2228e 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 8469b2f78b 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 8b17088db3 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 84d581be16 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards ca618d3625 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 1d99143cc0 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards e43fa6b4d8 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 7a1025547c 305: force: #2006: 7: Success after gdb: 2 commits discards 3d3207ba34 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 31f288fab3 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 006938ea7f 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards add68be995 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 16ee63bf75 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 124bbaa541 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 3e96a4e5f8 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 3ceb0f95b1 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards b907bd6824 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards d9bf966e1d 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards ff757920e0 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 660207cbb4 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 4a50e4d912 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 984533a3a5 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 8c2162c6b9 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 915f96af1f 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 1e9431e3f3 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 2be5fe4f38 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 92bd139092 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 9d65eed4f8 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 2ede30fca4 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards a653cb2117 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 9b3a89ba59 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new b4c1cef06e 284: onsuccess: #1981: 7: Success after gcc: 2 commits new b589830ecc 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new faae7b69fc 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 2fd7a03100 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 3dcb2f8ffe 288: onsuccess: #1985: 7: Success after gcc: 17 commits new 3c8fff1cc8 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new a2b49966e2 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new f07ee4f2b3 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new d3e9a92dab 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 1f0adccfc4 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new c0f7338dab 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 295953dd5c 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new cc8a104b14 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 1ae0f91bcf 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 9c1c0d0524 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 7a9be2f172 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 1dac87370c 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new cf4e99cfe6 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new b68f7b563a 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 77f585bbbf 303: onsuccess: #2001: 7: Success after binutils: 4 commits new afd625e3b4 304: onsuccess: #2002: 7: Success after gcc: 4 commits new e6263f3a5f 305: force: #2006: 7: Success after gdb: 2 commits new a16d1d0726 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 4f5b0a638e 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new feebc06ac0 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new e4107f2314 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new a364dfd162 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 34fd249e28 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 5ee8ec79f1 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 366bedc4da 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new ee1ebf040a 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 505409c839 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 1021cb2e48 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 13f59ebdf4 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new f4479524cf 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new b89d5e1a6e 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 911bf2e74d 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 4c481ca868 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 5bc34485f1 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 49c22c4130 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 88965c7ed0 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 0966cc0691 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 90d5058bc0 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 1286f9a57a 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 1b63a9af93 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 4909fc571e 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 8d230bd4bc 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 7aa8664d44 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 3e76957d94 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 393b91020c 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new ee7e53491d 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 80347375d1 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 171233b516 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new d10e263df6 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new bcbdd77df1 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 4d66645341 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new d7fc65d7a6 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 61e4537a09 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new aea79ab0ff 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new ed3e0be9a9 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new a14dba3665 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new a13a001c78 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 0508b657a4 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 1fd93142f0 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 74b18e6c63 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 9f4da6cf34 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 1da1b4c2da 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new d387e492cd 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 3a41dd7624 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 73668b71f0 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 50d68d9563 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 89d26aca94 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 16e69d7a36 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 9d7166cebb 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new a1bc52caa4 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new b22b8bd30b 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 45fb44a7dc 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 3fef549002 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 8177522e8f 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new ff7e42b1da 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 50e55f80b5 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 95cf9c39fc 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new e8b3b1457b 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 9f110fe315 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 8d7e715bda 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 9dbb2bb7eb 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 9920836d28 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new af72e45d20 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new f8eef8a436 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new b512ecf314 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 9d9a65cda9 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new b6089f1e2e 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 6e8d913ac4 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 61e399dc25 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new cb07b4eefd 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new e502e53ea6 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 165fb90e46 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new a9eee9a87d 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new 9a0b6c508d 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 91d239448f 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 1ff3220519 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/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 (47c34fa992) \ 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 1760 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31036 -> 30880 bytes 05-build_abe-stage1/console.log.xz | Bin 73424 -> 73024 bytes 07-build_abe-linux/console.log.xz | Bin 8860 -> 8868 bytes 08-build_abe-glibc/console.log.xz | Bin 244412 -> 244100 bytes 09-build_abe-stage2/console.log.xz | Bin 204664 -> 204712 bytes 10-build_abe-gdb/console.log.xz | Bin 38368 -> 38504 bytes 11-build_abe-qemu/console.log.xz | Bin 31732 -> 32096 bytes 12-check_regression/console.log.xz | Bin 3328 -> 3860 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++---------------- 20 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/bmk-scripts] branch master updated (4a0c121 -> 5b078f1)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/bmk-scripts. from 4a0c121 Revert "spec2xxx-install: Patch spec2006 makefile for atomic [...] new 5b078f1 Revert "spec2xxx-install,cpu2017_*cfg: Patch spec2017 makefil [...] 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: spec2xxx-install | 8 -------- 1 file changed, 8 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/bmk-scripts] branch master updated (7e8b676 -> 4a0c121)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/bmk-scripts. from 7e8b676 ssh-cc.sh: Fix rsync of *.fppized.* files new 4a0c121 Revert "spec2xxx-install: Patch spec2006 makefile for atomic [...] 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: spec2xxx-install | 5 ----- 1 file changed, 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: