Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allyesconfig updated (9045e44284 -> 8fb09437ae)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from 9045e44284 49: force: #454: 21626: Failure after linux: 88 commits new 8fb09437ae 50: onsuccess: #455: 21642: 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 1768 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30532 -> 31288 bytes 04-build_kernel_llvm/console.log.xz | Bin 66024 -> 64780 bytes 05-build_abe-qemu/console.log.xz | Bin 31348 -> 32128 bytes 06-build_linux/console.log.xz | Bin 3760 -> 3708 bytes 08-check_regression/console.log.xz | Bin 3292 -> 3916 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 26 ++++++++++++-------------- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 ----------- 08-check_regression/trigger-bisect | 2 -- 09-update_baseline/console.log | 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 | 26 ++++++++++++-------------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 13 +------------ 22 files changed, 51 insertions(+), 76 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (90e84881d3 -> da13210b31)

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_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 90e84881d3 44: onsuccess: #167: 1: Success after binutils/gcc: 14 commits new da13210b31 45: onsuccess: #168: 1: Success after binutils/gcc: 7 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 1736 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 51344 -> 52264 bytes 04-build_abe-bootstrap/console.log.xz | Bin 462716 -> 464012 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3936 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2700 -> 2448 bytes 07-check_regression/console.log.xz | Bin 5644 -> 5384 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 53 +- 07-check_regression/results.regressions | 27 - 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 | 20 +- results | 27 - sumfiles/g++.log.xz | Bin 2823360 -> 2808472 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2448528 -> 2449732 bytes sumfiles/gcc.sum | 4712 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 940544 -> 943676 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207172 -> 206928 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467304 -> 462144 bytes sumfiles/libstdc++.sum | 12 +- 35 files changed, 2529 insertions(+), 2589 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.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (9c97953735 -> 6f8aec15f6)

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 9c97953735 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits discards 6833140a1c 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits discards 066090eb7d 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits discards 9f1cb17147 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits discards ea1d8e8355 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits discards 82b7172afd 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits discards 965e02df6c 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits discards e4c3540d55 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits discards 93438e7bad 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits discards 8d85d03a36 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits discards c44768cdec 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits discards 5e9a31a81d 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits discards 8ac0ffd533 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits discards c7846fa4f1 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits discards 932c981788 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits discards e852041c87 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits discards 228d9a51fb 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits discards 26dde95ff8 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits discards e6aae9e004 441: onsuccess: #2403: 1: Success after gcc: 3 commits discards 27708403b2 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits discards 738ab34d5c 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits discards b864222e0f 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits discards 5b650bae83 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits discards 9b5972dd62 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits discards 3d7f98223c 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] discards c904bd09e5 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits discards 1ae9ed3845 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits discards 2b06fcc55d 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits discards 9c02df2923 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits discards 639c3dc33b 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] discards fd669eb86d 429: onsuccess: #2391: 1: Success after binutils: 3 commits discards b7198078dd 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits discards db7d7ebec8 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits discards b51a42a69f 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits discards 2527879669 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards 54fbe6c79a 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards f7a7f058aa 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards 843da825f3 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards d319ebe0a1 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards 089a27284f 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards b6ce9fc4ea 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards 8c95d90d8c 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards 25cff61ec2 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards be65b41df7 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 9d2645d92c 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards f6a42ebd2b 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards 37652e0c3a 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards 0b84e1f1a0 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards 0ae4213a52 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards b732e991bd 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards 0dd87700bf 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards f7b8e137b1 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] discards 949b06bf8d 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 22ca629626 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards d5a8aedf73 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] discards 888f79e4cc 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] discards 220fca0ddc 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards a95c113c69 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards 5569afbc5f 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] discards d9547fa7b6 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards e4d1048a93 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards e9bdd88299 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards 3fd7b893cc 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards 2412ef4e37 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards ef6477c047 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 9f92648085 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards 77d84f610f 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards d9f58c4a22 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards ff96161b61 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards 162bb32f0b 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards e54a922f97 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards 939d295632 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards b14f75831c 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards 623b221c10 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards e8ed59d1dd 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 98b4071337 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 7d48327c4d 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 8400a0a6a3 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards b93a9e12d4 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 140cd1628a 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 7967e8fec3 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] discards 4df5139e17 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards b5c90ef9d1 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 00f53f30db 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards f9ad2790bc 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards f3977a8d71 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 453da8187f 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards a70a8e5da2 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards ff81b5db26 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards ddbb031018 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 8d137347c0 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards bf8b12c7c0 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 553b6f48c2 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 46f344d657 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 7f8e76546b 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards af62d6422d 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards bd3911feeb 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards a90c16c92c 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 04ff19a8de 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards adf756af02 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards 297faa962a 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] new ce67cb8941 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] new 298b05cbd7 360: onsuccess: #2317: 1: Success after binutils: 4 commits new de3a6cad58 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 25cc26c264 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 83ebe627d8 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new c6c2aba13a 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 6e2f95abc8 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 6adcedf612 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 2e1cd757ba 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 8967462278 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new ffe7865e2b 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new e188df2b37 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new cc85be581f 371: onsuccess: #2333: 1: Success after binutils: 5 commits new f8d23607d7 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 05660fbf31 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new d364e17bad 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 6ef8a81411 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 93e9738180 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 13ea18fa90 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new bc21a839f3 378: onsuccess: #2340: 1: Success after binutils: 2 commits new b506c6be61 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] new 5519d76b53 380: onsuccess: #2342: 1: Success after gcc: 3 commits new fb2c1005e9 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 0d8a1d309e 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new e161632532 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new ccf00629de 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new d64d2ff493 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 6483b8b697 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new c813f4d83a 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new ffcd16b2d0 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 472d09b955 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new 1b70fa5810 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 9f2724c760 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 509089520b 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 38fa2faf5d 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new e456af54b7 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 1528409f5b 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new 32d5bf96ab 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new d06bb06759 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new 36b0890311 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new 009d1dbf1a 399: onsuccess: #2361: 1: Success after gcc: 10 commits new 40b66a0bd1 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new ebba43e541 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] new face377a61 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new b21e40a354 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 7014139077 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] new a1d056591a 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] new 58e2b31870 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new c5ea1043ae 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new d43a261b84 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] new c572f10e78 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new fa2aa788e8 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new aeed843fd7 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new 097ba3da5f 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new 2110de7c58 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new d3f3d5672e 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new ceaa59d90c 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new a1f52b62d7 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new 48fd10933b 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 202844d3bd 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new ccf889cf0d 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new ad044a29ab 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 20c94f76c8 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new 9320d5b3b0 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new 153c44c780 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new 3cad84c348 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new 570fe63c08 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new 427f4382c4 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits new 14fc7287cc 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits new f6da525b4b 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits new a8cf9feb08 429: onsuccess: #2391: 1: Success after binutils: 3 commits new a67667dcaa 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] new d46f27701f 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits new 91ec5a26bc 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits new 2fb2743d80 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits new 5723d99f11 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits new eb588dfbf2 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] new 7c7e169f6a 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits new 31ea0b7a6e 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits new 5523138bfc 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits new 254aff1880 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits new 848a5f726d 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits new 969e0e6286 441: onsuccess: #2403: 1: Success after gcc: 3 commits new 8e3987c65e 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits new 08074ec607 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits new eb0ef7d167 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits new c58bfec925 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits new a78cbd1860 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits new c76b870fff 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits new 212700668f 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits new ec6f782418 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits new ee206411cb 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits new a7425c02cf 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits new 32aab0eb89 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits new 8ab133cb75 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits new d5eed7145e 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits new f700b75270 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits new 8f345960dd 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits new 6aa2cf949c 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits new 6928e5eb5e 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits new d6d9cf3797 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits new 6f8aec15f6 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] 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 (9c97953735) \ 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 1788 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 39816 -> 40628 bytes 04-build_abe-gcc/console.log.xz | Bin 214812 -> 216912 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3868 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3312 -> 3232 bytes 07-check_regression/console.log.xz | Bin 5148 -> 4300 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 36 +- 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3642584 -> 3636028 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3163844 -> 3152036 bytes sumfiles/gcc.sum | 4624 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1054056 -> 1053628 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219804 -> 220092 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450032 -> 458996 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2473 insertions(+), 2564 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (2f9acb2f70 -> 4b4b381ae1)

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_debug in repository toolchain/ci/base-artifacts. from 2f9acb2f70 44: onsuccess: #167: 2: Success after binutils/gcc: 14 commits new 4b4b381ae1 45: onsuccess: #168: 2: Success after binutils/gcc: 7 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 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 53260 -> 51732 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 462104 -> 462348 bytes 06-check_regression/console.log.xz | Bin 2836 -> 2676 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (2eeb88938f -> 6309c15346)

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 2eeb88938f 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards f72bc9eb1a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 30bc7b84d5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards f4e6437742 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 8b60beb8fb 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards f3bce4460e 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards e6fc57e58a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 08919da6c4 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards ae2fb5a32f 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 8b19aad341 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards acb57a7234 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards dabe18e4f0 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards dbeb014f56 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 06b7edaad4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 3502fa7d24 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards a68b025f0a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards b650f0cff6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 6b2bbdd8a3 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards eaa825d194 125: onsuccess: #614: 1: Success after linux: 12 commits discards 9028a56659 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 1f24c0d766 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 43c43b1119 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 02209a60e2 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 0b3cb4aa2c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards d0d31a13c3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 3dc1fec06e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards a7e0863217 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards a6de659c46 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards d34ee6b171 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 124be2f86c 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 217f16700c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards b9e37fc8e6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards ef6846ae3c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 7ca0da4eb7 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 7090c7c310 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 48e7aa9c3e 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 4d7bdbdb69 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 50b7b8c329 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 3d12d101e8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 1fad9c6f13 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards e8d47ea9fe 103: onsuccess: #589: 1: Success after binutils: 3 commits discards b8204cc686 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 1a27f5c4f8 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards fe26c94663 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 0b3c922f40 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards e2d46917e9 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards d0e2c97f73 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 455e43720f 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 9cb45e1ca1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 9f8b9ffb77 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards d51768c61b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards cdefe266f8 92: onsuccess: #575: 1: Success after linux: 34 commits discards b60f13254a 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 49ba7c115c 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 4002c6518a 89: onsuccess: #570: 1: Success after linux: 11 commits discards 3e7d53b849 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 4500f7c8f6 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 1fcec8e630 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards e26ac9080d 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 801eb3106b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 3a2f4d4bd4 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 5b608a2269 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 6c0a3064ae 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards b0e33ff894 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 0b0df2dd12 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards aa5ad4e0fc 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 2ed87d6144 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 30d1178920 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 795e85ea32 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards f713b5371c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards fd50e5945b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards e0b2ac0e29 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 97d93301c0 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 10b8243b67 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 8c65556a85 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards bd8769c1f1 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards aeefdd53db 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 18b5d12166 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards df1598d38b 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 66f80319fa 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 0b216ebd84 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 9bebad5a91 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards fff1c1d000 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards a2c7c406e6 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 75bbc4e2a7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 22274ff25c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 785ee0779b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards f943b5c118 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 95d0f80520 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards fd08c8848b 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 1ab1769896 53: onsuccess: #531: 1: Success after binutils: 12 commits discards f4aba34dac 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 398f0f985a 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 5fbcfd4fe0 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 4424c3de72 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 952ab76a77 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards ebd9927c1d 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 9f3d5ebf9e 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards c06606bfb2 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards cdc23907c1 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 23b498248e 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new a3004e93e1 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 2554364d16 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 6e3273b244 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 8020792aec 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 56554dc129 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new c23833a3e7 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 3842e9a068 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 39928ce635 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 3a16d2681d 51: onsuccess: #525: 1: Success after binutils: 8 commits new d719546e8f 52: onsuccess: #528: 1: Success after binutils: 8 commits new af53a9d7a3 53: onsuccess: #531: 1: Success after binutils: 12 commits new 7e32255a0e 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new c066d2d02a 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new f1166ac0d8 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new c0b153fd69 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 9bfd8de677 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 1447905840 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 351eade097 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 5537a166cc 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new b8d28daa94 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new de09d0ea99 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 88c1bb20c9 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 6a3f612a5e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 187fa3b5ab 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new fb7ec5d4cd 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e2c4e698b2 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 82b4f80367 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new bec0487159 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 332a053ec1 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new febb329784 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new b697999d85 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 5424a87545 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 8ba9dead96 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 4b5010c452 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new b140b47f99 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new facd8352db 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new a01d76a4a0 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 5657f6c90e 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 2723e8d122 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 675db4c754 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new b9a92cb209 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 0812602c9f 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 1ffd11e679 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new a160906b5c 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new e530374f87 87: onsuccess: #567: 1: Success after binutils: 8 commits new d7ebeffdcd 88: onsuccess: #569: 1: Success after glibc: 10 commits new a3a8c3397f 89: onsuccess: #570: 1: Success after linux: 11 commits new 64655ce389 90: onsuccess: #572: 1: Success after binutils: 15 commits new 62b6759e35 91: onsuccess: #574: 1: Success after glibc: 3 commits new ef321682d1 92: onsuccess: #575: 1: Success after linux: 34 commits new 0ecf89753d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 72bc75718e 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 32415491a8 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 7620409ff6 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 090ac7d435 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 04f91d65c8 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new cfc8732cf9 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new f33e5f6f80 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 93c3252e30 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new a080c409d1 102: onsuccess: #586: 1: Success after binutils: 5 commits new 45c46ff160 103: onsuccess: #589: 1: Success after binutils: 3 commits new 2ce8b47a5e 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 6b79d69e83 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 6010df817d 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 21c8136641 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 637cb98267 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new a822bc5889 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new abc7abd408 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new d350831003 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new c861c415c9 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 6372b6d7b0 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new f1c826925a 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 13809909c3 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 13fb7723e6 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new bd2dafa792 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new cf1601dbdf 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 4f6c3388a4 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 5748b66965 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new b563c39a37 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 580624d3d9 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 05e627dbf1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new de141a9d46 124: onsuccess: #612: 1: Success after binutils: 18 commits new 1620aba73d 125: onsuccess: #614: 1: Success after linux: 12 commits new 19e4c97464 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 29341c380d 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new c4d99344db 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new de99bca1fb 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 2d59aefbaf 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 40524ea6cb 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 0de2b76873 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 4f777bad4d 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new ff98371e94 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 96e6f0a4d0 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new d7dbcd4aca 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new f230fcd865 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 7a1c72cc1c 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 4ea6745cad 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 4ca3137465 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 5e0c3ec74c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 811b460680 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new a5deb4835b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 6309c15346 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 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 (2eeb88938f) \ 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 1916 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 53708 -> 54468 bytes 04-build_abe-gcc/console.log.xz | Bin 237980 -> 240740 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 238580 -> 236900 bytes 08-build_abe-gdb/console.log.xz | Bin 53128 -> 52232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3912 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2644 -> 2184 bytes 11-check_regression/console.log.xz | Bin 17400 -> 10336 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 47 +- 11-check_regression/mail-body.txt | 221 +- 11-check_regression/results.compare | 131 +- 11-check_regression/results.compare2 | 4999 +++++------------------- 11-check_regression/results.regressions | 107 +- 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 223 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 107 +- sumfiles/gdb.log.xz | Bin 1719388 -> 1804268 bytes sumfiles/gdb.sum | 6319 ++++++++++++++----------------- 29 files changed, 4359 insertions(+), 7875 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (edda128da79 -> 2a005e97c91)

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 edda128da79 sim: mips: move distclean settings to common build new 2a005e97c91 sim: build: drop support for subdir distclean 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: sim/common/Make-common.in | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (d583171bf0 -> 7f748c9f8b)

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 d583171bf0 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards d7208fa6cc 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards eceb875977 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 95614f01ca 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 380f097567 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 3473e7cde3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 637d54cd75 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards dfd6952ac7 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 64864aa58a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards ff1f9439a2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards d8ef9304cc 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 65e78c47d4 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 9f41588da7 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 23110c21e9 127: onsuccess: #874: 1: Success after linux: 219 commits discards 6f6fa88aef 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 0726ae72c7 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 3bcf43a7e1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 8fa96dd6c9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards fc4fe55526 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 17908fe61e 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards bca4f80a8a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards d8fdb11c86 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 3b8a2945cd 118: onsuccess: #863: 1: Success after linux: 12 commits discards cecdcf176a 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 7deaf8b27c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 2e37fbb08d 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 01ad012a4f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 90ed957369 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 91bba390b4 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards a574d64e71 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards c43f9a5017 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 67a802747a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 222ae16508 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9a896eb39a 107: onsuccess: #849: 1: Success after binutils: 5 commits discards ddebd86d7a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards abcf80fcba 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards e1a697de08 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 5c10cf84ac 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards a2d082c34e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 6cc4969af9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 96b4eccb1c 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards b9ff9c5b6e 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards eda0c4cbdb 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards c0fca66d29 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards fa4022eb2a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards a3dbc844a4 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a9aef33567 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b17d6fbd77 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 2cb6b2b3a1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 2c567dfa38 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 1e27eb0688 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards bc5c4da971 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9f4453743b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards a39f3763e6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 09d1bd2225 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 95989465bf 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 3d28bb2255 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 40e164fda3 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards be4c2db1cb 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 0989032c44 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0fd0804faa 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 40e3522b71 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 4f9035e15a 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards efa9300c80 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards c5fe134702 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 2dcf48a339 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 6c48e820fa 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards a00d57ba2c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards ddf79d64f5 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards e1ff83fa48 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards b0c400db57 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 1a2cdd942a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 7fd01309ea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 2cac81074d 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 6c9eac002d 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 818f04f770 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 08f92db4cb 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 339dfffa5b 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards c1646efa25 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 3ea6fb6b69 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 1ce2e5f872 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 6f1c6f6fad 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 28f3cb22db 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 719c1e34db 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 3338ebaa98 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 9a053dbefd 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 512c4dd924 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards ff6a8d82ac 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 54eee30f9a 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards a3a528eab2 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 30625937ec 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 036d925d4e 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 4b1f765011 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 3e2668d4ea 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 99e26d7e5f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 9fb2639757 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards b1a906b404 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 543b67a641 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 02ed8f3154 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 704f56df23 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 51aed3b256 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 13831dd73a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 86b6a8ddab 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 10c737049b 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new aa49f8711b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 3a8c427118 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 5dcdd28cd1 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 348f7cfc6e 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new c7aa23f6c8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 0025c26a17 48: onsuccess: #782: 1: Success after binutils: 8 commits new 5fd60c4dc7 49: onsuccess: #785: 1: Success after binutils: 12 commits new bed22023a5 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new fd1fe5e6a8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 73059d7073 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 1b3e34b0c2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new fde951f267 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new f5bf51178a 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new b320c43e38 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 15334b5ae9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new dc926458e0 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new afb67b375b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 811b047418 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 1d1a0ce0a7 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new c7af2bdcd1 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 7ebd579502 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 73c2973c63 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 6c41724080 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 99222aa8df 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new bb08907010 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 8fec567f01 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new aa9e5c28b6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new bf40473b79 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new d9454f990b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new e6ccf067bb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 17d5c057db 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 9540134751 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new fc8d5ac74d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 316220ca02 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new bf3e434219 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new c74ec7a797 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 3704759ed3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 0f43ab70ad 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 93be9a5a5c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new e9dee4ddd4 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 057966f958 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new f46a8b716f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new dc55ed843b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 45e244fc36 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new bbb7e51926 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9403844414 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new bfdcef1712 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 526f518485 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new e2f2bd34df 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 84351e89ed 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new f37ecde2cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 08e5689093 94: onsuccess: #832: 1: Success after binutils: 5 commits new 21880ad077 95: onsuccess: #835: 1: Success after binutils: 3 commits new 599f5dc6fd 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new f7661a4f97 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 32140ef6bd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 80ae81bbbc 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 40171fdc3e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new f034a45e9a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 0e710a808f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 49ace43587 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new a17b81562c 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 89886fb464 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 826df00a12 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 2038b63924 107: onsuccess: #849: 1: Success after binutils: 5 commits new d381e456d5 108: onsuccess: #850: 1: Success after gcc: 2 commits new 292c4a82ea 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 53114692b6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 37e1efa0fe 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2f922b6ba5 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 6106d74fd3 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new f1e214cfa6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new f727e73f96 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 157f1d05d9 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 292c5dac64 117: onsuccess: #861: 1: Success after binutils: 18 commits new 071bb0b231 118: onsuccess: #863: 1: Success after linux: 12 commits new 11c097cdc8 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 3654d4ce54 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 812352d978 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 9c9a4b241a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 58f22242cd 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 6274e50acf 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 1e20f9f9ff 125: onsuccess: #871: 1: Success after binutils: 26 commits new fc202f5fc4 126: onsuccess: #873: 1: Success after glibc: 2 commits new ec988a8eac 127: onsuccess: #874: 1: Success after linux: 219 commits new 9242a5cd89 128: onsuccess: #876: 1: Success after binutils: 12 commits new f3905ed345 129: onsuccess: #878: 1: Success after linux: 3008 commits new 3f5b507fee 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new b56e2f1d68 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 30bdccf7af 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 7347b8cac3 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 58dfb77eae 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 0cf820ff57 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new fc343278f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 6eac8def15 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 874e8d2992 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 725492654e 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 5e98107d42 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 7f748c9f8b 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 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 (d583171bf0) \ 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 1744 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40596 -> 39856 bytes 04-build_abe-gcc/console.log.xz | Bin 215364 -> 216820 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8540 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 245448 -> 245548 bytes 08-build_abe-gdb/console.log.xz | Bin 39580 -> 39748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2460 -> 3284 bytes 11-check_regression/console.log.xz | Bin 6964 -> 6800 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 6 +- 11-check_regression/mail-body.txt | 58 +- 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 65 +- 11-check_regression/results.regressions | 31 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 31 +- sumfiles/g++.log.xz | Bin 3752572 -> 3775616 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3302488 -> 3310296 bytes sumfiles/gcc.sum | 4692 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1072908 -> 1080828 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232176 -> 232248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452460 -> 462656 bytes sumfiles/libstdc++.sum | 12 +- 41 files changed, 2705 insertions(+), 2583 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-defconfig updated (32a8d17f37 -> 9430c6f985)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from 32a8d17f37 32: onsuccess: #434: boot: Success after binutils/gcc/linux/ [...] new 9430c6f985 33: onsuccess: #435: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30336 -> 30012 bytes 04-build_abe-stage1/console.log.xz | Bin 87468 -> 86388 bytes 05-build_abe-qemu/console.log.xz | Bin 31276 -> 31572 bytes 06-build_linux/console.log.xz | Bin 3368 -> 3348 bytes 07-boot_linux/console.log.xz | Bin 5828 -> 5788 bytes 08-check_regression/console.log.xz | Bin 4212 -> 3936 bytes 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (3bd319d4a6 -> 4a4107bf3e)

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-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 3bd319d4a6 45: force: #529: all: Success after llvm: 484 commits new 4a4107bf3e 46: force: #530: 20163: Failure after working-8684-g114cc45a [...] 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32300 -> 32384 bytes 04-build_kernel_llvm/console.log.xz | Bin 66156 -> 63940 bytes 05-build_abe-qemu/console.log.xz | Bin 31752 -> 31644 bytes 06-build_linux/console.log.xz | Bin 3424 -> 7080 bytes 07-boot_linux/console.log.xz | Bin 576 -> 0 bytes 08-check_regression/console.log.xz | Bin 2844 -> 3672 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 17 +++- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 +++ 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 158 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +++- mail/mail-subject.txt | 2 +- manifest.sh | 12 +-- results | 15 ++- 26 files changed, 230 insertions(+), 23 deletions(-) delete mode 100644 07-boot_linux/console.log.xz create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/interesting-commits] branch master updated (d94275cd -> c2c9f766)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from d94275cd Add entry be2c74fdcd0e8d66c3667008ba2561ab5dcc379b from https [...] new c2c9f766 Add entry 114cc45a095eaeed1efe62a47cd298bd7cad85de from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../114cc45a095eaeed1efe62a47cd298bd7cad85de/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy llvm/sha1/114cc45a095eaeed1efe62a47cd298bd7cad85de/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/114cc45a095eaeed1efe62a47cd298bd7cad85de/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/114cc45a095eaeed1efe62a47cd298bd7cad85de/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022