Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[glibc] branch master updated (b712be5264 -> 71e408e45d)

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 glibc. from b712be5264 x86: Prevent SIGSEGV in memcmp-sse2 when data is concurrentl [...] new 71e408e45d elf: Fix tst-relro-symbols.py argument passing 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: elf/tst-relro-symbols.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 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/llvm-release-arm-mainline-defconfig updated (bb22da37046 -> 0a8ce2cd16a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from bb22da37046 29: onsuccess: #419: boot: Success after binutils/linux: 15 [...] new 0a8ce2cd16a 30: onsuccess: #420: boot: Success after binutils/linux/qem [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30240 bytes 04-build_kernel_llvm/console.log.xz | Bin 63520 -> 62988 bytes 05-build_abe-qemu/console.log.xz | Bin 30748 -> 31460 bytes 06-build_linux/console.log.xz | Bin 3204 -> 3268 bytes 07-boot_linux/console.log.xz | Bin 5668 -> 5644 bytes 08-check_regression/console.log.xz | Bin 3260 -> 3636 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- results | 2 +- 18 files changed, 23 insertions(+), 23 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_gcc_check/master-aarch64 updated (3b34925a8a0 -> 416e00c7216)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 3b34925a8a0 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards 5a426d628cb 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards e79aeb01110 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards b3d04f0ae5b 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards b149e500448 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards 681a1ed8153 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 107fbcfb707 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards b48b0e00b9d 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards c82c0bd4647 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards 25b1b595caa 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards f8ca5e0b68c 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards 84d80ece65d 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards 70949320255 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards 07cb4243b99 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-4 [...] discards fc72556c3c6 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 35275662bfe 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards f79075504b2 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] discards d371caea5c8 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] discards 869b553918e 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards bd915156582 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards c316ff6fa40 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] discards 5e8d384a7ae 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 83400e4e609 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards 83c3a35980b 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards c145ae71a7b 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards 3ee2865c3e4 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards 85ef9754b0f 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards b1dc8165e7e 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards 9df6b073954 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards 04ee5ac6473 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 08dcc8dfdda 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards e84c01e6588 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 9f03882518e 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards 2b57d55352e 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 44fc4f9fefd 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards 2b303d39ed6 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 212bde88f8b 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 0700277397d 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 8f71f654445 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 314c9814d38 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards 40d205a4086 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards d2ae6b551aa 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 8324f6bb0b4 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards 8f97cade8fc 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 7a3ad44881d 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 2f37aaf3ce9 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 60bcec93b8a 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards bc98fc52eed 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 11309474f3e 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 0b5b376d96e 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 34ccdbf588c 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards 73390607ee8 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards fd968814abb 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards b49a6e10c38 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 3f061bd1772 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards bb0f65abdb9 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards d8c1ef9190c 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 6468b92a9da 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards c92ff949835 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards d45bd19773d 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 471200451ec 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards d1ba6aa3b38 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards e2f006bba8c 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 4f09761e082 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 8b1d1b90b78 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 30881e96693 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards c13c1f1a935 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 80e4c5d375b 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 251781e24cb 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 690671699b2 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 15f0041d72a 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 369d2726a7b 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards 989815e5103 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards f80f70a4b14 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 27af01414e9 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 9701790446b 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 6fa1fea2f56 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards c5d1cd561b0 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 96d42d6476d 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards a53d7c2b55b 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards c1716177ca0 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards bb3e866da83 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 1e8ab3d4f5b 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards ee5891baef1 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards e3433c1f2f8 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards ff6bfc9f3c5 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards ff8ecfd8534 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 170ca39be48 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 0f0ea6a081a 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards b8da9ba0c72 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 4f25384626e 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards a0b6e30bd56 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards d1a744ecf40 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 5979c2b6cdb 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards da56295ccc9 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards c5e17f895c0 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 6535c17335b 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards a38becd837f 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 0de6674765b 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards c6836a673d4 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards c8163be1a63 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new c26ec82734e 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new dd5b7c366b1 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new d06bbdd54ea 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 5d9855c21da 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 8b563c1b327 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 8c1ae6a339a 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 6344d32419f 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new b37ddbae739 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new c8b5261d00f 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 0b999ae9cd5 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 039ec1181c2 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 94020f4cc66 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 08492a144cd 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 41a95b594b5 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 7a6afd49191 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 5686d97ec3c 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 043e53de289 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 593a5b31e21 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new fcc5dd6daf5 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 83545c2504e 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 6a0764c8f8d 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new f96f040a380 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 4e5c123b440 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 4b13eb69583 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 93d7e5c8b19 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new ad6353916fb 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 5934b632eb8 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new ec9b2d3700d 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 2f538f34847 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new cbfdf5aa48f 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new afd86ca2092 351: onsuccess: #2307: 1: Success after binutils: 2 commits new ef97761e7a1 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 340b969fbac 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 0288124e7e7 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new dd8ecd316d3 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 3b889ad147b 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 52df0ff7bff 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 63d3aa0e801 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new e91f70356bb 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 747bd24950f 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 6d690ab55f9 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 5777916299f 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 613e82f4e70 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 06d96204a79 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new b81efde35cf 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 646b87f300f 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 7ac87657f1e 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new cc642fb3ed6 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 32df8b4bc49 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new d9591619d98 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new a7c48df954f 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 4ca9835dc5a 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 39e18b3834c 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 6ef1ca55057 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 20791b592f3 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 1efe820ca4e 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 1cd81a75ecf 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new ab9fa0018dd 378: onsuccess: #2340: 1: Success after binutils: 2 commits new d0b2787eea8 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 0fffae407c5 380: onsuccess: #2342: 1: Success after gcc: 3 commits new 325bc40fa3e 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 0819975672a 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new 655b1c32346 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 9d10cf76239 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new fd5448cbd92 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 487cb6670f2 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new 85654c10a09 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 705f718cda6 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 73dd95148a8 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new b76e6c698a1 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 9bb817f7fbc 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 84d5dff5756 392: onsuccess: #2354: 1: Success after gcc: 5 commits new bafc58a9505 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 745705f71c3 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 92e20ce220a 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new e23fb9c6311 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new 6872621f0b3 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new ac323e9e5f9 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new a401727c5d5 399: onsuccess: #2361: 1: Success after gcc: 10 commits new 6007be6ea5a 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new 088a73d1504 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] new cd064c28445 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new 33792588f38 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 768d0f8f22a 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] new 84652d0796d 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] new 82818e4cca0 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new 333dd602a50 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new 52f38e74721 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-4 [...] new 02c99542f63 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new 7feac2e15fd 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new c59723456a9 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new 757aa93ac4e 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new 97b4238eeb7 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new cbf31fca3bb 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new f88afaf3050 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new faab9b00500 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new d154f3a8382 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 0ad4bf920df 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new fc73f0e6526 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new 5d49f4f8f4c 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 21a30cf2e91 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new 416e00c7216 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (3b34925a8a0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1920 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 39516 -> 40348 bytes 04-build_abe-gcc/console.log.xz | Bin 215540 -> 218228 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2500 -> 3132 bytes 07-check_regression/console.log.xz | Bin 5404 -> 5280 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 17 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 77 +- 07-check_regression/results.regressions | 37 - 08-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 37 - sumfiles/g++.log.xz | Bin 3620952 -> 3602196 bytes sumfiles/g++.sum | 121 +- sumfiles/gcc.log.xz | Bin 3152892 -> 3163456 bytes sumfiles/gcc.sum | 5140 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1047752 -> 1049588 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219684 -> 219660 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 454752 -> 453668 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2787 insertions(+), 2886 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- 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/llvm-release-arm-lts-allnoconfig updated (29bd374e0ed -> fdc51ac60a2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 29bd374e0ed 27: onsuccess: #250: all: Success after binutils/linux: 127 [...] new fdc51ac60a2 28: onsuccess: #251: all: Success after binutils/linux/qemu [...] 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 1744 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30176 -> 30128 bytes 04-build_kernel_llvm/console.log.xz | Bin 63384 -> 64100 bytes 05-build_abe-qemu/console.log.xz | Bin 30876 -> 31380 bytes 06-build_linux/console.log.xz | Bin 3432 -> 3480 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3228 -> 3640 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 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 (3da92104b26 -> 51dca1d6a2f)

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 3da92104b26 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards d56b3e40644 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards b4751dceff2 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a7bdff8ba9e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 7f0b7b92c38 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards fe632255b86 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards e5c1eb2a1d9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards db3e9ac2a29 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards fcbc4f45329 125: onsuccess: #614: 1: Success after linux: 12 commits discards 952942b8d7e 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 64b08d0af90 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 533086fabd0 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 24706562c2f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 083471dac0a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards edb378b1b29 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards cb81da8807c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 6f22ab7b241 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 2a8a4e86a3d 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards c28ae012dd2 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 90a9b435851 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 8750b9dcab7 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 7b6246a60e2 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards eb9e05113ef 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 1997cd948c7 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 58f9bf09231 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 93f836168de 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 8814cd202c8 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5bc93700477 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards ca787b457c4 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 4d0f56783f8 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards fec6c09c54b 103: onsuccess: #589: 1: Success after binutils: 3 commits discards f799b9206cc 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 0bdbbf853c0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards f6513ea402e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 5034a7f09c7 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 47f4f8618a4 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards b387ef2e15a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 70595ba1064 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 4d3d5233ca2 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 5eac8ef43ff 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards a268a2f3193 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards e237871269d 92: onsuccess: #575: 1: Success after linux: 34 commits discards f3c15fe54eb 91: onsuccess: #574: 1: Success after glibc: 3 commits discards bb56afa5f77 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 18a8c3b7208 89: onsuccess: #570: 1: Success after linux: 11 commits discards 7e44545e8b0 88: onsuccess: #569: 1: Success after glibc: 10 commits discards cbe4a6aad20 87: onsuccess: #567: 1: Success after binutils: 8 commits discards f2fd82468a4 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 5fd132d85c1 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 7863852900f 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 76c6bdcd0c3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 2a97fc36dad 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards 333f647af68 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 3e34f142b45 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards 694b2fd2644 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards d11226e2bb1 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards f1c2145e0f9 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 58294a0efe7 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 4b42da16f25 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 5f8cd541d59 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards ab86efe3b88 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 4089362b665 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 63f1dc89daa 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 0eb6a15f342 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards f8fa42ae4bc 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards 5e15932a964 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards ff9c057b3c5 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards ebe5daccb40 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards e328b8d9c04 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 4cc0443fe1f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 8343b6dbd0f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 0ec48d6a651 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 5e914a49aec 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 458f037f165 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards e8480a09227 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards b3e2ea63343 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards d5edb4567bd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 55ce0d8980b 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards c6c73151152 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 29c1a6ff6ed 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards c7b7164131e 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 1bbfa7f8a9d 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 1ad047a61d8 51: onsuccess: #525: 1: Success after binutils: 8 commits discards e700b31ba77 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 2bf908cf9d8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 811c54c2649 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards f6fc6d8c3a6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards 00a3c81f7fd 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards e32a6f1852d 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards d14fe4936f0 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 9b641be1e82 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 9c9157595f9 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 6d9b7c367a4 41: onsuccess: #514: 1: Success after linux: 64 commits discards 6d8b674e773 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards 519ba5ef31e 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 309fde3e24e 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 97554bb921c 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 9602ff6dd2f 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 57c1d92b987 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 342853f7e3b 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 42d2cfea3e7 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 9d349f93d23 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new e7cab50cd3a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 3005ca9774a 35: onsuccess: #503: 1: Success after binutils: 11 commits new 0031f0cccf8 36: onsuccess: #505: 1: Success after glibc: 3 commits new 5340d04e811 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 27f7c3c12bf 38: onsuccess: #508: 1: Success after binutils: 3 commits new 01febbe49dd 39: onsuccess: #511: 1: Success after binutils: 8 commits new b75b6bff467 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 30357fd81ed 41: onsuccess: #514: 1: Success after linux: 64 commits new 395cecff910 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 5fd7f2b8208 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 9da8d5c1631 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new aef2b516b27 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new aecfccf1ec2 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 3678e998fe1 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new d4062e2a2dd 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new 8ae4bf2f6c8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new df61137291e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 3638283da8c 51: onsuccess: #525: 1: Success after binutils: 8 commits new d28ae86bb7b 52: onsuccess: #528: 1: Success after binutils: 8 commits new c43f491ed7d 53: onsuccess: #531: 1: Success after binutils: 12 commits new 55164a911fa 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new 22c649179fa 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 8ae40188189 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 158b7b5b9c5 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new e5c16773365 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 7283e3dec40 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 9034b76b0de 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 2c47810d6e7 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new e967cd9a1be 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 9bf9c899a3e 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new a95264bd608 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 6b677cced41 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new f1182f89f48 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new b38b1c8ecd7 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new dffec5fe457 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 4ac304c955d 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new 437944dde8f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 426f4b6c3ac 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 5383a6763c1 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 9929097a96f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 51be15a4305 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new e3a5ce54ca2 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new faa853f5c7a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new 7a55e01fda3 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 09e0ff1307d 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new 6a65e30d10b 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new c5ba7284264 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new f5010d58120 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 5ce64f8e992 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 96e57e5eb16 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new ca8764790a1 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new bbfb7d99b27 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new fdd4918894b 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 6c848886086 87: onsuccess: #567: 1: Success after binutils: 8 commits new b9edafa083c 88: onsuccess: #569: 1: Success after glibc: 10 commits new 99e504561be 89: onsuccess: #570: 1: Success after linux: 11 commits new 870b3d76fc9 90: onsuccess: #572: 1: Success after binutils: 15 commits new be2cee09caa 91: onsuccess: #574: 1: Success after glibc: 3 commits new b29a8ab8c5f 92: onsuccess: #575: 1: Success after linux: 34 commits new 65e8fca81da 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new c5115b9ebb3 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 5eed0e19e2a 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new e20df7a3cc1 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 89444e5e765 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 4bebe2e06e7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 6b94469803a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new 8b4168cb47e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new c96e1c72502 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new 959a5190078 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2c57fb83cc4 103: onsuccess: #589: 1: Success after binutils: 3 commits new 117658eb957 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 3bc68d3516c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 5861d051f8b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 8215492efee 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 4233e10f1d2 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 7d64f79a4bb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new e903cbd8bce 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 0881679655d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new edac67896d6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 30fd103be70 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new ff1f69db55b 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 5a087a9db69 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 90db5fea65f 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 84977afac08 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 1c3586ef628 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 9916313cac0 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f39ae95d52a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new c5548a81b6c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8ddb3620d63 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new a5adcde4dd1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new d61864f05fa 124: onsuccess: #612: 1: Success after binutils: 18 commits new 08097fa9417 125: onsuccess: #614: 1: Success after linux: 12 commits new fb2eea88d45 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new ffd19ef9594 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 41fef8875e4 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 9308b95cfdc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new a406057b133 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new efd055b72f7 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 401849ad759 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 924b50fa021 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 51dca1d6a2f 134: onsuccess: #624: 1: 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 (3da92104b26) \ 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 1900 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 53524 -> 53672 bytes 04-build_abe-gcc/console.log.xz | Bin 237636 -> 236428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 10348 -> 9568 bytes 07-build_abe-glibc/console.log.xz | Bin 236296 -> 238680 bytes 08-build_abe-gdb/console.log.xz | Bin 52080 -> 51840 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3872 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2232 -> 2304 bytes 11-check_regression/console.log.xz | Bin 21136 -> 15800 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 95 +- 11-check_regression/mail-body.txt | 231 +- 11-check_regression/results.compare | 136 +- 11-check_regression/results.compare2 | 4995 +++++------------- 11-check_regression/results.regressions | 112 +- 12-update_baseline/console.log | 58 +- 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 | 233 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 112 +- sumfiles/gdb.log.xz | Bin 1767664 -> 1793712 bytes sumfiles/gdb.sum | 8735 +++++++++---------------------- 31 files changed, 4439 insertions(+), 10322 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/llvm-release-aarch64-mainline-allyesconfig updated (8e3e5aff51c -> 3e3453fbdb1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 8e3e5aff51c 32: onsuccess: #399: all: Success after binutils/qemu: 7 commits new 3e3453fbdb1 33: force: #401: all: Success after linux: 947 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30796 -> 30896 bytes 04-build_kernel_llvm/console.log.xz | Bin 66512 -> 64664 bytes 05-build_abe-qemu/console.log.xz | Bin 31556 -> 31380 bytes 06-build_linux/console.log.xz | Bin 3296 -> 3128 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3072 -> 2840 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 21 ++++++++++----------- results | 2 +- 17 files changed, 21 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (8b775b4c48a -> 12abd5a7d13)

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 8b775b4c48a c++: Ensure !!var is not an lvalue [PR107065] new 12abd5a7d13 IRA: Check that reg classes contain a hard reg of given mod [...] 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/ira-costs.cc | 102 ++++++++++++++++++++++++++++++--- gcc/ira.cc | 12 +++- gcc/testsuite/gcc.target/avr/pr90706.c | 9 +++ 3 files changed, 112 insertions(+), 11 deletions(-) create mode 100644 gcc/testsuite/gcc.target/avr/pr90706.c -- 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_gcc/master-aarch64 updated (eb0a812df72 -> 1344549494d)

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 eb0a812df72 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 114b54d950c 129: onsuccess: #878: 1: Success after linux: 3008 commits discards a59ffd03b85 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 40f2c854b07 127: onsuccess: #874: 1: Success after linux: 219 commits discards b873edfb9e1 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 3983e811365 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 9a7a5e10931 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 1c1e70b8fc2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards ee2540d57ae 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 28beaea1e95 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards b57f93c6513 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards d9a8c8a28a0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ea9f62379f4 118: onsuccess: #863: 1: Success after linux: 12 commits discards 6ff3132d7d8 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 98111f4c421 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards bece2447382 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 50fc123b289 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 6ca3badb38a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 039f7be4397 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards a7d943d958e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 238584d2770 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 5c306a5d3d8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards ef148a374a0 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 90ded295f93 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 23e739cd522 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 3ff33530394 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 8a9bc519481 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards cdb07163402 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 254e7784d76 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 8358f6e3d3e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards f132dc0429e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 185b025e11f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 6912fa301c4 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards f26b910eef0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 70640b6aad6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards e9ffc23e907 95: onsuccess: #835: 1: Success after binutils: 3 commits discards ae7c3439226 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 76c45efc566 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 7b749396235 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 6da28e3495a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards b2dbc8f83cf 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e1e37055a7e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 5ebd6237158 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards da1f296768f 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 9b4e1b87eda 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 916c3b09b95 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 25346cc4f12 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards b0e6507970b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards d38cf667c83 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 9fc22c350f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 23a5aebeb41 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards f72faa59585 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 40e1e907166 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards feefda5e1ce 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 1dd4336143e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 18c99d4d660 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards a05630627e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 291fc36e61e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards eb8f3d4147d 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards dca41b0f417 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards d7e647dcfe1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 8b056c69d57 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 7408e564da0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 406e18e3b8a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards f6a32f3cc0a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 0781ecead5e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 5b550b0e26a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 78d89a8cb96 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards e4ef66c2371 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 62859b94a65 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards cff0bff192f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards c511068e43b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards ffefd2ad259 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards c01de8f8575 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards b478abe1dfa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 10e58854e95 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 1d345636b10 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 87036b9635b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 4c0a2e01063 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards abe7e45da1d 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 347d0c0e246 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards cf7b2122115 49: onsuccess: #785: 1: Success after binutils: 12 commits discards a50869681b4 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 2924a829c3c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 2a1e096e51a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards b4f31a804ef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards d4d377cc802 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 480188bdbae 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards eab6ba1700c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 5dfb3ec8204 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 057646b1f7b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards ebc17140d97 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards ce5af8a3e10 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 977fc827db9 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 89a5aa9746e 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0d811c7ea7f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 4277855a722 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards fed02f0fc35 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards eb5b504417c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards d66e5b41bac 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 696dad93999 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new cc40381f780 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 0108f7392a2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 0c5d60f0331 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 9226e8c9230 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new ee083fd144a 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 7dd9bd8dfe4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new a12f942070c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new d14b38624e7 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 0de75554e63 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 113fd015e2d 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 5274893fc92 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new b6f2d17992b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 66973e0c7d5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 19c6a3614b0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 7d13eae2053 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 418f9b62581 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 5bf8c098011 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 9f860f22758 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 7dbb15e99f5 48: onsuccess: #782: 1: Success after binutils: 8 commits new f8e050bdbfd 49: onsuccess: #785: 1: Success after binutils: 12 commits new 328cad21365 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new f11795f5871 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new de581d8ad4b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 0dd819bc63a 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 07e31650e7b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 53c7bf6fb9b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new d24e658acc3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 72ba16fc4d1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 99d34b2d87d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new a5ddcc4e4ab 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new c6f03526902 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new c2e46cb15f3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new a7c512865f7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 9a544b63182 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 5ac1cbf53ed 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 8d63f46fdaf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 8d1f5624dad 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new e79350ad7cc 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new bebcdf7b72b 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new e9e90bbed37 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 79a6dd08994 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new e1cd568ad95 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new feceab5eb3e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 3c005f7c570 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new e3ecc989650 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 49357091fcc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new b0dd7d9ebe2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new fce6b274b3d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new da12c63e86d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 4647ca8c947 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 89d6c20a416 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new de18808f9c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 74b3fa503a7 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 6ff8fbb7932 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 415e6f7e841 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 19f056719af 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new bce55da6d25 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new fd9f058c1e8 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 19380184abc 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 7cc9429951a 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new e4bc3de69a1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new b525fee49fb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new a810a37af31 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 481b87cd7cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 162a79dfb2d 94: onsuccess: #832: 1: Success after binutils: 5 commits new 51de7dfebd2 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9b6522ad8fa 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 2163168a3f5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new a4c74092590 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 2d3ad4cf831 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 949c447cbcc 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new f50515b29fc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new fea0c16b1c4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 965b722df49 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new e4fe40882a9 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 5512847c147 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new e0aebccb26d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 9b5f5c2348d 107: onsuccess: #849: 1: Success after binutils: 5 commits new 33e22f09478 108: onsuccess: #850: 1: Success after gcc: 2 commits new d1684553550 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 1add1d469f3 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 21943cc6b79 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new fecb467d37f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 4d1112c6249 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 6c5b9d55d0f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new ac55f53495f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 451416b86a6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 9864670b06b 117: onsuccess: #861: 1: Success after binutils: 18 commits new a9c1005cc5e 118: onsuccess: #863: 1: Success after linux: 12 commits new 7614e887157 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new bb213ee53d9 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 488efe52b4a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 591eb85960a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 6c8e7fab85a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 0288c8245e2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 65335292f43 125: onsuccess: #871: 1: Success after binutils: 26 commits new 2d4ba349dab 126: onsuccess: #873: 1: Success after glibc: 2 commits new e52cd1c3b56 127: onsuccess: #874: 1: Success after linux: 219 commits new 081e61f18ce 128: onsuccess: #876: 1: Success after binutils: 12 commits new ede079a96a0 129: onsuccess: #878: 1: Success after linux: 3008 commits new 937a2d87ae9 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 1344549494d 131: onsuccess: #880: 1: 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 (eb0a812df72) \ 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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39904 -> 39540 bytes 04-build_abe-gcc/console.log.xz | Bin 215636 -> 215176 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10200 -> 9600 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 244740 bytes 08-build_abe-gdb/console.log.xz | Bin 39116 -> 39328 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2892 -> 2780 bytes 11-check_regression/console.log.xz | Bin 8164 -> 7508 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 18 +- 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 34 +- 11-check_regression/results.compare2 | 276 +- 11-check_regression/results.regressions | 34 +- 12-update_baseline/console.log | 60 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 34 +- sumfiles/g++.log.xz | Bin 3733672 -> 3754172 bytes sumfiles/g++.sum | 135 +- sumfiles/gcc.log.xz | Bin 3317548 -> 3350216 bytes sumfiles/gcc.sum | 4765 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085196 -> 1081024 bytes sumfiles/gfortran.sum | 103 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2284 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232824 -> 233108 bytes sumfiles/libgomp.sum | 28 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456388 -> 449368 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2883 insertions(+), 2802 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 (38665d717a3 -> 2e55fbce03a)

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 38665d717a3 gdb: use gdb_assert not internal_error new c573941878c Remove subset_compare new 2e55fbce03a Move streq and compare_cstrings to gdbsupport The 2 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/stack.c | 6 +++--- gdb/tui/tui-win.c | 4 ++-- gdb/utils.c | 28 ---------------------------- gdb/utils.h | 14 -------------- gdbsupport/common-utils.h | 16 ++++++++++++++++ 5 files changed, 21 insertions(+), 47 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-aarch64-mainline-defconfig updated (33fad34556c -> a179936a5a2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-mainline-defconfig in repository toolchain/ci/base-artifacts. from 33fad34556c 29: onsuccess: #430: boot: Success after binutils/gcc/linux [...] new a179936a5a2 30: onsuccess: #431: 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 1748 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30212 -> 30900 bytes 04-build_abe-stage1/console.log.xz | Bin 68700 -> 68856 bytes 05-build_abe-qemu/console.log.xz | Bin 30720 -> 31864 bytes 06-build_linux/console.log.xz | Bin 3104 -> 3116 bytes 07-boot_linux/console.log.xz | Bin 6124 -> 6164 bytes 08-check_regression/console.log.xz | Bin 3680 -> 4280 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 20 files changed, 30 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022