Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig updated (c08d2566d84 -> bef31d25d35)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from c08d2566d84 33: onsuccess: #514: boot: Success after binutils/gcc/linux [...] new bef31d25d35 34: onsuccess: #515: 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32896 -> 31800 bytes 04-build_abe-stage1/console.log.xz | Bin 73208 -> 73864 bytes 05-build_abe-qemu/console.log.xz | Bin 31064 -> 31012 bytes 06-build_linux/console.log.xz | Bin 6576 -> 6580 bytes 07-boot_linux/console.log.xz | Bin 6220 -> 6224 bytes 08-check_regression/console.log.xz | Bin 4024 -> 4080 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 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_kernel/gnu-release-arm-mainline-allmodconfig updated (a2a647f6045 -> 10953a2141c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from a2a647f6045 33: force: #443: boot: Success after linux: 8 commits new 10953a2141c 34: force: #444: boot: Success after v6.1-rc4-9-g9ed2b4616d [...] 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 -> 1892 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30652 bytes 04-build_abe-stage1/console.log.xz | Bin 87376 -> 88132 bytes 05-build_abe-qemu/console.log.xz | Bin 30516 -> 30788 bytes 06-build_linux/console.log.xz | Bin 3220 -> 3240 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 2852 -> 2720 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- 15 files changed, 14 insertions(+), 14 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 (5fc9d07f32b -> 1ac65e0f946)

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 5fc9d07f32b 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards b2ce6fa2977 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 315b4cdc6f0 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards 94a7caa2901 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards 7240a4e7b4a 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards 8f1dafe369f 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards bc64edb37ce 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards 9907a2a484f 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards 603ac498388 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards 5cee533b7dd 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-4 [...] discards b7ba822438f 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 6fb79adbf9f 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards fc7a14cd20d 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] discards 509f429fc16 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] discards 83166f1646d 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards 74c268df30e 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards 63a2ec49e87 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] discards 529600e4f99 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 28ca124c629 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards cb14efa38bb 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards c0b20070739 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards 94dadd38ada 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards 0cbe9477c14 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 78307094425 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards 2cb70949995 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards 8835c4ac426 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 7a2ef84a5f9 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards ed1fd36e91a 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 0f57bc30df1 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards 1b33060db51 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 78611549640 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards b07b32e7afb 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 6af430e7fb1 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 529cc5cff79 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards cd507dda0b4 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards c937dbbb361 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards d02a0dd7149 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 8e95d1b0de8 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 26723defebe 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards 6de107c0437 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards a52cbeabd28 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards a7de4e4fc59 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 0ae0f38046e 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards d1bc2c1f504 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 9f9d8119da9 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards fcd5f26e8db 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 55677707c48 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards c38bacb7a73 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards b0314cd9022 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 383b2ae46ea 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 62d2600837c 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards a336553d572 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 5751647ef67 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 466998053ea 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 6aac3966cf8 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 0af6b0df415 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 6d558dbaf36 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 5e7377f0b9a 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards f9138a7834d 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 95f68615193 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 8305722ea9b 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 8bfb25a1b4b 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards ca5878d6c0e 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 0f530f091b4 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 6d1f94ae945 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 197627a0c0e 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 2a73c753f8a 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 6c9a528b12f 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards c0b072f1644 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 452ca67a6e8 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards aa14b3a8d3f 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards fd5f6a9c373 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 3ff611cbd5d 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 75abc67bd19 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 5bac5980df1 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards be674d558c9 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards c474f017492 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 56cdd68f8a7 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 9913c0c9e77 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards a4561ad64fe 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards eb41b95ad86 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 3f65b0566c0 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards eace1eb7a79 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards be2ec1e595d 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 7a77351a803 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards ebe4192fb2f 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 8a5b199bac9 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards cbb9eaa22c9 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards ae79926121f 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards a3c89785340 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 08686fd12b4 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 8eee808f636 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards f91b4957a2e 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 80e0836e745 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards a955633d679 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards be5a795178e 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 828b28ccaa2 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 49722cd52c8 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 1ab0b670db0 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 9fb7edd52c3 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards cf381469eda 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new dfe0a7cf90a 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 0daed2e5c58 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 189987ec4e9 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 51e20e21e32 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 4da0eee9ad3 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 094cd650870 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 52badd6f298 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 295094f2136 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 18d09a68487 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 9cca4843a25 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new b013baa2095 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 183e0358564 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new 041062de170 329: onsuccess: #2285: 1: Success after gcc: 8 commits new f21bf2eb7c3 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 75190da9fcd 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 161104cc41e 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 797b9001bf0 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 951300b2c70 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 92a0176683f 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 0c41951e921 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new b88dd64bcbb 337: onsuccess: #2293: 1: Success after gcc: 21 commits new dd2828b8214 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 28163ddb28e 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 23caaeb9ade 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 45de0c2ca9b 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 4818e9012ae 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 1d35f61a977 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 8cc4766375d 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new e17aa4057da 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new d04568a5694 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 0ecd9d52072 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 0126b650bac 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new effa108dbf1 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 56274ec2fef 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 38417aeec27 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 0e22666d257 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 61eb0faa12b 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 98d4041423e 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new ca38c23f379 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 7c1649c16fe 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 652ddd26838 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new a05e8dd9d00 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new acb59b71157 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 5d936f036e5 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 03ad1890108 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 50bd30d7e98 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new a7143d860b9 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new d74c7291324 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 45300d26489 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 8f566d9e4e8 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 69562f0f6ad 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 68a6de749e1 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 77355f28ca3 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new e9522c119ec 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new c347ce06494 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 05898057927 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 5efde966dcf 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 047bfe5832e 374: onsuccess: #2336: 1: Success after gcc: 4 commits new e2ae45251f8 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 9d13a191c8e 376: onsuccess: #2338: 1: Success after gcc: 2 commits new fe8222ac6c4 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new b7a90490dfd 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 714b30d21d5 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 326c0ebe14a 380: onsuccess: #2342: 1: Success after gcc: 3 commits new b954059ef27 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 6fe390ddbe2 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new e33c09701e2 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 7fa824a0300 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new 2c8c6a6ebea 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 0c43e02b7af 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new feb28c0f4f7 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 5ecd19be89e 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 34ad7d6ebb7 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new df7af43fab6 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 856dd809ee8 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 8bf98224a14 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 69f5e49fe71 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 9721dc4fb8f 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new f002b2e74d6 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new 86cb43c6a2d 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new d901c8ac871 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new d1f0e7679b4 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new 803111941b1 399: onsuccess: #2361: 1: Success after gcc: 10 commits new ac9a727dcaa 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new d641111d58c 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] new 6e0a3b49009 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new 524d6d195dc 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 670769975a0 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] new d79b33be1c2 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] new f0e19722826 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new 37c8e461fd0 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new 1f87a402205 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-4 [...] new 87c6bea33b0 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new 0e86e514281 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new 87f083dd856 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new 29763312b27 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new ffe212ed8fc 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new cc9363645e4 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new ddf53071a4b 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new 46bb3bd858b 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new 200099e70e7 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 1ac65e0f946 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 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 (5fc9d07f32b) \ 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 1776 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 39776 -> 40260 bytes 04-build_abe-gcc/console.log.xz | Bin 215592 -> 226552 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3836 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3020 -> 13196 bytes 07-check_regression/console.log.xz | Bin 4824 -> 5772 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 78 +- 07-check_regression/results.regressions | 27 + 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 3637356 -> 3613892 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 3147296 -> 3145276 bytes sumfiles/gcc.sum | 4927 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1051488 -> 1056956 bytes sumfiles/gfortran.sum | 73 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220040 -> 220528 bytes sumfiles/libgomp.sum | 20 +- sumfiles/libitm.log.xz | Bin 2548 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452664 -> 450932 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2837 insertions(+), 2623 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create 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_gnu_native_check_gdb/master-arm updated (edfce0140e1 -> 3da92104b26)

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 edfce0140e1 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 032d01edfff 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards fe74fbd97f0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 94a7bba572c 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 71abdf17b2c 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 73cd0e72f80 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 8f1471e5f1e 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 2db6639bfa4 125: onsuccess: #614: 1: Success after linux: 12 commits discards af769c62c56 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 9e56e662248 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards e251653cf82 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 1216cc12c59 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 2623ec9338f 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards e03d62cd937 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 365921a03f8 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards e7058b2be77 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 8948b8f80bb 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 42adc6a2dd3 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 7b7c127936b 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards a361f90f8fb 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 31b39c452b8 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards a07734ab802 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 3bfa53475a4 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 39d5b958796 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 1798656031c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards ae288bbfa41 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 07030d28b93 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 77e3f62bd67 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards ab5f3d0860b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards c898edc2e56 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 1b70a335249 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 6f83927a3d4 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards c1b48d11614 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 0ab4fea1195 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 1aac19d79d4 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards b233e9f036d 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards d25926e0eb6 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 9e2d6af17e1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards d1609c2da90 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 5f86fc705fc 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 0e2f69601dc 92: onsuccess: #575: 1: Success after linux: 34 commits discards 358f0e49d9b 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 0072725d659 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 5503b040b1c 89: onsuccess: #570: 1: Success after linux: 11 commits discards 8c95a029fe7 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f030da53f5a 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 1b2138701ef 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 712b09b28f3 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 9edf75f3a94 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 923e36cc960 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 6afd01b7c02 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards b835465a7a1 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 93490605e94 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards cc03382d2c1 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 1ad18c527a8 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 2239fc9449e 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards b1c659940c0 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 0e69fa04af4 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 9c9e8d84eda 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 32cd67fc33b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 730d587e49c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 91070748479 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards a5d95054573 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 622299cad13 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards 515bf13e8e4 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 9472e2eeec6 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards cbf7b1d520a 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 04744b812d6 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards f7eda7ce4b8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 646f73fef9d 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 4de21266379 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards dbced033885 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 417f85b544d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards a1e82aee1a5 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 9edc3e6f368 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards c233fc459d9 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 7e087845b03 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 2f69f6f989c 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 46b7fd22442 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 2ccebaecaa4 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 28a93713a57 52: onsuccess: #528: 1: Success after binutils: 8 commits discards dceee58a9fe 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 1b68ccd2aca 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards b8c1449bbf4 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 699a0767845 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards 06c5803d92c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards 05e3ddd4531 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 8a9ce6e0afc 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 057b8dabc28 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards f73d94a950b 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 607cddd9fad 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards e3cfe7d3c0b 41: onsuccess: #514: 1: Success after linux: 64 commits discards 6d047ccb078 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards 266f32f4aaa 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 31810e09577 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 61d7c607281 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 5e355b3e9db 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 89e1e27284a 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 080753a32be 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 1bc9936e7f2 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards 70bd323b627 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 4740dea1622 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 42d2cfea3e7 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new 342853f7e3b 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 57c1d92b987 35: onsuccess: #503: 1: Success after binutils: 11 commits new 9602ff6dd2f 36: onsuccess: #505: 1: Success after glibc: 3 commits new 97554bb921c 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 309fde3e24e 38: onsuccess: #508: 1: Success after binutils: 3 commits new 519ba5ef31e 39: onsuccess: #511: 1: Success after binutils: 8 commits new 6d8b674e773 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 6d9b7c367a4 41: onsuccess: #514: 1: Success after linux: 64 commits new 9c9157595f9 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 9b641be1e82 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new d14fe4936f0 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new e32a6f1852d 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new 00a3c81f7fd 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new f6fc6d8c3a6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 811c54c2649 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new 2bf908cf9d8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new e700b31ba77 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 1ad047a61d8 51: onsuccess: #525: 1: Success after binutils: 8 commits new 1bbfa7f8a9d 52: onsuccess: #528: 1: Success after binutils: 8 commits new c7b7164131e 53: onsuccess: #531: 1: Success after binutils: 12 commits new 29c1a6ff6ed 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new c6c73151152 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 55ce0d8980b 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new d5edb4567bd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new b3e2ea63343 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new e8480a09227 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 458f037f165 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 5e914a49aec 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 0ec48d6a651 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 8343b6dbd0f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 4cc0443fe1f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new e328b8d9c04 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new ebe5daccb40 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new ff9c057b3c5 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 5e15932a964 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new f8fa42ae4bc 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new 0eb6a15f342 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 63f1dc89daa 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 4089362b665 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new ab86efe3b88 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 5f8cd541d59 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 4b42da16f25 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 58294a0efe7 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new f1c2145e0f9 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new d11226e2bb1 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new 694b2fd2644 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 3e34f142b45 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new 333f647af68 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 2a97fc36dad 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 76c6bdcd0c3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new 7863852900f 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 5fd132d85c1 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new f2fd82468a4 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new cbe4a6aad20 87: onsuccess: #567: 1: Success after binutils: 8 commits new 7e44545e8b0 88: onsuccess: #569: 1: Success after glibc: 10 commits new 18a8c3b7208 89: onsuccess: #570: 1: Success after linux: 11 commits new bb56afa5f77 90: onsuccess: #572: 1: Success after binutils: 15 commits new f3c15fe54eb 91: onsuccess: #574: 1: Success after glibc: 3 commits new e237871269d 92: onsuccess: #575: 1: Success after linux: 34 commits new a268a2f3193 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 5eac8ef43ff 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 4d3d5233ca2 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 70595ba1064 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new b387ef2e15a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 47f4f8618a4 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 5034a7f09c7 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new f6513ea402e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 0bdbbf853c0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new f799b9206cc 102: onsuccess: #586: 1: Success after binutils: 5 commits new fec6c09c54b 103: onsuccess: #589: 1: Success after binutils: 3 commits new 4d0f56783f8 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new ca787b457c4 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 5bc93700477 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 8814cd202c8 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 93f836168de 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 58f9bf09231 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 1997cd948c7 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new eb9e05113ef 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 7b6246a60e2 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 8750b9dcab7 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 90a9b435851 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new c28ae012dd2 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 2a8a4e86a3d 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 6f22ab7b241 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new cb81da8807c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new edb378b1b29 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 083471dac0a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 24706562c2f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 533086fabd0 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 64b08d0af90 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 952942b8d7e 124: onsuccess: #612: 1: Success after binutils: 18 commits new fcbc4f45329 125: onsuccess: #614: 1: Success after linux: 12 commits new db3e9ac2a29 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new e5c1eb2a1d9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new fe632255b86 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 7f0b7b92c38 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new a7bdff8ba9e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new b4751dceff2 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new d56b3e40644 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 3da92104b26 133: onsuccess: #623: 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 (edfce0140e1) \ 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 1736 -> 1900 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53656 -> 53524 bytes 04-build_abe-gcc/console.log.xz | Bin 237576 -> 237636 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9460 -> 10348 bytes 07-build_abe-glibc/console.log.xz | Bin 237668 -> 236296 bytes 08-build_abe-gdb/console.log.xz | Bin 51004 -> 52080 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2384 -> 2232 bytes 11-check_regression/console.log.xz | Bin 10356 -> 21136 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 96 +- 11-check_regression/mail-body.txt | 219 +- 11-check_regression/results.compare | 144 +- 11-check_regression/results.compare2 | 5672 ++++++++++++++-- 11-check_regression/results.regressions | 133 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 221 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 133 +- sumfiles/gdb.log.xz | Bin 1764732 -> 1767664 bytes sumfiles/gdb.sum | 10869 +++++++++++++++++------------- 31 files changed, 12148 insertions(+), 5431 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_gcc/master-aarch64 updated (05df84e8113 -> eb0a812df72)

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 05df84e8113 129: onsuccess: #878: 1: Success after linux: 3008 commits discards ba10a267310 128: onsuccess: #876: 1: Success after binutils: 12 commits discards abea1408b26 127: onsuccess: #874: 1: Success after linux: 219 commits discards 0d34824c44a 126: onsuccess: #873: 1: Success after glibc: 2 commits discards a4beb986f30 125: onsuccess: #871: 1: Success after binutils: 26 commits discards f713ea5033d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 79e68a4058f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards be777a4b198 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards e000dbb8e55 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 6efcbc34eb2 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 03663f03b6a 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards d5307d874b1 118: onsuccess: #863: 1: Success after linux: 12 commits discards 462bdd55640 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 8770a938e9a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 25f10302e95 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 4e0f30621e8 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 54e9ec3fa2a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards ad34133894a 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 22b2f0f3aec 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards b8e390ef567 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 634f5c4483e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 466b8e1331d 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 68ff76dd74e 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 3359d0e26c3 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards b5d6ebeab31 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 1c2291b42ca 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards d86af9f0bd0 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards bacf8009211 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards cab44ad61bc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 3ecbdfc1247 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 87812bbff02 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 54c5155be76 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 19974f710d1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 7efed152dd7 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 0f0578be1d6 95: onsuccess: #835: 1: Success after binutils: 3 commits discards db6c814964f 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 1c040f5128e 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards b379f29e26d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 61090bd8f47 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards cfcdad1ffca 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards f8265cb0984 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 3de0d66f817 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards d9f926a1a06 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 36d87104a84 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 92d986141a4 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 5945c6caccd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 1754e1dadb8 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 09b84958170 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 41c72e340b1 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 8a65176e83f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards fd23ecc286b 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 3f96c08b638 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 02b92768198 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards b7ed11b59e0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards db4fe159f57 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards ff6008e71cf 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards f3f29123c0c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 77813345893 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards c6bbba2119d 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 7d1d2fdcc26 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards b13d82df5a4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards d24ed20b888 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 591a0ea7e44 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 9519f381a52 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8fe7888fe2e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards efeb8846d53 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards d56af85e434 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards b125aa0f46a 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c545a1aefff 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f80542befc0 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards ecd3019385d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards e67790bf8f7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 8a28edfd87f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 8cd408906b8 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards f5c2f57af42 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards de1c1ebcc2b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 06374c0c6ab 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 13a3aca08d4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 202bc0225fb 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards f64dc710e52 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards e353fabb9a7 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 634bce0b4a2 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 04e85c75cd5 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 9d89c49e640 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards f29321bcd62 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 5cc92ed8198 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 10e66dff5b1 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards ff1c3753c53 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 182513b1cc3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 169ec236231 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 28c3622e374 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 89180703d05 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 46526b3116b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards afc24e91073 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 919b05ae5da 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 61ca5b67fd5 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 12742a20788 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 2147795ec38 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards ca7b1f9ff6b 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards ad47126dd38 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 43ea4a71228 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 6f85cf92333 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 696dad93999 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new d66e5b41bac 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new eb5b504417c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new fed02f0fc35 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 4277855a722 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 0d811c7ea7f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 89a5aa9746e 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 977fc827db9 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new ce5af8a3e10 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new ebc17140d97 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 057646b1f7b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 5dfb3ec8204 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new eab6ba1700c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 480188bdbae 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new d4d377cc802 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new b4f31a804ef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 2a1e096e51a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 2924a829c3c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new a50869681b4 48: onsuccess: #782: 1: Success after binutils: 8 commits new cf7b2122115 49: onsuccess: #785: 1: Success after binutils: 12 commits new 347d0c0e246 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new abe7e45da1d 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 4c0a2e01063 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 87036b9635b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 1d345636b10 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 10e58854e95 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new b478abe1dfa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new c01de8f8575 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new ffefd2ad259 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new c511068e43b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new cff0bff192f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 62859b94a65 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new e4ef66c2371 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 78d89a8cb96 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 5b550b0e26a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 0781ecead5e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new f6a32f3cc0a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 406e18e3b8a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 7408e564da0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 8b056c69d57 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new d7e647dcfe1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new dca41b0f417 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new eb8f3d4147d 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 291fc36e61e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new a05630627e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 18c99d4d660 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 1dd4336143e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new feefda5e1ce 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 40e1e907166 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new f72faa59585 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 23a5aebeb41 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 9fc22c350f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new d38cf667c83 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new b0e6507970b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 25346cc4f12 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 916c3b09b95 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 9b4e1b87eda 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new da1f296768f 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 5ebd6237158 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new e1e37055a7e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new b2dbc8f83cf 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 6da28e3495a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 7b749396235 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 76c45efc566 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new ae7c3439226 94: onsuccess: #832: 1: Success after binutils: 5 commits new e9ffc23e907 95: onsuccess: #835: 1: Success after binutils: 3 commits new 70640b6aad6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new f26b910eef0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 6912fa301c4 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 185b025e11f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new f132dc0429e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 8358f6e3d3e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 254e7784d76 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new cdb07163402 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 8a9bc519481 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 3ff33530394 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 23e739cd522 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 90ded295f93 107: onsuccess: #849: 1: Success after binutils: 5 commits new ef148a374a0 108: onsuccess: #850: 1: Success after gcc: 2 commits new 5c306a5d3d8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 238584d2770 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a7d943d958e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 039f7be4397 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 6ca3badb38a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 50fc123b289 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new bece2447382 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 98111f4c421 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 6ff3132d7d8 117: onsuccess: #861: 1: Success after binutils: 18 commits new ea9f62379f4 118: onsuccess: #863: 1: Success after linux: 12 commits new d9a8c8a28a0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new b57f93c6513 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 28beaea1e95 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new ee2540d57ae 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 1c1e70b8fc2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 9a7a5e10931 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 3983e811365 125: onsuccess: #871: 1: Success after binutils: 26 commits new b873edfb9e1 126: onsuccess: #873: 1: Success after glibc: 2 commits new 40f2c854b07 127: onsuccess: #874: 1: Success after linux: 219 commits new a59ffd03b85 128: onsuccess: #876: 1: Success after binutils: 12 commits new 114b54d950c 129: onsuccess: #878: 1: Success after linux: 3008 commits new eb0a812df72 130: onsuccess: #879: 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 (05df84e8113) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 40276 -> 39904 bytes 04-build_abe-gcc/console.log.xz | Bin 216032 -> 215636 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9456 -> 10200 bytes 07-build_abe-glibc/console.log.xz | Bin 245304 -> 244148 bytes 08-build_abe-gdb/console.log.xz | Bin 39460 -> 39116 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2892 bytes 11-check_regression/console.log.xz | Bin 4848 -> 8164 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 200 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 44 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 3769128 -> 3733672 bytes sumfiles/g++.sum | 125 +- sumfiles/gcc.log.xz | Bin 3297096 -> 3317548 bytes sumfiles/gcc.sum | 5305 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1073704 -> 1085196 bytes sumfiles/gfortran.sum | 140 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232008 -> 232824 bytes sumfiles/libgomp.sum | 20 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451356 -> 456388 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 3239 insertions(+), 2815 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (c7020e1b346d -> 6f1f5caed5bf)

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 linux. from c7020e1b346d Merge tag 'pci-v6.2-changes' of git://git.kernel.org/pub/s [...] new 9a48b4a6fd51 xfs: fully initialize xfs_da_args in xchk_directory_blocks new be1317fdb8d4 xfs: don't track the AGFL buffer in the scrub AG context new 3e59c0103e66 xfs: log the AGI/AGF buffers when rolling transactions dur [...] new b255fab0f80c xfs: make AGFL repair function avoid crosslinked blocks new 823ca26a8f07 Merge tag 'scrub-fix-ag-header-handling-6.2_2022-11-16' of [...] new 48ff40458f87 xfs: standardize GFP flags usage in online scrub new fcd2a43488d5 xfs: initialize the check_owner object fully new 306195f355bb xfs: pivot online scrub away from kmem.[ch] new af1077fa87c3 Merge tag 'scrub-cleanup-malloc-6.2_2022-11-16' of git://g [...] new a7a0f9a5503f xfs: return EINTR when a fatal signal terminates scrub new 0a713bd41ea2 xfs: fix return code when fatal signal encountered during [...] new 6bf2f8791597 xfs: don't retry repairs harder when EAGAIN is returned new 93b0c58ed04b xfs: don't return -EFSCORRUPTED from repair when resources [...] new 3d8426b13bac Merge tag 'scrub-fix-return-value-6.2_2022-11-16' of git:/ [...] new 9e13975bb062 xfs: load rtbitmap and rtsummary extent mapping btrees at [...] new 5f369dc5b4eb xfs: make rtbitmap ILOCKing consistent when scanning the r [...] new b76f593b33aa Merge tag 'scrub-fix-rtmeta-ilocking-6.2_2022-11-16' of gi [...] new 11f97e684583 xfs: skip fscounters comparisons when the scan is incomplete new e74331d6fa2c xfs: online checking of the free rt extent count new 7aab8a05e7c7 Merge tag 'scrub-fscounters-enhancements-6.2_2022-11-16' o [...] new 033985b6fe87 xfs: fix perag loop in xchk_bmap_check_rmaps new 6a5777865eeb xfs: teach scrub to check for adjacent bmaps when rmap lar [...] new 830ffa09fb13 xfs: block map scrub should handle incore delalloc reservations new f23c40443d1c xfs: check quota files for unwritten extents new 31785537010a xfs: check that CoW fork extents are not shared new 5eef46358fae xfs: teach scrub to flag non-extents format cow forks new cc5f38fa12fc Merge tag 'scrub-bmap-enhancements-6.2_2022-11-16' of git: [...] new bd5ab5f98741 xfs: don't warn about files that are exactly s_maxbytes long new f36b954a1f1b xfs: check inode core when scrubbing metadata files new 7b082b5e8afa Merge tag 'scrub-check-metadata-inode-records-6.2_2022-11- [...] new 2653d53345bd xfs: fix incorrect error-out in xfs_remove new 59f6ab40fd87 xfs: fix sb write verify for lazysbcount new 64c80dfd04d1 xfs: Print XFS UUID on mount and umount events. new 28b4b0596343 xfs: fix incorrect i_nlink caused by inode racing new 118e021b4b66 xfs: write page faults in iomap are not buffered writes new 198dd8aedee6 xfs: punching delalloc extents on write failure is racy new b71f889c18ad xfs: use byte ranges for write cleanup ranges new 9c7babf94a0d xfs,iomap: move delalloc punching to iomap new f43dc4dc3eff iomap: buffered write failure should not truncate the page cache new 7348b322332d xfs: xfs_bmap_punch_delalloc_range() should take a byte range new d7b64041164c iomap: write iomap validity checks new 304a68b9c63b xfs: use iomap_valid method to detect stale cached iomaps new 6e8af15ccdc4 xfs: drop write error injection is unfixable, remove it new 7dd73802f97d Merge tag 'xfs-iomap-stale-fixes' of git://git.kernel.org/ [...] new c2beff99eb03 xfs: add debug knob to slow down writeback for fun new 254e3459285c xfs: add debug knob to slow down write for fun new cd14f15b0e64 Merge tag 'iomap-write-race-testing-6.2_2022-11-30' of git [...] new 032e160305f6 xfs: invalidate block device page cache during unmount new fd5beaff250d xfs: use memcpy, not strncpy, to format the attr prefix du [...] new e5827a007aa4 xfs: shut up -Wuninitialized in xfsaild_push new 4c6dbfd2756b xfs: attach dquots to inode before reading data/cow fork mappings new 4b4d11bbeca4 Merge tag 'random-fixes-6.2_2022-11-30' of git://git.kerne [...] new 1eb52a6a7198 xfs: wait iclog complete before tearing down AIL new 575689fc0ffa xfs: fix super block buf log item UAF during force shutdown new 9d720a5a658f xfs: hoist refcount record merge predicates new b25d1984aa88 xfs: estimate post-merge refcounts correctly new 948961964b24 Merge tag 'maxrefcount-fixes-6.2_2022-12-01' of git://git. [...] new 8c25febf2396 xfs: get rid of assert from xfs_btree_islastblock new ddfdd530e43f xfs: invalidate xfs_bufs when allocating cow extents new 1f5619ed8810 xfs: Remove duplicated include in xfs_iomap.c new 52f31ed22821 xfs: dquot shrinker doesn't check for XFS_DQFLAG_FREEING new 87be949912ee Merge tag 'xfs-6.2-merge-8' of git://git.kernel.org/pub/sc [...] new e4b731ccb097 ceph: remove useless session parameter for check_caps() new 68c62bee9d08 ceph: try to check caps immediately after async creating finishes new cfb3162495fe Merge tag 'ceph-for-6.2-rc1' of https://github.com/ceph/ce [...] new b3525072835b orangefs: remove variable i new 610defdccff7 orangefs: remove redundant assignment to variable buffer_index new ea60a4ad0cf8 orangefs: Fix sysfs not cleanup when dev init failed new d23417a5bf3a orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string() new 1f2c0e8a587b orangefs: Fix kmemleak in orangefs_sysfs_init() new 31720a2b109b orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init() new 6f1f5caed5bf Merge tag 'for-linus-6.2-ofs1' of git://git.kernel.org/pub [...] The 72 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: fs/ceph/addr.c | 2 +- fs/ceph/caps.c | 25 ++-- fs/ceph/file.c | 26 +++-- fs/ceph/inode.c | 6 +- fs/ceph/ioctl.c | 2 +- fs/ceph/super.h | 5 +- fs/iomap/buffered-io.c | 254 ++++++++++++++++++++++++++++++++++++++++- fs/iomap/iter.c | 19 ++- fs/orangefs/file.c | 1 - fs/orangefs/inode.c | 2 - fs/orangefs/orangefs-debugfs.c | 29 +---- fs/orangefs/orangefs-mod.c | 8 +- fs/orangefs/orangefs-sysfs.c | 71 ++++++++++-- fs/xfs/libxfs/xfs_bmap.c | 8 +- fs/xfs/libxfs/xfs_btree.h | 1 - fs/xfs/libxfs/xfs_errortag.h | 18 +-- fs/xfs/libxfs/xfs_refcount.c | 146 ++++++++++++++++++++--- fs/xfs/libxfs/xfs_sb.c | 4 +- fs/xfs/scrub/agheader.c | 47 +++++--- fs/xfs/scrub/agheader_repair.c | 81 ++++++++++--- fs/xfs/scrub/attr.c | 11 +- fs/xfs/scrub/bitmap.c | 11 +- fs/xfs/scrub/bmap.c | 147 +++++++++++++++++++----- fs/xfs/scrub/btree.c | 14 ++- fs/xfs/scrub/common.c | 48 +++++--- fs/xfs/scrub/common.h | 2 +- fs/xfs/scrub/dabtree.c | 4 +- fs/xfs/scrub/dir.c | 10 +- fs/xfs/scrub/fscounters.c | 109 +++++++++++++++++- fs/xfs/scrub/inode.c | 2 +- fs/xfs/scrub/quota.c | 8 +- fs/xfs/scrub/refcount.c | 12 +- fs/xfs/scrub/repair.c | 51 ++++++--- fs/xfs/scrub/scrub.c | 6 +- fs/xfs/scrub/scrub.h | 18 +-- fs/xfs/scrub/symlink.c | 2 +- fs/xfs/xfs_aops.c | 32 +++--- fs/xfs/xfs_bmap_util.c | 10 +- fs/xfs/xfs_bmap_util.h | 2 +- fs/xfs/xfs_buf.c | 1 + fs/xfs/xfs_buf_item.c | 2 + fs/xfs/xfs_error.c | 46 ++++++-- fs/xfs/xfs_error.h | 13 +++ fs/xfs/xfs_file.c | 2 +- fs/xfs/xfs_fsmap.c | 4 +- fs/xfs/xfs_icache.c | 6 + fs/xfs/xfs_inode.c | 2 +- fs/xfs/xfs_iomap.c | 185 ++++++++++++++++++------------ fs/xfs/xfs_iomap.h | 6 +- fs/xfs/xfs_log.c | 46 +++++--- fs/xfs/xfs_mount.c | 15 +++ fs/xfs/xfs_pnfs.c | 6 +- fs/xfs/xfs_qm.c | 16 ++- fs/xfs/xfs_rtalloc.c | 60 +++++++++- fs/xfs/xfs_super.c | 2 +- fs/xfs/xfs_trace.c | 2 + fs/xfs/xfs_trace.h | 86 ++++++++++++++ fs/xfs/xfs_trans_ail.c | 4 +- fs/xfs/xfs_xattr.c | 2 +- include/linux/iomap.h | 47 ++++++-- 60 files changed, 1425 insertions(+), 382 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-lts-defconfig updated (4078fc7600f -> e1888711ee0)

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-defconfig in repository toolchain/ci/base-artifacts. from 4078fc7600f 29: onsuccess: #283: boot: Success after binutils/linux/qem [...] new e1888711ee0 30: onsuccess: #284: 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 1732 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30112 -> 30092 bytes 04-build_kernel_llvm/console.log.xz | Bin 62708 -> 64248 bytes 05-build_abe-qemu/console.log.xz | Bin 30712 -> 30568 bytes 06-build_linux/console.log.xz | Bin 3612 -> 3468 bytes 07-boot_linux/console.log.xz | Bin 5796 -> 5800 bytes 08-check_regression/console.log.xz | Bin 3448 -> 3504 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_gcc_bootstrap/release-arm-bootstrap_profiled_lto updated (10810c368c0 -> 1f0abb87ae0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from 10810c368c0 34: onsuccess: #147: 2: Success after binutils/gcc: 8 commits new 1f0abb87ae0 35: onsuccess: #148: 2: Success after binutils/gcc: 19 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 1716 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 51476 -> 52296 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 944480 -> 949628 bytes 06-check_regression/console.log.xz | Bin 2760 -> 2800 bytes 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 16 insertions(+), 16 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-master-aarch64-stable-defconfig updated (c784a9e5452 -> 0cb316a5a7f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from c784a9e5452 30: onsuccess: #484: boot: Success after binutils/llvm/linu [...] new 0cb316a5a7f 31: onsuccess: #485: boot: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32792 -> 32032 bytes 04-build_kernel_llvm/console.log.xz | Bin 67000 -> 66244 bytes 05-build_abe-qemu/console.log.xz | Bin 31288 -> 31592 bytes 06-build_linux/console.log.xz | Bin 4552 -> 3444 bytes 07-boot_linux/console.log.xz | Bin 6256 -> 6256 bytes 08-check_regression/console.log.xz | Bin 4212 -> 4360 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 27 insertions(+), 27 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_fast_check_gdb/master-aarch64 updated (bb4e12aee81 -> 474dfa97acb)

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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from bb4e12aee81 42: onsuccess: #53: 1: Success after linux: 3008 commits new 474dfa97acb 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40288 -> 39672 bytes 04-build_abe-gcc/console.log.xz | Bin 215592 -> 214168 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9444 -> 10320 bytes 07-build_abe-glibc/console.log.xz | Bin 244352 -> 245596 bytes 08-build_abe-gdb/console.log.xz | Bin 39612 -> 39816 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3872 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2716 -> 2552 bytes 11-check_regression/console.log.xz | Bin 4704 -> 6128 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14588 -> 14612 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 26 files changed, 59 insertions(+), 46 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