Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (f86174b947 -> 8175cae73f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards f86174b947 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 1fa8494d9a 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards a6271b10a4 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 7f6cd12b8f 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards d4487b3b4a 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 34efb04cb2 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 4180b2911f 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 8021eba39c 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards ab087f4c9a 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 258f1f4764 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 4a15efc076 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 807fb57e46 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards c6f6384196 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 7cd2cde905 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 94b95073d8 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 116491e3c9 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards e7b94f19a6 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 1bc58f0848 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards d45f622784 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards a89f45e646 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 5c65a7e8a8 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 3ae8c73804 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 79719580a8 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards c78996709d 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 50495de905 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards 5b0ae4d9cf 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 6b7450dae5 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards 7dd1be7ede 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards cc706a7fd1 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 922aec885f 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards 4d684df606 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 4511bf8155 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ac2efc71ae 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 0444cf39ae 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 89406fc3c1 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 0dda6b235b 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 83ce9e4133 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 2217aeefc8 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards e6a8809c3b 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 514b8daa90 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 750e30097f 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 5d5d77d941 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 5aea8aa0bd 427: onsuccess: #7: 1: Success after linux: 26 commits discards c02b6efdea 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 30a14de766 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 7ef80a8cc0 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards bec4065eb8 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards ef3f1d9381 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards a474bdac34 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards d68e585f30 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 00d68878aa 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 48f50ef796 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 0ffd19abc7 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards ab70108d01 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards e10f3aa698 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 96783d35cf 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 86e5684859 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards c56f2cbe57 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 6a61fa8312 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards fa2d3aaddb 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards b869a927e7 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 626528d806 408: onsuccess: #2662: 1: Success after linux: 11 commits discards b3f299f083 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards ee6e98d9cf 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 504a2c3507 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 6f220d3ede 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards a8f8fcabc3 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 461ffc6508 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 5ac27a40a1 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 9983a11be2 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards bda7e1472c 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 38c9c7236d 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 4e75abc170 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards b4f73bb832 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 03b97c629d 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 2917878bc3 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards b6af097557 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 64c331dfcb 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 8cf713bbe0 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards da36899e03 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 97c1a4c8e9 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 1e5bc96af6 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 97095b81f0 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 5aa50b3043 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 16deb1af80 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 4140a7999a 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards b98e828d60 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 42c65a92f9 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 002491283d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards dc0426ce75 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards ede4dc572c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 57f215f130 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 7dc9aa5a99 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 2cd7bec0dc 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards ccca44c1f1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards f42c4bd330 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards a4ce4869fd 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 598ebbdde7 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards fb62ca73ab 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 3310872b39 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 3a30f2c1fd 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 83309e5b36 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 5332b3c922 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 6c97988770 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new b61ff886e6 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 83976ff914 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 08db9cb5b5 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 02c07a5aa3 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 4c6a40d651 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new ed1c5a68e3 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new da8709c9fd 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 14ae96e9d2 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 8aafa6acae 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 5c2e93d80f 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 6c95bab91f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 43235d63bd 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new c5fba540f9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 81b450262a 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new cc2406537d 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 8b9444badd 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 6a2716e7c2 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new b8f8a17e3f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 9d9c7e35e0 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 670a3d9bbd 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new ba10d7c51c 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new d74282d0dd 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 831bcac917 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new d5a146ecd0 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 49602cff38 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new cd46073c98 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 24191c1f8c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new c4d54a4342 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 6fe3a6f3dc 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 83c47133fc 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new d95d2b279d 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 60e360f915 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new f355e40f65 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 192b45a872 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new b319c292c4 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new cb7a349b62 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 546b6eb626 408: onsuccess: #2662: 1: Success after linux: 11 commits new 97866968e9 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 8aa5a372bf 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 72bef5aecc 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new ba8391ac90 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 304eb5ec12 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 19bcc50fee 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 1400d6016c 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new e38b129879 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new c1e43393aa 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 9607c86bcf 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new a5e93fbd7d 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 2db6e5a9e2 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 898360825a 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 0a129094da 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new be9b368c89 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3a2042e98e 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 8de2598b39 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 867f4280c5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 5ff409998e 427: onsuccess: #7: 1: Success after linux: 26 commits new a21dacc34a 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 43daef6f2c 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 4138ea225d 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new e1e119e608 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 184e996be5 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new a8cd6339c2 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 102b3a7792 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 2fcfe30e0f 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new cdaf1b83e7 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new ef97410ddb 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new da8a4036b4 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 75d93c0a00 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new dc690898c4 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 532e603653 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new ee6d530345 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 07a30fa3b7 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new dd54381372 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new 74b5ff5edc 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new ec6d872328 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 01f24dff21 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new f29a06758e 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 5efd29b205 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3deb10553c 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 9d67256278 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 64a5c0f15a 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 050ed5f4fd 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new a575e312c2 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 6de0a19dd0 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new a7549a0c8d 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new d4b314143a 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 39163ad349 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 311140114e 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 8a80b47b1e 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new e774c04a21 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new b7eb97e8e7 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new b52a413ab2 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 2d6532285d 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 660149da13 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 91774155b2 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new e6c2030fbb 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 574f6a5b19 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 1e700fcdec 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 8175cae73f 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] 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 (f86174b947) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2088 -> 2136 bytes 02-prepare_abe/console.log.xz | Bin 2556 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 27212 -> 27640 bytes 04-build_abe-stage1/console.log.xz | Bin 71056 -> 71208 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8288 -> 8272 bytes 07-build_abe-glibc/console.log.xz | Bin 241800 -> 240784 bytes 08-build_abe-stage2/console.log.xz | Bin 202112 -> 201460 bytes 09-build_abe-gdb/console.log.xz | Bin 34748 -> 35056 bytes 10-build_abe-qemu/console.log.xz | Bin 31240 -> 32368 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6544 -> 6060 bytes 13-check_regression/console.log.xz | Bin 5228 -> 5836 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 38 + 13-check_regression/results.compare | 63 +- 13-check_regression/results.compare2 | 61 +- 13-check_regression/results.regressions | 58 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 36 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 42 +- manifest.sh | 44 +- results | 58 + sumfiles/g++.log.sep.xz | Bin 184544 -> 140756 bytes sumfiles/g++.log.xz | Bin 3407000 -> 3410296 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 18483 ++++-------------------------- sumfiles/gcc.log.sep.xz | Bin 156600 -> 166436 bytes sumfiles/gcc.log.xz | Bin 3031820 -> 3031512 bytes sumfiles/gcc.sum | 62 +- sumfiles/gcc.sum.sep | 15014 ++++++++++++++++++++---- sumfiles/gfortran.log.sep.xz | Bin 61456 -> 77568 bytes sumfiles/gfortran.log.xz | Bin 1045004 -> 1041408 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 7479 +++++++----- sumfiles/libatomic.log.xz | Bin 2312 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217280 -> 217596 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2680 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 16372 -> 57320 bytes sumfiles/libstdc++.log.xz | Bin 436356 -> 424272 bytes sumfiles/libstdc++.sum.sep | 867 +- 51 files changed, 20584 insertions(+), 21826 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (1245520270 -> f189dd2ab5)

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. discards 1245520270 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards fcb30fef79 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 87857b970b 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards bedeff33ff 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards f2c92f2cdc 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 83943cd771 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards ce0630fe05 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3c29c80ef5 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 6ad8870916 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 61f4c7ebd7 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 280a3073c7 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards fc9c195549 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards bd66919db1 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 18f3ef58b1 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 1b84f9165d 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards efd0d89eb6 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards abdf1c725e 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards c3d47369e5 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 9a5165c516 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards b5a0964311 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards ef02e5bf45 127: force: #27: : Failure after baseline build: no new commits discards 2e860750e0 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 95653fb8fc 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 51973fa128 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 95f2c477a9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards cd8c1ee39d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 924ced55ef 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards aa088dca85 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards def059a9b8 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 8bbbb6385c 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 4b507043bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 13b92b3888 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 9822692796 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards fe10f3e9ff 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards c8a4d4dd04 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards d42a0f4397 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 653dea9417 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 7b7c4ba465 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 772bcf7270 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards caae57f7d2 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 2915881155 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 780832a5aa 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards d34e48e649 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 3996a2afea 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 70928215fc 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 3df332c325 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 3ecb29b49f 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 74214a0c54 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 33d012efe6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 97cbd48961 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 3461166fbb 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 7d4707254f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards dc9bfbeb5e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 73cee8d33c 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 7a9f8a5323 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 54870bbdcd 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards a31c1a357a 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 577e7e63b5 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 7b0a84abf4 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards f18ede61fe 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 7e2ae585b4 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 844de0884c 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 6a831dacf1 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards f0a7997861 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards eb55c8c77d 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards c8cb82ca42 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards d07755eff2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 3bdc3788be 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 9cd3f9e8cc 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 343915106a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards d4f8db3922 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards c136aeb180 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards b918bd0965 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards b2986057a8 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards c9180bcf7d 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c449a3d21e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 6f25e6cb88 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards d1c200ad80 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 950b7c676c 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 093eb58153 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 43e19e7736 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 75a26096ee 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 32d8cd1373 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards f73899f782 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards dcdeee1157 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 8fb426b66d 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 4de88b9405 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 64358b3321 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 4913567191 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 578ae7dc87 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 54539a588e 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 7a0966c5ad 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards eb3a8a6007 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 998f2e676d 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards fcebfd7f60 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 74cbd3e542 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 055c874da5 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 089fb2080c 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards afb8952a7c 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards efc52cebce 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards b58dfa6f6d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 70ffd9bc06 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new e22096ac6d 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new 9f6fda03f0 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 333e9b6f17 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new a3fbebdfaa 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 2b72ab2beb 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new f07012b2fc 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 4ec24b39c1 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 07125efab7 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 172fa346a5 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 6bb362f735 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new f7eecce4bb 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 4cda5e7d35 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new ce84f0944f 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 3e44c77af3 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new a92497c074 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new e970c7242c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new f79667cea7 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 454b27442c 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 83ba7f8321 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 5d21e317c5 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 26eefba65d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 0ffa291223 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new bc2c610571 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 519528bb62 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 95157481ce 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 0472fb08b0 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new e931db4cf4 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new d8db24ed67 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 16d8111eff 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new d35f6d5f88 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 7179da6451 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 5759868714 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 834c8a77a3 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 3711b983e6 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 1c6d9d0128 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 8d8d95ca89 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 7532d92742 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 093217c428 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new e937fd1188 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new c198e64ffd 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new d23ee2c591 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 749b29a3e7 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new c922211a5b 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new eabbadd8d4 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 2ccd2f1eea 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new f6ecc0ce3f 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 9310a28e39 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new b8e6d38d8a 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 6998afa600 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new d0141e8d37 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 93058e4139 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 6c3f2d2ef6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 6c0ed6dc02 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new d94ac9a9d1 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new b97f321b9e 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 87f7e3688d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 406803939a 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 5d020813ca 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 8b225743dd 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new b39cb2c1c8 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new f3e5c56a19 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 033ac18e64 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new c08ac0ac0e 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 18584e0e27 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 6ea94dd9cf 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 339fe69339 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 4abd2beff5 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 74e55eb5aa 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new d2bf5e598b 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 0893067025 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 49198cabd8 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 4172b1045b 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 0736d5ab80 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new f669a469c2 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 4c2896139e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 4ba2278449 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 00e63683f8 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new deba6ab55a 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new e9749c1b06 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new f5aabeec1f 127: force: #27: : Failure after baseline build: no new commits new 693ab75ea2 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 63297f72b5 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new e388dac84f 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 94661b0fbd 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 445194cc60 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new e4ca585277 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 53f649db5e 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new ac0869dde5 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new d1dbd89ec2 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new c246c5bece 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 947300ed46 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8f1300fe4e 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new c97f902627 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new cf52a1cb00 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new d77a57722c 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 707b2d259d 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 0674a2b68c 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new f1a7602c88 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 73b5387cfc 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new c56085dadc 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new f189dd2ab5 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] 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 (1245520270) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 2088 -> 2084 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 35084 -> 35152 bytes 04-build_abe-gcc/console.log.xz | Bin 203964 -> 203376 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 241756 -> 241024 bytes 08-build_abe-gdb/console.log.xz | Bin 34836 -> 35024 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2800 -> 3136 bytes 11-check_regression/console.log.xz | Bin 4168 -> 4808 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 +++++++++++++++++----------------- 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/changes-list-long.txt | 34 ++++++++++++++++++--------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++++------------- manifest.sh | 38 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14440 -> 14440 bytes sumfiles/gdb.sum | 4 ++-- 26 files changed, 93 insertions(+), 81 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[glibc] branch master updated (747812349d -> cd019ddd89)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from 747812349d hurd: Improve reply port handling when exiting signal handlers new cd019ddd89 hurd: Don't leak __hurd_reply_port0 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: sysdeps/mach/hurd/i386/tls.h | 5 +++++ sysdeps/mach/hurd/x86_64/tls.h | 9 ++++++++- 2 files changed, 13 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (0fed20147b -> b3d4aa4800)

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/master-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. discards 0fed20147b 236: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] discards 7a0dc21d7b 235: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards e1dbf2709b 234: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards a825249825 233: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards b257313cca 232: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 14afa715a3 231: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards 8d24db3a2e 230: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] discards daebc75937 229: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] discards 86685a8a41 228: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] discards 62385b1b07 227: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] discards 04bdba2733 226: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] discards 4b50f33c0b 225: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] discards 689360be66 224: onsuccess: #35: 2: Success after binutils/gcc: 7 commits discards 9d6b6cef40 223: onsuccess: #34: 2: Success after binutils/gcc: 7 commits discards 3767dd6a33 222: onsuccess: #33: 2: Success after binutils/gcc: 32 commits discards f416174661 221: onsuccess: #32: 2: Success after binutils/gcc: 32 commits discards a74c108856 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits discards 1d245bf1b7 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits discards 2530574b2e 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits discards b1ad20de6a 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits discards 3cc19d764f 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits discards 828870a248 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards f4c2f8fdb6 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits discards 472dba812f 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits discards 00b0d26d4a 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits discards 3d053fb4ec 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits discards d8e121e7f6 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits discards 74d8881eb8 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits discards 3d2fe7fde3 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits discards 6b96b8591e 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits discards 60171be501 206: onsuccess: #16: 0: Success after binutils: 17 commits discards 30a5d5c8f3 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] discards f6da67ac0f 204: force: #14: 2: Success after binutils: 17 commits discards 141b7927b9 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits discards 2db86727a6 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 407dc0924c 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits discards e325580f45 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits discards 7c4a573a64 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits discards 40bd8db35e 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits discards 2e1f5922a7 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits discards ec2ccbe841 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits discards 987c0387b0 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits discards 4bf1292f15 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits discards e53af04077 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits discards 5e16938d57 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits discards 5996e0c456 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits discards 7f0f5e88f7 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits discards 8b4affe76e 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits discards 83427aae0e 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits discards c86ea65757 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits discards e5b9527193 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits discards c8ea6a0e04 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits discards af591431e9 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits discards 8738e775f2 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits discards 06f0e3dc85 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits discards 55f6d067dd 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits discards 2ba9ba57e3 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits discards 9b38e2a5e5 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits discards 922656c93a 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits discards 6f79f8b205 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits discards 380ad92e46 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits discards 5fd52a3245 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits discards c4f6100f25 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits discards a74d2de15f 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits discards d09f121bd2 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits discards b9da2874bf 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits discards 32656d9e0a 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits discards b3170f6e47 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits discards bda7cb0a97 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits discards 471f2fd790 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits discards d84af8a7fd 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits discards 7e2cf83f0b 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits discards bd3a7f5e97 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits discards c87e0b679f 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits discards 0c738b9778 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits discards 66c73dc07a 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits discards 4b9d941e70 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits discards 3e6d525262 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits discards 2dd0b4721b 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits discards c66d153dbd 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits discards 94a1b2e20c 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits discards a634ca9321 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards ac44badc0b 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits discards ef972d4a86 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits discards 3a23a3f5a9 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits discards deaf634f33 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits discards 4aa8d42047 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits discards e53624b2ea 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits discards 955cee4b12 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits discards 6023efb0aa 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits discards a53c5831b9 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits discards 7608c20564 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards e86cefe31d 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits discards b49a7ac3f8 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits discards 6c5f2a932b 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits discards f765bf3d09 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 3dafa910b4 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits discards 9524c055c1 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits discards 93d3e7e07e 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits discards 3407ca0e7e 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits discards 0579774307 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits new 77781f31e6 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits new 8c4e28f559 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits new f003fb55b0 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits new 9f53110724 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits new cee894c8eb 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits new 035b4af370 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 0e0ac618fc 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new 6b350a03f0 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits new cc9f49d239 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits new 6feee1efe0 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new 455dd03e83 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits new c44738f9a8 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits new bbcbcf762a 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits new 38e9b755b2 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits new 85aa6474ef 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits new 4619f577e4 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits new 8e10028068 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits new e96cd6370b 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits new 08331dc2b3 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits new 963e1e803c 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 85a198352f 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits new a2a1262ede 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits new 76c8966442 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits new d1a1e4e922 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits new 797b20cb7e 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits new 7a97d5bb6e 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits new 6a172b1e41 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits new 1653f7eaf8 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits new a0cf197eb3 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits new 3c79c9682d 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits new 08b1cedaee 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits new 6c80743b2b 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits new 0052aaed01 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits new e2b2820641 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits new 05c42b7811 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits new f382e1bbe7 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits new c1ae173387 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits new 28c858c780 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits new 7449cff970 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits new 7a92e046bc 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits new 5f1ecda800 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits new d2bf16e133 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits new dc90917b00 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits new 69ba8faaea 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits new 8314be3cf0 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits new 8c8595dbc1 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits new 5877648222 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits new e9f368f234 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits new 731db51c1c 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits new 3c24fc6f0e 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits new 37f4763776 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits new 6b59aa2e1a 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits new 1ab4d52408 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits new cd55f3d5d7 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits new 11b37d9857 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits new 2bb9c80576 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits new 1c1ee46f33 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits new 0b9010d8a3 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits new 691ab92cdf 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits new c46f6d27a2 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits new dd43c23b8b 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits new 8be60cf0e9 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits new 1b1ed81612 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits new 7f1ca5d840 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits new 094b161613 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits new 4402f07c69 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits new 1c9aee11b0 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new 5cc3f46d7e 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits new 2efd28ddf5 204: force: #14: 2: Success after binutils: 17 commits new 200461e560 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] new 996c034d7b 206: onsuccess: #16: 0: Success after binutils: 17 commits new cd3624ac38 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits new 010b1153ba 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits new be86a98ed7 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits new 871b685f15 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits new b7eb9eef3f 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits new 2ad17f4a37 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits new 6c2158210e 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits new ae18f83bcb 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits new 72634cd885 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new 12ae52f72e 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits new 35f5058699 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits new 56c39ba4c5 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits new 4ab3a30c25 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits new 34afdee1d7 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits new e2b114a4b6 221: onsuccess: #32: 2: Success after binutils/gcc: 32 commits new 53c147c0cc 222: onsuccess: #33: 2: Success after binutils/gcc: 32 commits new 08954a5e05 223: onsuccess: #34: 2: Success after binutils/gcc: 7 commits new 299776c343 224: onsuccess: #35: 2: Success after binutils/gcc: 7 commits new 12f8948434 225: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] new 378e839349 226: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] new 8fbdb4b051 227: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] new d558343044 228: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] new 987e5656f4 229: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] new 56c2a7c629 230: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] new d7dec7484b 231: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new f2511c52d4 232: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new 24ef42b02e 233: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new e128b2c5f7 234: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new 5360923fbd 235: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new 77ae3cfce5 236: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] new b3d4aa4800 237: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] 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 (0fed20147b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1912 -> 1912 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2500 bytes 04-build_abe-binutils/console.log.xz | Bin 48888 -> 49544 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 468004 -> 467124 bytes 06-check_regression/console.log.xz | Bin 2492 -> 2704 bytes 07-update_baseline/console.log | 44 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 10 ++++--- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 ++++++------- manifest.sh | 20 +++++++------- 13 files changed, 52 insertions(+), 48 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[glibc] branch master updated (b37899d34d -> 747812349d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from b37899d34d hurd: Only check for TLS initialization inside rtld or in st [...] new 747812349d hurd: Improve reply port handling when exiting signal handlers 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: hurd/sigunwind.c | 24 +++++++++++------------- sysdeps/mach/hurd/i386/sigreturn.c | 21 +++++---------------- 2 files changed, 16 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[glibc] branch master updated (4644fb9c4c -> b37899d34d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from 4644fb9c4c elf: Stop including tls.h in ldsodefs.h new b37899d34d hurd: Only check for TLS initialization inside rtld or in st [...] 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: sysdeps/mach/hurd/Makefile | 4 ++ .../mach/hurd/i386/dl-tls-initialized.c | 8 ++-- sysdeps/mach/hurd/i386/tls.h | 43 +++++++++++++--------- sysdeps/mach/hurd/x86/init-first.c | 11 +----- .../mach/hurd/x86_64/dl-tls-initialized.c | 10 ++--- sysdeps/mach/hurd/x86_64/tls.h | 19 ++++++---- 6 files changed, 51 insertions(+), 44 deletions(-) copy locale/lc-time.c => sysdeps/mach/hurd/i386/dl-tls-initialized.c (88%) copy locale/lc-collate.c => sysdeps/mach/hurd/x86_64/dl-tls-initialized.c (84%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[linux] branch master updated (09a9639e56c0 -> 0d3eb744aed4)

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 09a9639e56c0 Linux 6.3-rc6 new a3046a618a28 um: Only disable SSE on clang to work around old GCC bugs new 411eb0141085 Merge tag 'uml-for-linus-6.3-rc7' of git://git.kernel.org/ [...] new 707823e7f22f 9P FS: Fix wild-memory-access write in v9fs_get_acl new ea4f1009408e 9p/xen : Fix use after free bug in xen_9pfs_front_remove d [...] new 347dca97f75d Update email address and mailing list for v9fs new c118b59e71d2 Merge tag '9p-6.3-fixes-rc7' of git://git.kernel.org/pub/s [...] new f1ba4e674feb virtio-blk: fix to match virtio spec new 10805eb5d6d1 virtio-blk: fix ZBD probe in kernels without ZBD support new e508efc3ae7e vhost-scsi: Fix vhost_scsi struct use after free new 4c363c81f66c vhost-scsi: Fix crash during LUN unmapping new 9513c55ce3e8 tools/virtio: fix typo in README instructions new f0417e72add5 vdpa/mlx5: Add and remove debugfs in setup/teardown driver new 9da667e50c7e vdpa_sim_net: complete the initialization before register [...] new dfc191544864 Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linu [...] new 5da7cb193db3 rcu/kvfree: Avoid freeing new kfree_rcu() memory after old [...] new 0d3eb744aed4 Merge tag 'urgent-rcu.2023.04.07a' of git://git.kernel.org [...] The 16 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: MAINTAINERS | 6 +- arch/x86/Makefile.um | 5 + drivers/block/virtio_blk.c | 269 ++++++++++++++++++++++------------- drivers/vdpa/mlx5/net/mlx5_vnet.c | 8 +- drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 13 +- drivers/vhost/scsi.c | 39 +---- fs/9p/xattr.c | 8 +- include/uapi/linux/virtio_blk.h | 18 +-- kernel/rcu/tree.c | 27 ++-- net/9p/trans_xen.c | 4 + tools/virtio/virtio-trace/README | 2 +- 11 files changed, 241 insertions(+), 158 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[glibc] branch master updated (645da826bb -> 4644fb9c4c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from 645da826bb hurd: Do not declare local variables volatile new 60f9bf9746 hurd: Port trampoline.c to x86_64 new 4644fb9c4c elf: Stop including tls.h in ldsodefs.h The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/generic/ldsodefs.h | 1 - sysdeps/mach/hurd/{i386 => x86}/trampoline.c | 158 +++++++++++++++++++++++++-- 2 files changed, 151 insertions(+), 8 deletions(-) rename sysdeps/mach/hurd/{i386 => x86}/trampoline.c (68%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (398ef63b92 -> 4d06e2690d)

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-next-defconfig in repository toolchain/ci/base-artifacts. from 398ef63b92 64: onsuccess: #9: boot: [TCWG CI] Success after binutils/ll [...] new 4d06e2690d 65: onsuccess: #11: boot: [TCWG CI] Success after binutils/l [...] 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 2004 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 27292 -> 27448 bytes 04-build_kernel_llvm/console.log.xz | Bin 66124 -> 65052 bytes 05-build_abe-qemu/console.log.xz | Bin 32660 -> 31568 bytes 06-build_linux/console.log.xz | Bin 3028 -> 3432 bytes 07-boot_linux/console.log.xz | Bin 6136 -> 6172 bytes 08-check_regression/console.log.xz | Bin 4328 -> 4228 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++------------ manifest.sh | 32 +++++++++++------------ results | 2 +- 18 files changed, 63 insertions(+), 63 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm updated (819c0d73b5 -> b5ec0b081a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm in repository toolchain/ci/base-artifacts. from 819c0d73b5 14: onsuccess: #17: 1: [TCWG CI] Success after binutils/gcc/ [...] new b5ec0b081a 15: onsuccess: #18: 1: [TCWG CI] Success after binutils/gcc/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2064 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 26896 -> 27264 bytes 04-build_abe-stage1/console.log.xz | Bin 88972 -> 89760 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8276 -> 8284 bytes 07-build_abe-glibc/console.log.xz | Bin 233044 -> 233404 bytes 08-build_abe-stage2/console.log.xz | Bin 224968 -> 225740 bytes 09-build_abe-gdb/console.log.xz | Bin 34384 -> 34968 bytes 10-build_abe-qemu/console.log.xz | Bin 30748 -> 31916 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3860 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2152 -> 2500 bytes 13-check_regression/console.log.xz | Bin 4776 -> 5088 bytes 13-check_regression/results.compare | 8 +++--- 13-check_regression/results.compare2 | 6 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 36 +++++++++++++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 42 +++++++++++++-------------- manifest.sh | 44 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 62084 -> 61504 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 101012 -> 101032 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 114132 -> 114140 bytes sumfiles/ld.sum | 4 +-- 31 files changed, 83 insertions(+), 77 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023