Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (51dca1d6a2f -> d96e4e93008)

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 51dca1d6a2f 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 924b50fa021 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 401849ad759 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards efd055b72f7 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a406057b133 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 9308b95cfdc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 41fef8875e4 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards ffd19ef9594 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards fb2eea88d45 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 08097fa9417 125: onsuccess: #614: 1: Success after linux: 12 commits discards d61864f05fa 124: onsuccess: #612: 1: Success after binutils: 18 commits discards a5adcde4dd1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 8ddb3620d63 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards c5548a81b6c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards f39ae95d52a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 9916313cac0 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 1c3586ef628 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 84977afac08 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 90db5fea65f 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 5a087a9db69 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards ff1f69db55b 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 30fd103be70 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards edac67896d6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 0881679655d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards e903cbd8bce 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 7d64f79a4bb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 4233e10f1d2 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 8215492efee 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5861d051f8b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 3bc68d3516c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 117658eb957 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 2c57fb83cc4 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 959a5190078 102: onsuccess: #586: 1: Success after binutils: 5 commits discards c96e1c72502 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards 8b4168cb47e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 6b94469803a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 4bebe2e06e7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 89444e5e765 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards e20df7a3cc1 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 5eed0e19e2a 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards c5115b9ebb3 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 65e8fca81da 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards b29a8ab8c5f 92: onsuccess: #575: 1: Success after linux: 34 commits discards be2cee09caa 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 870b3d76fc9 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 99e504561be 89: onsuccess: #570: 1: Success after linux: 11 commits discards b9edafa083c 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 6c848886086 87: onsuccess: #567: 1: Success after binutils: 8 commits discards fdd4918894b 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards bbfb7d99b27 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards ca8764790a1 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 96e57e5eb16 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 5ce64f8e992 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards f5010d58120 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards c5ba7284264 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards 6a65e30d10b 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 09e0ff1307d 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 7a55e01fda3 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards faa853f5c7a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards e3a5ce54ca2 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 51be15a4305 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 9929097a96f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 5383a6763c1 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 426f4b6c3ac 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 437944dde8f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 4ac304c955d 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards dffec5fe457 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards b38b1c8ecd7 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards f1182f89f48 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 6b677cced41 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards a95264bd608 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 9bf9c899a3e 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards e967cd9a1be 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 2c47810d6e7 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 9034b76b0de 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 7283e3dec40 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards e5c16773365 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 158b7b5b9c5 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 8ae40188189 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 22c649179fa 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 55164a911fa 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards c43f491ed7d 53: onsuccess: #531: 1: Success after binutils: 12 commits discards d28ae86bb7b 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 3638283da8c 51: onsuccess: #525: 1: Success after binutils: 8 commits discards df61137291e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 8ae4bf2f6c8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards d4062e2a2dd 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards 3678e998fe1 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards aecfccf1ec2 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards aef2b516b27 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 9da8d5c1631 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 5fd7f2b8208 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 395cecff910 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 30357fd81ed 41: onsuccess: #514: 1: Success after linux: 64 commits discards b75b6bff467 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards 01febbe49dd 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 27f7c3c12bf 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 5340d04e811 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 0031f0cccf8 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 3005ca9774a 35: onsuccess: #503: 1: Success after binutils: 11 commits discards e7cab50cd3a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 91ae5e92fe6 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 40e3028a4fd 35: onsuccess: #503: 1: Success after binutils: 11 commits new c9e6db9a53c 36: onsuccess: #505: 1: Success after glibc: 3 commits new d3415be2dc3 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 53627dfaa1a 38: onsuccess: #508: 1: Success after binutils: 3 commits new 18306489273 39: onsuccess: #511: 1: Success after binutils: 8 commits new 46314d25894 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new a3c1f6c4557 41: onsuccess: #514: 1: Success after linux: 64 commits new a8aadc755ed 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 19f3746a766 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 404219d7ee0 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 4b1e8da25d0 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new c4404065262 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 1b602ab1d82 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 46ad005ca1f 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new b1af73b03f1 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new 5f6c7268f29 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 9512b8cc611 51: onsuccess: #525: 1: Success after binutils: 8 commits new 8d181fd8b35 52: onsuccess: #528: 1: Success after binutils: 8 commits new 71cc52ea248 53: onsuccess: #531: 1: Success after binutils: 12 commits new 071f929028a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new 9a42b4c4b1e 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new c5d4c37456e 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 6d6511dab2b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new 67690530074 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new b51ca7632b4 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 80dc3c3ea73 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new dde76c6025f 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 824ea91eb06 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new c03c9e3864b 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new e89583188f8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new ee9c3f4a289 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new c888d10f92e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 5c3efcd717c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 65d68d51588 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 556840fb813 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new 489e768327e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new e02597c6f1d 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 0e0f6c769bb 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new d0c4dd318cc 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 58ed8ca1641 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 572b801c58e 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new a7cbc3a33b8 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new 19221bab885 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new a390ffe79fc 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new ef38f646fa2 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 583fa0d4724 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new bba975f6ed1 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new be75c4a0c43 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 0e81c0c96be 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new fa5bbd88491 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 92d6c94cf5a 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 10994b80fd3 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 0c1252efd1f 87: onsuccess: #567: 1: Success after binutils: 8 commits new 1873ad06f24 88: onsuccess: #569: 1: Success after glibc: 10 commits new 05c102d35d8 89: onsuccess: #570: 1: Success after linux: 11 commits new add6f74297d 90: onsuccess: #572: 1: Success after binutils: 15 commits new a329035bbba 91: onsuccess: #574: 1: Success after glibc: 3 commits new ecd17cae8f6 92: onsuccess: #575: 1: Success after linux: 34 commits new 87c2bed3cc3 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 653089565aa 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 67c9e64f20f 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 20dbff9c074 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 92a693f716b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 19ff8b9611f 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 9ead7b68e2b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new cdad1092d62 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 0856c9e184e 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new 49594710a3d 102: onsuccess: #586: 1: Success after binutils: 5 commits new 34cd18e2bbd 103: onsuccess: #589: 1: Success after binutils: 3 commits new 86f3b763e28 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new d9cfebf580a 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 672e2675c77 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e7d827514da 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 786cae989a2 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 0c35877f5f8 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new c3a367d6f71 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new c6591c6404d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 7a14bb6ad21 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new d5eea3068d4 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 8e5540e9149 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 8e339972c2e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new b59ede51184 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new db27b8c3e79 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 7e7ca08172c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 84b6d57a7bd 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 7bcb32b4aa5 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 53562d5859c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 53d6f8b751d 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 99e335092f7 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 2a2c49cae7d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 553daf2e0b7 125: onsuccess: #614: 1: Success after linux: 12 commits new 1ae2173e4d8 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new f708c8fc7c6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 1b511ded523 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 6c9f80f8329 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 51c4919be66 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 244f6a4c30f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 91eaa082790 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new c7a9861db89 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 7de13d88bff 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new d96e4e93008 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (51dca1d6a2f) \ 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 53672 -> 53668 bytes 04-build_abe-gcc/console.log.xz | Bin 236428 -> 235324 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9568 -> 9852 bytes 07-build_abe-glibc/console.log.xz | Bin 238680 -> 236396 bytes 08-build_abe-gdb/console.log.xz | Bin 51840 -> 52324 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3892 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2304 -> 2656 bytes 11-check_regression/console.log.xz | Bin 15800 -> 11792 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 49 +- 11-check_regression/mail-body.txt | 211 +- 11-check_regression/results.compare | 114 +- 11-check_regression/results.compare2 | 3014 ++------------- 11-check_regression/results.regressions | 99 +- 12-update_baseline/console.log | 34 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 213 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 99 +- sumfiles/gdb.log.xz | Bin 1793712 -> 1850740 bytes sumfiles/gdb.sum | 6353 ++++++++++++++++++------------- 31 files changed, 4473 insertions(+), 5767 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (e87d1e4874a -> 07fb1ca0c0b)

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 e87d1e4874a 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards bc04bccc26a 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards b40de93c6d2 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards 482ac0d83f2 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards ea6e42e61a1 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards efec867328d 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards 20d2ecddd77 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards c5f1d67a63d 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards bd89a93d1e2 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards d0a2da2ce03 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards d2307050bee 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards 6662ac60a5d 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards 0dc7a6263bf 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards f0cf6aea42a 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards 1e5bfd5e0e5 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards 540b4485714 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards 282d98191d4 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards d79535f472b 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-4 [...] discards ce052ea8225 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 2d80a1d25ec 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards e8e86c9f163 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] discards 5f0e5d0b2ef 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] discards c00b4d8ad04 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards e69f33eb257 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards 8f5ad2b5dce 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] discards d74d8d9b29d 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 06fc1cdb0b1 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards e0346212c0b 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards decab7840d8 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards e8ddb6b36e4 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards 70ac323d4c3 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 9d75209a9f5 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards 333b6c697c6 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards da63367656a 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 291956f10c2 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards f04ee5fb8d8 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 86dc8545eab 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards cf6ba45441c 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 635bed92719 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards 8bb0b12dbd1 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards b6ec6783798 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 24dde61ba43 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 5e3df814238 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 948ae143527 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards 938e1554ea8 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 99f524ab5eb 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards dc74ef2c3a0 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards b8364b8ca03 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 8867fc1d7da 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 13422c05d9c 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards ae2985706a0 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 1151f4664de 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards e42b5c60d80 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards ec053717a98 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 80da1ae65b6 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards 4ff08271f89 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards f744da63ed8 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 42325a5214a 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 111a549c0e2 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 03751174652 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 32ea8e2bbd4 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 413d6e0b7a2 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards dc3fb6dfa4e 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 478cdfcf78c 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards adb43256364 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 78faec4d3da 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards 8b6d84d8fab 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 2fa9fe62293 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards efd79fe65e0 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 327f2118c09 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 4583bb6af0d 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 1bba8581c82 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 1dbd141841b 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards d6fda528ad4 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 530e4e8af82 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards f93d93ddf27 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards 59f05d56123 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 304355059bc 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 22a63108e04 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 67d4195abbe 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 74e2738ece8 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 0d830e7be00 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 15313351bfd 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards 6cc04e30c1a 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 7c410b0318f 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 82d2612ec28 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 8762d1301e9 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 5b21d982f2b 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 620b222330e 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 54fe3b7d98b 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 784859973a4 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 8ebc6c21405 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 6b9dd3b058c 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards 79e5816b174 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards e08b7860493 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards f2b475ec1b9 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards f3e7099c8a2 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards a7d7e7c6896 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 69cc7274f01 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 906c43bf21d 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards cebdbeeb522 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 3030a1cbb75 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 1f620e5a4ed 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 2cd14a1533d 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 6a0658b3892 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new c0a742e28ed 329: onsuccess: #2285: 1: Success after gcc: 8 commits new fdbaf9ddf21 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 4d5b54333ce 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 0cad1b2c062 332: onsuccess: #2288: 1: Success after gcc: 2 commits new b09aff21bc3 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new daf3358efe0 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 12680a6dd71 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 4385d25bf2f 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new b24565ab5ab 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 6ab36fb2e0b 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new df29be2b725 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new e9ff95f32f3 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 9f83b3e3d83 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 1fd3d87f9aa 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 9d888af8796 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 40677007817 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new f65998e546b 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new aee02241ee1 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 6a7df56b4da 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new c37fc096185 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new bfa148e01be 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 1c91641f8e9 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 3deed439630 351: onsuccess: #2307: 1: Success after binutils: 2 commits new a8e3e684c20 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 2079a262b58 353: onsuccess: #2309: 1: Success after gcc: 7 commits new d79db3640dc 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new b4b4d692cd2 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new de65b4e1438 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 75f0c2278a0 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 88486289f75 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 2c391bb68bb 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new a5a88a66b73 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 3ecf2a3ec35 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 27b08812563 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 110ecd27b36 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new bef8867520e 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 1b043a9cac6 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 1bb8d24e846 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new eb2eb654449 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new a7886c52bef 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 3842e6d9270 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new f354f8f8ef3 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new 7a83304d1d7 371: onsuccess: #2333: 1: Success after binutils: 5 commits new b7c33a18c11 372: onsuccess: #2334: 1: Success after gcc: 5 commits new a1baaf7c703 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 20666c3cb23 374: onsuccess: #2336: 1: Success after gcc: 4 commits new d430befe48d 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 5ff4ee26394 376: onsuccess: #2338: 1: Success after gcc: 2 commits new f2d0b0a8187 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new 0b5c678e175 378: onsuccess: #2340: 1: Success after binutils: 2 commits new f5066507ae0 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 171047fbbe5 380: onsuccess: #2342: 1: Success after gcc: 3 commits new 6923f2885a8 381: onsuccess: #2343: 1: Success after gcc: 2 commits new bc55b4a3ea0 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new bb70f760965 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 1415549259f 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new 9f59d16d5cb 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 41ecad6259a 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new 96780f1e3f0 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 5148c323a3d 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new a654220b2e0 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new dceb836ee3a 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 6df32cf29c6 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 11b446fa3a3 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 6a0a275c4dd 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 80cb3f64c48 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 29eb3a97396 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new 97c40f59b4b 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new 495a5afbd2e 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new 8248842718b 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new ff106e43e2b 399: onsuccess: #2361: 1: Success after gcc: 10 commits new 9e6da539b4c 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new 53e3affe8b8 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint- [...] new e4f8c1d0c20 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new 9be83f2a1ac 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 2cb9ce6f1a9 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-4 [...] new e02bbc8c96a 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-4 [...] new 5a5a823b33a 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new c7b9125aedf 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new 9ca44db7200 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-4 [...] new fcba34acfe4 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new 59b2090821a 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new 037b00d5ea7 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new 417ed57f7c6 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new fa0ee0a3abd 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new 80e7159b3af 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new 31c2da9405e 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new ce4ade7c041 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new ad8d1a3daa8 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 884c3dabbb3 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new 688d6c9a3c1 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new 13e6994cd5b 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 9ef9676130a 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new 2b62f4ab7ee 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new c9156359ade 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new c61e047087c 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new f7c82c81ba2 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new 07fb1ca0c0b 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 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 (e87d1e4874a) \ 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 1904 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39396 -> 40188 bytes 04-build_abe-gcc/console.log.xz | Bin 214928 -> 216824 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3848 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2468 -> 3016 bytes 07-check_regression/console.log.xz | Bin 5416 -> 5356 bytes 07-check_regression/results.compare | 36 +- 07-check_regression/results.compare2 | 112 +- 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3587864 -> 3594972 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3177876 -> 3148520 bytes sumfiles/gcc.sum | 5169 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1052496 -> 1050176 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220332 -> 219588 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2552 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447132 -> 455444 bytes sumfiles/libstdc++.sum | 14 +- 31 files changed, 2863 insertions(+), 2802 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (b321a7cc2c8 -> 3b447e0c3d4)

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 b321a7cc2c8 41: onsuccess: #164: 2: Success after binutils/gcc: 18 commits new 3b447e0c3d4 42: onsuccess: #165: 2: Success after binutils/gcc: 9 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 2756 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 52112 -> 51016 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 464560 -> 462572 bytes 06-check_regression/console.log.xz | Bin 2880 -> 2756 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig updated (053b10a3ef1 -> f7920f66fe8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 053b10a3ef1 28: onsuccess: #470: boot: Success after binutils/gcc: 98 commits new f7920f66fe8 29: onsuccess: #471: 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 1740 -> 1852 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31976 -> 32240 bytes 04-build_abe-stage1/console.log.xz | Bin 73468 -> 73952 bytes 05-build_abe-qemu/console.log.xz | Bin 31152 -> 32036 bytes 06-build_linux/console.log.xz | Bin 3308 -> 3348 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3496 -> 4492 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (1344549494d -> 7f625878b8f)

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 1344549494d 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 937a2d87ae9 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards ede079a96a0 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 081e61f18ce 128: onsuccess: #876: 1: Success after binutils: 12 commits discards e52cd1c3b56 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2d4ba349dab 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 65335292f43 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 0288c8245e2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 6c8e7fab85a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 591eb85960a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 488efe52b4a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards bb213ee53d9 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 7614e887157 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards a9c1005cc5e 118: onsuccess: #863: 1: Success after linux: 12 commits discards 9864670b06b 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 451416b86a6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards ac55f53495f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 6c5b9d55d0f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 4d1112c6249 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards fecb467d37f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 21943cc6b79 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 1add1d469f3 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards d1684553550 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 33e22f09478 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9b5f5c2348d 107: onsuccess: #849: 1: Success after binutils: 5 commits discards e0aebccb26d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 5512847c147 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards e4fe40882a9 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 965b722df49 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards fea0c16b1c4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards f50515b29fc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 949c447cbcc 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 2d3ad4cf831 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards a4c74092590 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 2163168a3f5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 9b6522ad8fa 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 51de7dfebd2 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 162a79dfb2d 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 481b87cd7cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards a810a37af31 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards b525fee49fb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards e4bc3de69a1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 7cc9429951a 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 19380184abc 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards fd9f058c1e8 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards bce55da6d25 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 19f056719af 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 415e6f7e841 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 6ff8fbb7932 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 74b3fa503a7 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards de18808f9c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 89d6c20a416 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 4647ca8c947 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards da12c63e86d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards fce6b274b3d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards b0dd7d9ebe2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 49357091fcc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards e3ecc989650 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 3c005f7c570 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards feceab5eb3e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards e1cd568ad95 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 79a6dd08994 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards e9e90bbed37 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards bebcdf7b72b 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards e79350ad7cc 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 8d1f5624dad 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8d63f46fdaf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 5ac1cbf53ed 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 9a544b63182 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards a7c512865f7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c2e46cb15f3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards c6f03526902 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards a5ddcc4e4ab 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 99d34b2d87d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 72ba16fc4d1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards d24e658acc3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 53c7bf6fb9b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 07e31650e7b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 0dd819bc63a 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards de581d8ad4b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards f11795f5871 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 328cad21365 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards f8e050bdbfd 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 7dbb15e99f5 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 9f860f22758 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 5bf8c098011 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 418f9b62581 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 7d13eae2053 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 19c6a3614b0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 66973e0c7d5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards b6f2d17992b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 5274893fc92 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 113fd015e2d 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 0de75554e63 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards d14b38624e7 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards a12f942070c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 7dd9bd8dfe4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards ee083fd144a 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 9226e8c9230 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 0c5d60f0331 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 0108f7392a2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new f6da4b15dc6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new d808a32d6c9 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new f02b4d5b884 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 36cbf598ad1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new f659df71a32 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 0b5d4745743 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 26c359e7b74 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 4b259a1e5dd 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new b2ca7faa67d 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new f3d48a0735b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new f9e6667e214 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 007b72f2e4e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 755c804a442 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 0773cfd7883 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new d1c9cc61b4d 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new b728b5d81df 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new f9a5fc89465 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 5e70ccb1caf 48: onsuccess: #782: 1: Success after binutils: 8 commits new b4d298ab396 49: onsuccess: #785: 1: Success after binutils: 12 commits new 7fd6fba3642 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 7d0db5c52b5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 37d9a450ee1 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new d07305c0b7f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new bdd440e24b6 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 5bc08b461b3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 7469493d9bb 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 0d5c713ee63 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 90070c23ca3 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new ca92e67c94d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 94e04484712 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 7777f99b47a 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 8842053ef35 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new d4bf740c8d4 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 1ce7bd5d6bd 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new b8161cf0ffb 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 1334e1a1068 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 13367350a9a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 1621e774ae2 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 71b08141760 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 37e2e08f651 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new bbf0552d87a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new b5119c92f9b 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new ea46a6a9c39 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 5191e3f6840 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 441bba26fb6 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 24ea8c2a107 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 8a9def32014 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 97cd48edd9a 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new bff8362e0e0 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 05588a7698d 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new f4f1170204d 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 4b1150f656a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 90abfb4a921 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new a528b6fba09 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 578ab523e19 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 4b896d60c3d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new fe6049befb2 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new e571bae1d6c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new aafa0f53ea0 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 1728f55c173 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 07aecbbc91d 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new b36ceca9f40 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new a350fa4f35f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 83ae852c295 94: onsuccess: #832: 1: Success after binutils: 5 commits new 03c75c41719 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7bb7e1db1c4 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 1b7bfac8b5b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 91aa4f39684 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 9b56537b886 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new abed5775fec 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 189b9c147f1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new a89439238bb 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new a73152fd0bb 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new c6cb3139712 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 62afc410603 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 0fd5ef49e1f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 66d9260407d 107: onsuccess: #849: 1: Success after binutils: 5 commits new cf4c73b3c61 108: onsuccess: #850: 1: Success after gcc: 2 commits new 44ba04c1ead 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 3fd15ecf4a4 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new ad71ce499c0 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new e6e581b774e 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 5aaecd54004 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 96d7c7a5c77 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 8d9672b5f45 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 6847ca54619 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 73add8d9042 117: onsuccess: #861: 1: Success after binutils: 18 commits new a5f7463e1f9 118: onsuccess: #863: 1: Success after linux: 12 commits new 91388531f57 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 9fd35c7e878 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 092f28844d6 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new c6c4ea02873 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new f6af8d0b87a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new a9b2db6d5fc 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 55da97684a9 125: onsuccess: #871: 1: Success after binutils: 26 commits new 96a91418f12 126: onsuccess: #873: 1: Success after glibc: 2 commits new edf637a8774 127: onsuccess: #874: 1: Success after linux: 219 commits new c249ce65126 128: onsuccess: #876: 1: Success after binutils: 12 commits new e9f5a64ce22 129: onsuccess: #878: 1: Success after linux: 3008 commits new 0df9cc83112 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 1f89f2f1ed5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 7f625878b8f 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1344549494d) \ 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 1756 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39540 -> 39808 bytes 04-build_abe-gcc/console.log.xz | Bin 215176 -> 214540 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9600 -> 9780 bytes 07-build_abe-glibc/console.log.xz | Bin 244740 -> 243544 bytes 08-build_abe-gdb/console.log.xz | Bin 39328 -> 39260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3880 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2488 bytes 11-check_regression/console.log.xz | Bin 7508 -> 7388 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 17 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 212 +- 11-check_regression/results.regressions | 37 - 12-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 37 - sumfiles/g++.log.xz | Bin 3754172 -> 3745796 bytes sumfiles/g++.sum | 184 +- sumfiles/gcc.log.xz | Bin 3350216 -> 3307476 bytes sumfiles/gcc.sum | 4892 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081024 -> 1089368 bytes sumfiles/gfortran.sum | 100 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233108 -> 232152 bytes sumfiles/libgomp.sum | 28 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 449368 -> 450744 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 2886 insertions(+), 2909 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[newlib] branch master updated (c04c01524 -> c8130c3fe)

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 newlib. from c04c01524 Revert "amdgcn: Add vectorized math routines" new c8130c3fe Fix 3 other instances of Reme typo (should be Remez) 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: newlib/libm/common/s_expm1.c | 2 +- newlib/libm/common/s_log1p.c | 2 +- newlib/libm/math/e_log.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (71a7507afbc3 -> dcde56bb37a9)

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 71a7507afbc3 Merge tag 'driver-core-6.2-rc1' of git://git.kernel.org/pu [...] new dcde56bb37a9 Fix mismerge due to devnode now taking a 'const *' device 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: drivers/accel/drm_accel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch users/ibhagat/try-sframe-next updated (b47f55e35a4 -> 26ed4e7a54a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/ibhagat/try-sframe-next in repository binutils-gdb. discards b47f55e35a4 libsframe: avoid generating misaligned loads discards 35187fde977 [5/5] sframe: doc: update documentation for pauth key in SF [...] discards d453944fba9 [4/5] gas: sframe: testsuite: add testcase for .cfi_b_key_frame discards 7c3a62f3f11 [3/5] objdump/readelf: sframe: emit marker for SFrame FDE w [...] discards adfbd2c4d1f [2/5] gas: sframe: add support for .cfi_b_key_frame discards 0c2db8fd335 [1/5] sframe.h: add support for .cfi_b_key_frame discards df06d366c29 [6/6] sframe: doc: update spec for the mangled-RA bit in FRE discards 8e1a554e981 [5/6] objdump/readelf: sframe: emit marker for FREs with ma [...] discards a1e721518aa [4/6] libsframe: provide new access API for mangled RA bit discards 9153bde573c [3/6] gas: sframe: testsuite: add testcase for .cfi_negate_ [...] discards 08b4313d5cf [2/6] gas: sframe: add support for .cfi_negate_ra_state discards 07e43da4395 [1/6] sframe.h: add support for .cfi_negate_ra_state adds eb99386180b x86: adjust type checking constructs adds 207cc92d92c RISC-V: Add string length check for operands in AS adds 9399ac88830 gdb/testsuite: fix readnow detection adds 9f50fe08358 gdb/testsuite: new test for recent dwarf reader issue adds b1e678d920e gdb: convert 'set debug symbol-lookup' to new debug printin [...] adds 2698da268bd gdb: add SYMBOL_LOOKUP_SCOPED_DEBUG_ENTER_EXIT adds d1da8dd5bdf Fix haiku ld dependencies adds ad2f3a3f72a asan: buffer overflow in sh_reloc adds 8a0c0290261 Re: ld, gold: remove support for -z bndplt (MPX prefix) adds 45664f164a0 gdb/remote: remove some manual reference count handling adds 91e3d1d1a54 gdb: have target_stack automate reference count handling adds 9678f8fe975 gdb: remove decref_target adds c8181f706f5 gdb: remove the pop_all_targets (and friends) global functions adds 740a579fd5f gdb: ensure all targets are popped before an inferior is de [...] adds 5d80df4a109 gdb/maint: add core file name to 'maint info program-spaces [...] adds 9c71ba0dc4f Automatic date update in version.in adds 9066e0c72bb [gdb/testsuite] Fix gdb.base/condbreak-multi-context.exp wi [...] adds c91a13e4e67 gdb: int to bool conversion in tracefile.c adds 53cf95c3389 gdb: make more use of make_target_connection_string adds c896441822c gdb: some int to bool conversion in remote-sim.c adds 38665d717a3 gdb: use gdb_assert not internal_error adds c573941878c Remove subset_compare adds 2e55fbce03a Move streq and compare_cstrings to gdbsupport adds 69de4313924 gdb/testsuite: don't delete command files in gdb.base/commands.exp adds 8c078abdc23 libsframe asan: avoid generating misaligned loads adds ffd894b51dc Automatic date update in version.in adds f8631e5e04d gdb: remove static buffer in command_line_input adds de75275fe54 gdbsupport: change xml_escape_text_append's parameter from [...] adds 689933867ad x86: change representation of extension opcode adds 22a8433e00f gas: restore Dwarf info generation after macro diagnostic a [...] adds d88cb738e6a [aarch64] Fix removal of non-address bits for PAuth adds 429f0cd1396 gdb/testsuite: add test for Python commands redefining itself adds fa501b69309 Fix a potential illegal memory access when parsing corrupt [...] adds 38c0c0cac9f gdb: clean up some inefficient std::string usage adds 65cded61a22 gdbsupport: add string_xml_appendf adds e60a615dde5 gdb: convert linux-osdata.c from buffer to std::string adds c3efaf0afd9 gdb: fix crash when getting the value of a label symbol adds 832a980e172 [gdb/testsuite] Fix race in gdb.threads/detach-step-over.exp adds c7ce51d8c88 Fix previous delta to allow for compilation on 32-bit systems adds 9dff6a5d54f Delay checking whether /proc/pid/mem is writable (PR gdb/29907) new ddebd2092bd sframe.h: add support for .cfi_negate_ra_state new 222810e627e gas: sframe: add support for .cfi_negate_ra_state new bb73f2209b1 gas: sframe: testsuite: add testcase for .cfi_negate_ra_state new 4b6bddd0eef libsframe: provide new access API for mangled RA bit new 75021b3a299 objdump/readelf: sframe: emit marker for FREs with mangled RA new 26ed4e7a54a sframe: doc: update spec for the mangled-RA bit in FRE 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 (b47f55e35a4) \ N -- N -- N refs/heads/users/ibhagat/try-sframe-next (26ed4e7a54a) 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 6 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: bfd/coff-sh.c | 3 +- bfd/version.h | 2 +- binutils/ChangeLog | 5 + binutils/NEWS | 4 + binutils/doc/binutils.texi | 5 + binutils/dwarf.c | 21 +- binutils/objdump.c | 22 + binutils/testsuite/binutils-all/objdump.exp | 26 + gas/config/tc-i386.c | 4 +- gas/config/tc-riscv.c | 3 +- gas/gen-sframe.c | 26 +- gas/gen-sframe.h | 2 +- gas/input-scrub.c | 3 - gas/macro.c | 5 +- gas/sframe-opt.c | 3 - .../cfi-sframe/cfi-sframe-aarch64-pac-ab-key-1.d | 25 - .../cfi-sframe/cfi-sframe-aarch64-pac-ab-key-1.s | 36 - gas/testsuite/gas/cfi-sframe/cfi-sframe.exp | 1 - gas/testsuite/gas/elf/dwarf-5-macro-include.d | 17 + gas/testsuite/gas/elf/dwarf-5-macro-include.inc | 3 + gas/testsuite/gas/elf/dwarf-5-macro-include.s | 5 + gas/testsuite/gas/elf/elf.exp | 1 + gas/testsuite/gas/riscv/vector-insns-fail-vsew.d | 3 + gas/testsuite/gas/riscv/vector-insns-fail-vsew.l | 3 + gas/testsuite/gas/riscv/vector-insns-fail-vsew.s | 1 + gdb/NEWS | 4 + gdb/aarch64-linux-nat.c | 2 +- gdb/aarch64-linux-tdep.c | 48 +- gdb/ada-lang.c | 3 +- gdb/arch-utils.c | 8 + gdb/arch-utils.h | 4 + gdb/arch/aarch64.c | 31 + gdb/arch/aarch64.h | 18 + gdb/breakpoint.c | 10 +- gdb/cli/cli-script.c | 19 +- gdb/cli/cli-script.h | 11 +- gdb/cp-namespace.c | 113 +- gdb/defs.h | 3 +- gdb/doc/gdb.texinfo | 8 +- gdb/event-top.c | 113 +- gdb/findvar.c | 50 +- gdb/gdbarch-components.py | 22 +- gdb/gdbarch-gen.h | 21 +- gdb/gdbarch.c | 24 +- gdb/inferior.c | 90 +- gdb/inferior.h | 20 + gdb/language.c | 12 +- gdb/linespec.c | 4 +- gdb/linux-nat.c | 9 +- gdb/mi/mi-cmd-break.c | 2 +- gdb/minsyms.c | 31 +- gdb/nat/linux-osdata.c | 287 +- gdb/progspace.c | 18 +- gdb/python/py-breakpoint.c | 2 +- gdb/python/py-gdb-readline.c | 3 +- gdb/python/python.c | 2 +- gdb/remote-sim.c | 20 +- gdb/remote.c | 40 +- gdb/rust-lang.h | 12 +- gdb/scoped-mock-context.h | 2 +- gdb/stack.c | 6 +- gdb/symtab.c | 261 +- gdb/symtab.h | 33 + gdb/target-connection.c | 5 +- gdb/target.c | 87 +- gdb/target.h | 25 +- .../aarch64-non-address-bits.c} | 41 +- .../gdb.arch/aarch64-non-address-bits.exp | 118 + gdb/testsuite/gdb.base/commands.exp | 14 +- gdb/testsuite/gdb.base/condbreak-multi-context.cc | 6 +- ...multi-context.cc => signed-builtin-types-lib.c} | 42 +- ...eak-multi-context.cc => signed-builtin-types.c} | 39 +- gdb/testsuite/gdb.base/signed-builtin-types.exp | 112 + gdb/testsuite/gdb.opt/break-on-_exit.exp | 3 +- gdb/testsuite/gdb.python/py-cmd.exp | 30 + gdb/testsuite/gdb.python/py-connection-removed.exp | 92 + .../py-label-symbol-value.c} | 44 +- gdb/testsuite/gdb.python/py-label-symbol-value.exp | 39 + gdb/testsuite/gdb.rust/traits.exp | 2 - gdb/testsuite/gdb.threads/detach-step-over.exp | 34 +- gdb/testsuite/lib/gdb.exp | 30 +- gdb/testsuite/lib/mi-support.exp | 28 +- gdb/top.c | 42 +- gdb/top.h | 8 +- gdb/tracefile.c | 6 +- gdb/tui/tui-win.c | 4 +- gdb/unittests/xml-utils-selftests.c | 2 +- gdb/utils.c | 50 - gdb/utils.h | 17 - gdbserver/linux-aarch64-low.cc | 33 +- gdbserver/linux-low.cc | 2 +- gdbserver/netbsd-low.cc | 2 +- gdbsupport/common-debug.h | 92 +- gdbsupport/common-utils.h | 16 + gdbsupport/xml-utils.cc | 121 +- gdbsupport/xml-utils.h | 12 +- gold/testsuite/Makefile.am | 39 - gold/testsuite/Makefile.in | 162 +- gold/testsuite/bnd_ifunc_1.s | 16 - gold/testsuite/bnd_ifunc_1.sh | 36 - gold/testsuite/bnd_ifunc_2.s | 28 - gold/testsuite/bnd_ifunc_2.sh | 50 - gold/testsuite/bnd_plt_1.s | 9 - gold/testsuite/bnd_plt_1.sh | 52 - include/sframe.h | 25 +- ld/emulparams/aarch64haiku.sh | 2 +- ld/emulparams/armelf_haiku.sh | 2 +- ld/emulparams/elf32ppchaiku.sh | 4 +- ld/emulparams/elf_mipsel_haiku.sh | 4 +- ld/emulparams/elf_x86_64_haiku.sh | 4 +- libsframe/doc/sframe-spec.texi | 8 +- libsframe/sframe-dump.c | 19 - libsframe/sframe.c | 2 +- opcodes/i386-gen.c | 9 +- opcodes/i386-opc.tbl | 4561 ++++++++++---------- opcodes/i386-tbl.h | 4 +- 116 files changed, 3991 insertions(+), 3838 deletions(-) delete mode 100644 gas/testsuite/gas/cfi-sframe/cfi-sframe-aarch64-pac-ab-key-1.d delete mode 100644 gas/testsuite/gas/cfi-sframe/cfi-sframe-aarch64-pac-ab-key-1.s create mode 100644 gas/testsuite/gas/elf/dwarf-5-macro-include.d create mode 100644 gas/testsuite/gas/elf/dwarf-5-macro-include.inc create mode 100644 gas/testsuite/gas/elf/dwarf-5-macro-include.s create mode 100644 gas/testsuite/gas/riscv/vector-insns-fail-vsew.d create mode 100644 gas/testsuite/gas/riscv/vector-insns-fail-vsew.l create mode 100644 gas/testsuite/gas/riscv/vector-insns-fail-vsew.s copy gdb/testsuite/{gdb.base/condbreak-multi-context.cc => gdb.arch/aarch64-non-ad [...] create mode 100644 gdb/testsuite/gdb.arch/aarch64-non-address-bits.exp copy gdb/testsuite/gdb.base/{condbreak-multi-context.cc => signed-builtin-types-li [...] copy gdb/testsuite/gdb.base/{condbreak-multi-context.cc => signed-builtin-types.c} (66%) create mode 100644 gdb/testsuite/gdb.base/signed-builtin-types.exp create mode 100644 gdb/testsuite/gdb.python/py-connection-removed.exp copy gdb/testsuite/{gdb.base/condbreak-multi-context.cc => gdb.python/py-label-sym [...] create mode 100644 gdb/testsuite/gdb.python/py-label-symbol-value.exp delete mode 100644 gold/testsuite/bnd_ifunc_1.s delete mode 100755 gold/testsuite/bnd_ifunc_1.sh delete mode 100644 gold/testsuite/bnd_ifunc_2.s delete mode 100755 gold/testsuite/bnd_ifunc_2.sh delete mode 100644 gold/testsuite/bnd_plt_1.s delete mode 100755 gold/testsuite/bnd_plt_1.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allmodconfig updated (af8b32803f4 -> 8e3bdfecce9)

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-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from af8b32803f4 46: force: #533: all: Success after linux: 947 commits new 8e3bdfecce9 47: force: #534: 23540: Failure after v6.1-rc4-1107-g8cab76 [...] 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 1976 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32072 -> 32256 bytes 04-build_kernel_llvm/console.log.xz | Bin 67080 -> 66548 bytes 05-build_abe-qemu/console.log.xz | Bin 31152 -> 31752 bytes 06-build_linux/console.log.xz | Bin 3088 -> 3568 bytes 07-boot_linux/console.log.xz | Bin 504 -> 0 bytes 08-check_regression/console.log.xz | Bin 2908 -> 3812 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 15 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 7 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 609 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 10 +- results | 11 +- 26 files changed, 666 insertions(+), 24 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.

2 years, 5 months

[toolchain/ci/interesting-commits] branch master updated (92ddc788 -> 922b17ef)

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 92ddc788 Add entry 969b9a36506bfb386f8ce30f88f1a6a6ebbaca6e from https [...] new 922b17ef Add entry 8cab76ec634995e59a8b6346bf8b835ab7fad3a3 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: .../tcwg_kernel/llvm-master-aarch64-mainline-allmodconfig}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../8cab76ec634995e59a8b6346bf8b835ab7fad3a3/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy linux/sha1/{0d2b746b1bef73de62d2d311e594a7ffed4ca434/tcwg_kernel/llvm-master- [...] copy linux/sha1/8cab76ec634995e59a8b6346bf8b835ab7fad3a3/tcwg_kernel/{llvm-master- [...] copy linux/sha1/8cab76ec634995e59a8b6346bf8b835ab7fad3a3/tcwg_kernel/{llvm-master- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022