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 (c6abf6c266 -> 0ac2e6e6aa)

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 c6abf6c266 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 8a9aa90151 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 50d712d1e5 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 79c3fd2088 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 077dd52ca3 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards e583aec302 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 7e275296c9 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards d1d4b9010d 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 6bc46cc92b 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards cc736445c5 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards b35ce9c0e4 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards f521e59c9d 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 533243d186 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 6c58b29ded 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 517b6a2c83 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards e13ecde9dd 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards bc5c60f363 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards a3343d1b40 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 736871257c 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards bfff75fe82 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 956d67fd49 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 5dbbd6a62d 125: onsuccess: #614: 1: Success after linux: 12 commits discards 3859f6706c 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 30d47d082a 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 9fba1237f6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 485fe4c56a 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 767f5357f7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards de3c1803a3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 637454b2a6 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 775a86a7d8 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 88180832da 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 2a8e155eb0 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 128f18a6ac 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 2fce7f0213 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards eb64b29da1 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 96f189219e 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 1931dbd71f 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 9a7bb00944 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 6ed155ce11 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards fd9d046e84 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 046f9dec3a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 6e1040fadd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards d5ba2eb99e 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards fbb8ff016c 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 081841d8be 102: onsuccess: #586: 1: Success after binutils: 5 commits discards fa920464e8 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 0281bc4b20 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 91c5c27602 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards d467cbec40 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 31dc1d7cbe 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards a0417ccdf9 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards b19080e64e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 9c366c5012 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 0264229704 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 2a9f19ef3f 92: onsuccess: #575: 1: Success after linux: 34 commits discards ced177c903 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 6dba5ee925 90: onsuccess: #572: 1: Success after binutils: 15 commits discards f66fa4f117 89: onsuccess: #570: 1: Success after linux: 11 commits discards c70fde1f75 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 98c5545531 87: onsuccess: #567: 1: Success after binutils: 8 commits discards ec42947866 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 2d5750e04d 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 8f3f1d19af 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 12b645fd7d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 4a148b9a58 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 4e425436b9 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards ce9c0ef526 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards f3b49466a8 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 8ce0cd4648 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards b18057a710 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards c48bc42638 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 83023d8949 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards b7a372a88c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards d689466501 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards e16c011253 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards e3083630d8 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards bf53b2aca3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 07df97eacf 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards cbdad71f5b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e826ddd534 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 2df0ace345 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards e31a7d0bfb 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 1a2fe89874 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 6d9d81515b 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards fa41ef7242 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 9bfff317e1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 5f0bfb5525 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 314946352e 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 8f7247ed91 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards c31d893b68 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 65ee98a3b7 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards cf42ee7d3d 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 9773b283f5 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards d787f4eb18 53: onsuccess: #531: 1: Success after binutils: 12 commits discards ac1ba41ba9 52: onsuccess: #528: 1: Success after binutils: 8 commits discards c0079cb50f 51: onsuccess: #525: 1: Success after binutils: 8 commits discards c80434266c 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards a5b9132f92 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards d235f318f5 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 4a044fb10a 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards eb974bb457 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new c59fb6dda4 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new fe4b6acc63 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 6d67be3a94 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 4e278b4d17 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 87ec9ddbbe 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 2f57f9944c 51: onsuccess: #525: 1: Success after binutils: 8 commits new c3a0acbf12 52: onsuccess: #528: 1: Success after binutils: 8 commits new 66c218448f 53: onsuccess: #531: 1: Success after binutils: 12 commits new 91aaf9e84a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 0d94bb0a12 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 8e91293400 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 5941368c1f 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 5aa6d9c32c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 6d3564c6ea 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new e6ea834bef 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new d16666d77e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 3ec17cbe93 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new d434a245eb 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 63f87abaa0 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 6e640dd1b6 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new fbd79aa2a0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e3d6efa932 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 4839818292 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 9a20882e2a 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 0dd54c5189 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new ba6db754fc 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 86a08d290e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 67636ef2c8 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 49a039ea29 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new bfb999288f 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new ac89cef3cc 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new fa28b278da 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new d54ca08680 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new b316705a2d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new a5bc768c7b 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 230f64bc92 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new e9d2594f3b 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new ff2274309d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new ddf761dbc1 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new bd958c8efd 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 77f136a4dc 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 3e971060ef 87: onsuccess: #567: 1: Success after binutils: 8 commits new 65e23639a4 88: onsuccess: #569: 1: Success after glibc: 10 commits new b9ae89319a 89: onsuccess: #570: 1: Success after linux: 11 commits new 785f2289e2 90: onsuccess: #572: 1: Success after binutils: 15 commits new 8b9c768a08 91: onsuccess: #574: 1: Success after glibc: 3 commits new a6e05ad34f 92: onsuccess: #575: 1: Success after linux: 34 commits new c06701af1d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 0877a38a6d 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new cb1774497d 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 1b73febc99 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 71e275e2a5 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new b94aa1b4ed 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new f34a585dff 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 640296c095 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 2f71c57b89 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 6e90f2631c 102: onsuccess: #586: 1: Success after binutils: 5 commits new 14df8f6660 103: onsuccess: #589: 1: Success after binutils: 3 commits new 9510c43aa5 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new a027fdec6a 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 0b6bc6806f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 7ae8edec2c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new d8c345a3f4 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new b786c18d82 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 70b55b78bd 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 789daae745 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 7e697f2548 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new f972c5d791 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new cd76eac69f 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 5305d7360e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 6ca69b4db4 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new bd57f458d9 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new df6e0d491a 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 7f62a430b6 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new aa8d3225f5 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new eb39c927cd 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 626b5dfccc 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 0facc32aeb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 1c65e42df3 124: onsuccess: #612: 1: Success after binutils: 18 commits new 4088b937a6 125: onsuccess: #614: 1: Success after linux: 12 commits new dd0f6badee 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 6fe7ca075c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e9142fdc48 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 8db347fdf3 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 8173de9027 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new bd0b6b8e7a 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 6409a1ef56 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 95235cb24a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new dd1a4bdf9b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 37ec61698b 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new ccf3ed8bf0 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new ea48ee8025 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new c14a0349f5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 416868be77 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 4a08c66ce6 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new e6d6280d14 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new cb8aadbbab 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new e99a435c4e 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new eedf5b1665 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new a47b198320 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 3349c0284e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 0ac2e6e6aa 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 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 (c6abf6c266) \ 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 1744 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 54128 -> 52872 bytes 04-build_abe-gcc/console.log.xz | Bin 240808 -> 240124 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8332 -> 8428 bytes 07-build_abe-glibc/console.log.xz | Bin 236608 -> 238832 bytes 08-build_abe-gdb/console.log.xz | Bin 51656 -> 52540 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2428 -> 2208 bytes 11-check_regression/console.log.xz | Bin 11112 -> 7708 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 42 +- 11-check_regression/mail-body.txt | 184 +- 11-check_regression/results.compare | 91 +- 11-check_regression/results.compare2 | 1990 +----------- 11-check_regression/results.regressions | 91 +- 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 186 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 91 +- sumfiles/gdb.log.xz | Bin 1716312 -> 1694500 bytes sumfiles/gdb.sum | 5096 +++++++++++++++---------------- 29 files changed, 3062 insertions(+), 4795 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig updated (5965102ebc -> 95cad30fce)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 5965102ebc 30: onsuccess: #256: all: Success after binutils/linux/qemu: [...] new 95cad30fce 31: onsuccess: #257: all: Success after binutils: 4 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 1764 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30368 -> 30004 bytes 04-build_kernel_llvm/console.log.xz | Bin 64688 -> 62040 bytes 05-build_abe-qemu/console.log.xz | Bin 31384 -> 30964 bytes 06-build_linux/console.log.xz | Bin 3464 -> 3436 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3708 -> 2860 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 15 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (9e24e503b4 -> 77a393f38d)

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 9e24e503b4 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards b7fe61c15e 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 47c902f6b6 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 7f0c30b1cd 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 4c4ef76ec6 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 2f25e84e95 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 3e0986460f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards eebce76ff7 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 64714af42c 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 208e765723 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards c52a8413b2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards bc422a6aee 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards b3a62c2ac8 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 40c661f858 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 45f0e79f88 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 53e46c8481 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 57d53d69e9 127: onsuccess: #874: 1: Success after linux: 219 commits discards c2c8d7b216 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 3f0aae12fc 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 01dc0e7770 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards a53a6da6e2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards f8f52511f9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards c8ec0f95de 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ad3e31ab15 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards a1dc543e81 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards bbfc7f4c4e 118: onsuccess: #863: 1: Success after linux: 12 commits discards 6dfc06d53f 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 14dd49d2f6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 077c2cbb9c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 63bfd40657 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards f472b2d4e8 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards ebf0d2ae5f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 1dee7cb721 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards caaaaf475e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 93964a6905 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 761c2b3ae1 108: onsuccess: #850: 1: Success after gcc: 2 commits discards a31262c584 107: onsuccess: #849: 1: Success after binutils: 5 commits discards f40d4a077e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards cb0b49ec3d 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 58aa93f7d8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards be036af736 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards b352e63d62 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards ccb41f6f46 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards c45035f4c8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards c691098b47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 8cbf686355 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 36d98ca4f8 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards e324ddbe4e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 26e8dd63c8 95: onsuccess: #835: 1: Success after binutils: 3 commits discards cd5e7f0fdf 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 9c9c9eb441 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 4b78d222a5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 56e449485d 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 807e08b410 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards e67a1c2f3c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards f853c97731 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards f697139498 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 385ae38bf4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 85971cc643 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 0048c063c8 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 3b53ef1483 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards de924adcd0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 2e222f9989 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0b6dac95f8 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 2bd598b802 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 12af03224b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards f1862164fc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards f895d6eac4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards e0a60bc39d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 177dfe372c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards b711be8381 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards c40cceb691 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards d905362749 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 63bf975e38 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 57a0d4f843 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 4a625c12ab 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 26df8d8547 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 6a67f5cae2 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 290a1193d7 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards cf895c42f4 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 4375eed3ec 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 2e6c1f5ed7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 9d46137902 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 7ec5826572 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards e81113a750 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards d5264bd26f 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 9c056a71fd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 02ec84db40 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 7a8fc7708d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards bd745a82a2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 6637b4e30f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 51f590e967 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 9ca0279232 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards b0626addad 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards d41a8315c3 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 8832bfaa9b 48: onsuccess: #782: 1: Success after binutils: 8 commits discards a55848614d 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 185c5f25f4 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 92fea1ea6c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards b4bb5f776b 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 8b8a0b1e00 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 7e4596d41e 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 29d1b93781 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new d365b578f5 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 74c31ad4d5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 1adc18cce2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new b31b100852 48: onsuccess: #782: 1: Success after binutils: 8 commits new 0b1b120554 49: onsuccess: #785: 1: Success after binutils: 12 commits new 0415cf1c39 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 1292b09ed4 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new e1ccc60399 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 543cd79c6f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 6cd53f163a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 96526bfe65 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 295774c30a 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new fea32b80b9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 36a5002f8a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new fba45f217b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new f39f6a3c44 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 10e94b81f1 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 5327f1d355 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new df2ccd9da0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new f5eff59d75 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 5dd1ae1133 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new aad3b641d6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8f65c70663 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 268bbffdee 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 80b074a62b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new ebb6b78f0c 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 24ee31c89b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 5e267444ee 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 04ff134229 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 8683f57d9c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 333065644e 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 3ec44caac0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new d54a435ee4 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new dfac8582f1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 7f59f761ac 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 7e3881f187 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 080ba6c4f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 402f69e6ef 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 8691904441 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new cbfd8fd6fd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 36e0550617 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 76badb6424 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new b490c099f6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 2400f643e0 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 9d5c42b655 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0f54c2e826 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new abc07571a3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5b4accfc6b 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 06df8271ed 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 026786b387 94: onsuccess: #832: 1: Success after binutils: 5 commits new 3ca9126fdd 95: onsuccess: #835: 1: Success after binutils: 3 commits new 06988a334f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 96b0f5b851 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 568d9cdc57 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 94d02e6b04 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 52e95e95a8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 55a98a2798 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new aecfdbdc96 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 985666ec4a 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 2ff6e6f6ab 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new d145dc8d4f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new c48b7da249 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 8f5c62498e 107: onsuccess: #849: 1: Success after binutils: 5 commits new c71a7d355a 108: onsuccess: #850: 1: Success after gcc: 2 commits new af304e8035 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 7b3ce70931 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new d6ed9c2243 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new fd0c431ead 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 0401b9c15c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 6f14db952c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 7d3409d1ab 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 574c04f0b1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 530eba5ce5 117: onsuccess: #861: 1: Success after binutils: 18 commits new 85fd1a565c 118: onsuccess: #863: 1: Success after linux: 12 commits new fb41c51340 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 2e394f9b39 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 97d336663c 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 641a9d8151 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new c421e848fb 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 47c1b23d33 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 835dd77589 125: onsuccess: #871: 1: Success after binutils: 26 commits new 657c50cfcc 126: onsuccess: #873: 1: Success after glibc: 2 commits new 6bc40fe449 127: onsuccess: #874: 1: Success after linux: 219 commits new 81023c14aa 128: onsuccess: #876: 1: Success after binutils: 12 commits new 4c87e70201 129: onsuccess: #878: 1: Success after linux: 3008 commits new faa1da1510 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 8729bb78a5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 0fb0b1148a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 006b8a3763 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 9c385c1025 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new cacb58b1df 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new b30d62a1f9 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 74297ec058 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 839d381ef7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 112ace12b3 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 3c4bcacabc 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 978d00d000 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 3e41c40e51 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 375724eb76 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 77a393f38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 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 (9e24e503b4) \ 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 1752 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40344 -> 39800 bytes 04-build_abe-gcc/console.log.xz | Bin 214880 -> 214496 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8348 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 244776 -> 244684 bytes 08-build_abe-gdb/console.log.xz | Bin 39712 -> 39348 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2424 bytes 11-check_regression/console.log.xz | Bin 5464 -> 5656 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 18 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3768040 -> 3731524 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3313864 -> 3291524 bytes sumfiles/gcc.sum | 4845 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1081568 -> 1079284 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232920 -> 232132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459756 -> 456444 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2607 insertions(+), 2598 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allmodconfig updated (2b148e3c0a -> ef9cb2cdee)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 2b148e3c0a 34: onsuccess: #411: all: Success after binutils/gcc/linux/q [...] new ef9cb2cdee 35: onsuccess: #412: all: Success after binutils/gcc: 10 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30236 -> 30000 bytes 04-build_abe-stage1/console.log.xz | Bin 87148 -> 86960 bytes 05-build_abe-qemu/console.log.xz | Bin 31680 -> 30716 bytes 06-build_linux/console.log.xz | Bin 3516 -> 3460 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4040 -> 3216 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 | 24 ++++++++++++------------ 15 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allmodconfig updated (50e3aede18 -> 92db59ddc0)

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-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 50e3aede18 34: onsuccess: #496: 33: Success after binutils/gcc/linux/qe [...] new 92db59ddc0 35: onsuccess: #497: 33: Success after binutils/gcc: 68 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32492 -> 31716 bytes 04-build_abe-stage1/console.log.xz | Bin 92612 -> 91548 bytes 05-build_abe-qemu/console.log.xz | Bin 31568 -> 31576 bytes 06-build_linux/console.log.xz | Bin 5256 -> 5128 bytes 08-check_regression/console.log.xz | Bin 4376 -> 3424 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 | 24 ++++++++++++------------ 14 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os_LTO updated (bf40f5f9b2 -> 961c741831)

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_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os_LTO in repository toolchain/ci/base-artifacts. from bf40f5f9b2 41: onsuccess: #355: 1: [TCWG CI] No change after binutils/g [...] new 961c741831 42: onsuccess: #356: 1: [TCWG CI] No change after binutils/g [...] 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 1792 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31936 -> 31736 bytes 04-build_abe-stage1/console.log.xz | Bin 90988 -> 89672 bytes 06-build_abe-newlib/console.log.xz | Bin 15148 -> 15088 bytes 07-build_abe-stage2/console.log.xz | Bin 165992 -> 164724 bytes 08-benchmark/benchmark-build.log | 86 ++++++++++----------- 08-benchmark/benchmark.log | 84 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3820 -> 3820 bytes 09-check_regression/console.log.xz | Bin 4988 -> 4556 bytes 09-check_regression/results-vs-first.log | 4 +- 09-check_regression/results-vs-prev.log | 4 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 28 ++++--- mail/mail-body.txt | 28 ++++--- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++--- results_id | 2 +- 23 files changed, 149 insertions(+), 153 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (5dcd6eda9f -> 638e373f36)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 5dcd6eda9f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 638e373f36 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 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 1784 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40020 -> 39712 bytes 04-build_abe-gcc/console.log.xz | Bin 214588 -> 214724 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 246800 -> 247240 bytes 08-build_abe-gdb/console.log.xz | Bin 40448 -> 40204 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2864 -> 2552 bytes 11-check_regression/console.log.xz | Bin 5272 -> 5276 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 3 --- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14616 -> 14652 bytes sumfiles/gdb.sum | 4 ++-- 22 files changed, 25 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (b771fa633d -> 36da4db59b)

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-arm in repository toolchain/ci/base-artifacts. discards b771fa633d 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 40a1a5c874 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 96341619be 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 477fa1cab5 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 76381cf9df 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 07ae744992 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7e04633aac 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 0a3603fd2f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards e29fa63508 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f545751d44 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards a62be32dea 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards a56ef611b5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 54e994ae3e 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards d2b50ef89b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 31865922c9 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 4ca4d382ad 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 5369b826b1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 69801de38e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards f43600dfef 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 5eab99e53c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 7692cb388e 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 6d43af8228 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 77223fd572 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a7ea2034b3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 048a492995 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 0175f40447 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 7fb0c6193a 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 4224142bae 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 52eef1be6b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 012c760701 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 5c10563371 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 2beeea5e79 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards f092cf3f32 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 812093bc91 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 3d4ec7ba28 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 7ee1460ad9 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 0b08b8f109 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1b0af3e5be 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d9e0355552 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards ded6b5d63b 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 77e2703d86 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1a4767027c 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 611ff1027a 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 4d9a676b49 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards fdf3fb89ab 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 1f9d7cdb79 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 33d312e58a 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 61d74fab6d 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 8dd676240f 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 84cadc62f1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 3860db90e7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards fd767ee082 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards a429f1068a 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 10663e9a31 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 5fac00f2d4 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 6dd26abe3d 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards cd9987bbda 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 05abf545cf 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 16775e417e 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 424b74eb1d 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 21b97b15e5 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards dde1eae8e2 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 27e56ae8fd 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards c3684d0b3f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 260f4f6420 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 0529d847b3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 41d683f7b5 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 41fe1c37a9 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 5cd215b1de 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards d54c995c89 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards cc2fa502c8 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards e9e92cd4fa 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 0f63cc7b46 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 0c7499371c 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards d0ca85a1e1 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards d132cb081a 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 74f2885bce 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards e4c2e59992 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 2b615d454b 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards ccde6d8b16 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 58d892973e 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards d3b375d587 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 0dc69a95a3 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards f174c6f62b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards c19daa4b61 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards c4db2da6e6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards c1fd2ddc22 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 4eb764fec1 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 8c159469e3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 605e4ca6a3 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 6b76443374 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards cabb7e8966 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 6410b36b63 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 6846055d41 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 140327cf87 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 6c6d72b2dc 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 85584c7d1f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards eeb39420ab 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards aaa2a81584 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 38fa6eb6b8 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards c941efb401 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 00ae8dbf54 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 5518066d3d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new baf3bf86c4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 25555b712d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 9f79f9251c 193: onsuccess: #1992: 1: Success after binutils: 151 commits new ad0b5ddc7b 194: onsuccess: #1995: 1: Success after linux: 517 commits new 7f16ee8f7c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 61a36465ce 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 8dd1657a37 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 420f6de0d9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 71f7ebb8da 199: onsuccess: #2000: 1: Success after gcc: 5 commits new d5984e1ca5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new af12ced131 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 296f8bce16 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 7a96d6d5f8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new e12aa123c2 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new a33b3e8071 205: onsuccess: #2006: 1: Success after gcc: 3 commits new b4b7c6befc 206: onsuccess: #2007: 1: Success after gcc: 2 commits new eddc5b9af7 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 7f52c08444 208: onsuccess: #2012: 1: Success after linux: 12 commits new 9f5cab9586 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 8d501f2460 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 376bea3c46 211: onsuccess: #2020: 1: Success after binutils: 10 commits new e4c06702f1 212: onsuccess: #2022: 1: Success after linux: 3 commits new a8896ed791 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 0cd3ce8f15 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 3dfab5ae47 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 2030665206 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new efa794fbd8 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new a9ab3fd678 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 457f79442d 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 530f709e92 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 0525557cb9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 685b15bd0c 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 19e1037f04 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 86a63e2286 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 35ece92dd1 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 82cce7704c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new e21fbaae76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new c77253b874 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 2b52f07bee 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new d318e62018 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new dff3066d45 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 03843739b6 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7234e945c9 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 9aee585667 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 45cef1cf2c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new b3d12272ba 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new fc77f53eff 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 5020e8327b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 632814f5d3 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new a9141efdb5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 32697a4908 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 623bab7ea3 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 2065ebe0e5 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 099263e99a 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 154f438061 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new f404da0fb0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 01a1ea7120 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 39888b0541 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new b359ae5515 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d2bc607c77 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new d6d2030fc3 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new a58a63dcde 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new cece3392bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 5fae511369 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 9d65628b05 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 78a070f225 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6cb992c223 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new a47a3f47f6 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 8a3336e973 259: onsuccess: #2075: 1: Success after glibc: 2 commits new c0615c70a7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new cf830e438c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 4e16cfc0f3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 8ff448a0a1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 4378861f2a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new e4c70bea04 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new c31b6d7374 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new bc58994936 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 94366b3f86 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new bb85b52c6e 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new d43fda5df1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 1705ccabe9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new d372083848 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9f85ce9093 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5a1840c8d6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 90f4762f56 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 009e4fddbd 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d61f7c1282 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 60af7eb096 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new bc4d5a0c7c 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 4df1ed580d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 72b7b7abda 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 60e083ef0b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 80c0315a31 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new bc04f0ce0c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 1c8ae08759 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 266792f43b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new b13edd1e4f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new af2b2c037d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new fe85bcc795 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 36da4db59b 290: onsuccess: #2106: 1: Success after gcc: 2 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 (b771fa633d) \ 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 1808 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31872 -> 31928 bytes 04-build_abe-stage1/console.log.xz | Bin 92136 -> 91884 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 236996 -> 237088 bytes 08-build_abe-stage2/console.log.xz | Bin 228356 -> 228312 bytes 09-build_abe-gdb/console.log.xz | Bin 39120 -> 39204 bytes 10-build_abe-qemu/console.log.xz | Bin 31088 -> 31132 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2588 -> 2532 bytes 13-check_regression/console.log.xz | Bin 5872 -> 5328 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 - sumfiles/g++.log.xz | Bin 2667684 -> 2662568 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2260716 -> 2275044 bytes sumfiles/gcc.sum | 2269 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 893524 -> 892840 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214016 -> 214080 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431296 -> 435604 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1259 insertions(+), 1310 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (e75e5dc7ab -> 0f6a0af0b6)

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-arm in repository toolchain/ci/base-artifacts. discards e75e5dc7ab 467: onsuccess: #2109: 1: Success after gcc: 2 commits discards e08bc4d613 466: onsuccess: #2108: 1: Success after binutils/gcc: 5 commits discards d61a156d48 465: onsuccess: #2107: 1: Success after binutils/gcc: 6 commits discards 52ef5cde09 464: onsuccess: #2106: 1: Success after gcc: 9 commits discards 5f015ebd6e 463: onsuccess: #2105: 1: Success after binutils/gcc: 10 commits discards dce326fbc0 462: onsuccess: #2104: 1: Success after binutils/gcc: 2 commits discards 215c9f86d2 461: onsuccess: #2103: 1: Success after binutils/gcc: 2 commits discards 938156e030 460: onsuccess: #2102: 1: Success after binutils: 2 commits discards 74bf398c6d 459: onsuccess: #2101: 1: Success after binutils/gcc: 3 commits discards fa62388677 458: onsuccess: #2100: 1: Success after gdb-13-branchpoint-1 [...] discards 836526e69d 457: onsuccess: #2099: 1: Success after binutils/gcc: 2 commits discards b29af34916 456: onsuccess: #2098: 1: Success after binutils: 10 commits discards 1681565675 455: onsuccess: #2097: 1: Success after binutils/gcc: 11 commits discards 4e53b819f5 454: onsuccess: #2096: 1: Success after gcc: 4 commits discards ee05287002 453: onsuccess: #2095: 1: Success after gdb-13-branchpoint-1 [...] discards 21066a6638 452: onsuccess: #2094: 1: Success after binutils/gcc: 4 commits discards e5896e21eb 451: onsuccess: #2093: 1: Success after binutils/gcc: 4 commits discards 22294e7bb7 450: onsuccess: #2092: 1: Success after binutils/gcc: 28 commits discards 221efe67c7 449: onsuccess: #2091: 1: Success after binutils/gcc: 29 commits discards dba0b09455 448: onsuccess: #2090: 1: Success after binutils/gcc: 28 commits discards 9c7a682954 447: onsuccess: #2089: 1: Success after binutils/gcc: 10 commits discards 3591220cb7 446: onsuccess: #2088: 1: Success after binutils/gcc: 6 commits discards 7af0ef6a2c 445: onsuccess: #2087: 1: Success after binutils/gcc: 15 commits discards 7e55802a2f 444: onsuccess: #2086: 1: Success after binutils/gcc: 12 commits discards a26ab881b8 443: onsuccess: #2085: 1: Success after binutils/gcc: 4 commits discards 551fade4f3 442: onsuccess: #2084: 1: Success after binutils/gcc: 12 commits discards d26556ec59 441: onsuccess: #2083: 1: Success after binutils/gcc: 38 commits discards 9e9d7de62b 440: onsuccess: #2082: 1: Success after binutils/gcc: 11 commits discards 2ba61a6f1d 439: onsuccess: #2081: 1: Success after binutils/gcc: 4 commits discards 28b7fc7435 438: onsuccess: #2080: 1: Success after gcc: 3 commits discards 918297f301 437: onsuccess: #2079: 1: Success after binutils/gcc: 4 commits discards 97320f2f07 436: onsuccess: #2078: 1: Success after binutils/gcc: 6 commits discards f07d53d983 435: onsuccess: #2077: 1: Success after gcc: 5 commits discards 54e340f801 434: onsuccess: #2076: 1: Success after binutils/gcc: 30 commits discards fb774b0a45 433: onsuccess: #2075: 1: Success after binutils/gcc: 16 commits discards fb8a20171d 432: onsuccess: #2074: 1: Success after binutils/gcc: 2 commits discards fcdad237e5 431: onsuccess: #2073: 1: Success after basepoints/gcc-13-47 [...] discards be403bee95 430: onsuccess: #2072: 1: Success after binutils/gcc: 3 commits discards 722da0d467 429: onsuccess: #2071: 1: Success after binutils/gcc: 5 commits discards 528daa3533 428: onsuccess: #2070: 1: Success after basepoints/gcc-13-47 [...] discards 8464665416 427: onsuccess: #2069: 1: Success after basepoints/gcc-13-47 [...] discards b3278a6227 426: onsuccess: #2068: 1: Success after binutils: 9 commits discards 2d61a76d81 425: onsuccess: #2067: 1: Success after binutils/gcc: 5 commits discards d99dd37093 424: onsuccess: #2066: 1: Success after gcc: 11 commits discards 95a20701d1 423: onsuccess: #2065: 1: Success after binutils/gcc: 21 commits discards a45462cc0f 422: onsuccess: #2063: 1: Success after binutils/gcc: 6 commits discards 967b71527d 421: onsuccess: #2062: 1: Success after binutils/gcc: 15 commits discards 22abb731b8 420: onsuccess: #2061: 1: Success after binutils/gcc: 13 commits discards d7f0821e5e 419: onsuccess: #2060: 1: Success after gcc: 3 commits discards c4a4aac3a1 418: onsuccess: #2059: 1: Success after binutils/gcc: 2 commits discards d1e91d0f9b 417: onsuccess: #2058: 1: Success after gcc: 7 commits discards 0f5e89d622 416: onsuccess: #2057: 1: Success after binutils/gcc: 17 commits discards c01ea8a06c 415: onsuccess: #2056: 1: Success after binutils/gcc: 10 commits discards aef1757e88 414: onsuccess: #2055: 1: Success after binutils/gcc: 12 commits discards baa54196b9 413: onsuccess: #2054: 1: Success after binutils/gcc: 10 commits discards 1781248209 412: onsuccess: #2053: 1: Success after binutils/gcc: 53 commits discards a403f09d12 411: onsuccess: #2052: 1: Success after binutils/gcc: 6 commits discards 528efdc020 410: onsuccess: #2051: 1: Success after binutils/gcc: 5 commits discards 6e50377672 409: onsuccess: #2050: 1: Success after binutils/gcc: 6 commits discards f9f6f87bbc 408: onsuccess: #2049: 1: Success after binutils/gcc: 26 commits discards 6a629d6dc3 407: onsuccess: #2048: 1: Success after binutils/gcc: 12 commits discards cbc290d23b 406: onsuccess: #2047: 1: Success after binutils/gcc: 2 commits discards 25cac970e2 405: onsuccess: #2046: 1: Success after gcc: 2 commits discards e709cc4990 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits discards 6b6cb5786e 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits discards 3847cd3287 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-45 [...] discards 2e97d2310b 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits discards dac1429f95 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits discards b7b4678339 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits discards ce440a9ed0 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits discards 955d21fc33 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits discards b1f48e56f8 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits discards 612213e4f9 395: onsuccess: #2035: 1: Success after gcc: 4 commits discards 60ffbd2000 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits discards 46f13a36ef 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits discards 8ddd268f9c 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits discards b9d6c38280 391: onsuccess: #2031: 1: Success after binutils/gcc: 5 commits discards ff64274ca0 390: onsuccess: #2030: 1: Success after binutils/gcc: 8 commits discards 107290b43d 389: onsuccess: #2029: 1: Success after binutils/gcc: 13 commits discards b991b6d1ca 388: onsuccess: #2028: 1: Success after binutils/gcc: 15 commits discards d9fdd5c48a 387: onsuccess: #2027: 1: Success after binutils/gcc: 14 commits discards ac0d439bc6 386: onsuccess: #2026: 1: Success after binutils/gcc: 5 commits discards 5c3bef5e90 385: onsuccess: #2025: 1: Success after binutils: 8 commits discards 42ebb20b19 384: onsuccess: #2024: 1: Success after binutils/gcc: 13 commits discards 62dfbc3c25 383: onsuccess: #2023: 1: Success after binutils/gcc: 7 commits discards 727a4f1f7c 382: onsuccess: #2022: 1: Success after binutils/gcc: 3 commits discards ee1d8e6a62 381: onsuccess: #2021: 1: Success after binutils/gcc: 6 commits discards 3e1b2e086e 380: onsuccess: #2020: 1: Success after gcc: 2 commits discards 328d094e04 379: onsuccess: #2019: 1: Success after gcc: 3 commits discards 88666936e8 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits discards 914eb4b0d7 377: onsuccess: #2017: 1: Success after binutils: 3 commits discards 3f7eac54fa 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-44 [...] discards 45dbad117a 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits discards 4339e21ae5 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits discards daed67776f 373: onsuccess: #2013: 1: Success after gcc: 6 commits discards bfaabcc6a9 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits discards 02a815fc2c 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits discards d637acd5f6 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits discards a281fa2a0d 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits discards 1c54f7b323 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits discards 272386f79a 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits new 369da3ae71 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits new 576e4f02b1 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits new ff3ae4f8da 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits new 1e5b7d3f35 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits new 8b1a0244c0 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits new f2c48de22e 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits new 4e1e8d936e 373: onsuccess: #2013: 1: Success after gcc: 6 commits new 36f8a8e62b 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits new 67e02d762b 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits new 54edfc5518 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-44 [...] new eb47ffa51c 377: onsuccess: #2017: 1: Success after binutils: 3 commits new 13bf650d2f 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits new feff5116fb 379: onsuccess: #2019: 1: Success after gcc: 3 commits new 73665d1bdc 380: onsuccess: #2020: 1: Success after gcc: 2 commits new eee0e277c4 381: onsuccess: #2021: 1: Success after binutils/gcc: 6 commits new 40f073d434 382: onsuccess: #2022: 1: Success after binutils/gcc: 3 commits new 81c1d41746 383: onsuccess: #2023: 1: Success after binutils/gcc: 7 commits new 20595dac88 384: onsuccess: #2024: 1: Success after binutils/gcc: 13 commits new e0f23d8d33 385: onsuccess: #2025: 1: Success after binutils: 8 commits new f7608098a4 386: onsuccess: #2026: 1: Success after binutils/gcc: 5 commits new 78929b0ee3 387: onsuccess: #2027: 1: Success after binutils/gcc: 14 commits new 6611297d81 388: onsuccess: #2028: 1: Success after binutils/gcc: 15 commits new a75ca2f955 389: onsuccess: #2029: 1: Success after binutils/gcc: 13 commits new a1e92dd210 390: onsuccess: #2030: 1: Success after binutils/gcc: 8 commits new 2e60c3a9ae 391: onsuccess: #2031: 1: Success after binutils/gcc: 5 commits new bbc33b5570 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits new 9cff455e82 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits new 5cdc3d28cf 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits new e22fed89cb 395: onsuccess: #2035: 1: Success after gcc: 4 commits new 0f7e113867 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits new 850f33bfba 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits new 115a990f8f 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits new cb0cc0402e 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits new 7e93eb526b 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits new 35b80a7119 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits new 8a768b3e69 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-45 [...] new bae863dfc9 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits new 238e190824 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits new f6a8c0140f 405: onsuccess: #2046: 1: Success after gcc: 2 commits new 2ba3b2a113 406: onsuccess: #2047: 1: Success after binutils/gcc: 2 commits new 1deaa35013 407: onsuccess: #2048: 1: Success after binutils/gcc: 12 commits new ef5e6b0a1d 408: onsuccess: #2049: 1: Success after binutils/gcc: 26 commits new 5694e90bc8 409: onsuccess: #2050: 1: Success after binutils/gcc: 6 commits new dcfdfdee3f 410: onsuccess: #2051: 1: Success after binutils/gcc: 5 commits new adac772bb9 411: onsuccess: #2052: 1: Success after binutils/gcc: 6 commits new e9df742e83 412: onsuccess: #2053: 1: Success after binutils/gcc: 53 commits new 0bf45178dd 413: onsuccess: #2054: 1: Success after binutils/gcc: 10 commits new 2796bfab32 414: onsuccess: #2055: 1: Success after binutils/gcc: 12 commits new a69d815184 415: onsuccess: #2056: 1: Success after binutils/gcc: 10 commits new abc4dc90bd 416: onsuccess: #2057: 1: Success after binutils/gcc: 17 commits new a1fc45e4f7 417: onsuccess: #2058: 1: Success after gcc: 7 commits new dbd44c16ab 418: onsuccess: #2059: 1: Success after binutils/gcc: 2 commits new b6704aa770 419: onsuccess: #2060: 1: Success after gcc: 3 commits new 348e0a888f 420: onsuccess: #2061: 1: Success after binutils/gcc: 13 commits new a9bea7d0b7 421: onsuccess: #2062: 1: Success after binutils/gcc: 15 commits new c2b31323ad 422: onsuccess: #2063: 1: Success after binutils/gcc: 6 commits new ade0da947d 423: onsuccess: #2065: 1: Success after binutils/gcc: 21 commits new 451e250b49 424: onsuccess: #2066: 1: Success after gcc: 11 commits new 76348008bd 425: onsuccess: #2067: 1: Success after binutils/gcc: 5 commits new cfb03a97ce 426: onsuccess: #2068: 1: Success after binutils: 9 commits new 52abe81b42 427: onsuccess: #2069: 1: Success after basepoints/gcc-13-47 [...] new f1a7cd8247 428: onsuccess: #2070: 1: Success after basepoints/gcc-13-47 [...] new 81bc7494b7 429: onsuccess: #2071: 1: Success after binutils/gcc: 5 commits new 7ce43682f1 430: onsuccess: #2072: 1: Success after binutils/gcc: 3 commits new 4ece3fd8c3 431: onsuccess: #2073: 1: Success after basepoints/gcc-13-47 [...] new c8bf2a612f 432: onsuccess: #2074: 1: Success after binutils/gcc: 2 commits new 66a3e62f0d 433: onsuccess: #2075: 1: Success after binutils/gcc: 16 commits new a568372e5b 434: onsuccess: #2076: 1: Success after binutils/gcc: 30 commits new c73779f6da 435: onsuccess: #2077: 1: Success after gcc: 5 commits new eb2bb5aaac 436: onsuccess: #2078: 1: Success after binutils/gcc: 6 commits new 87b3ec622d 437: onsuccess: #2079: 1: Success after binutils/gcc: 4 commits new cbfd2e47e8 438: onsuccess: #2080: 1: Success after gcc: 3 commits new 5f0df99997 439: onsuccess: #2081: 1: Success after binutils/gcc: 4 commits new f913d1a911 440: onsuccess: #2082: 1: Success after binutils/gcc: 11 commits new 2eca7a70aa 441: onsuccess: #2083: 1: Success after binutils/gcc: 38 commits new 5fedd1fbbc 442: onsuccess: #2084: 1: Success after binutils/gcc: 12 commits new e5fb7e73a4 443: onsuccess: #2085: 1: Success after binutils/gcc: 4 commits new e4b4987985 444: onsuccess: #2086: 1: Success after binutils/gcc: 12 commits new bd713d577f 445: onsuccess: #2087: 1: Success after binutils/gcc: 15 commits new 4a6e1328e2 446: onsuccess: #2088: 1: Success after binutils/gcc: 6 commits new 80641e20c2 447: onsuccess: #2089: 1: Success after binutils/gcc: 10 commits new 6cf57c7122 448: onsuccess: #2090: 1: Success after binutils/gcc: 28 commits new c3f4777564 449: onsuccess: #2091: 1: Success after binutils/gcc: 29 commits new a25e44644c 450: onsuccess: #2092: 1: Success after binutils/gcc: 28 commits new 343a0cfd79 451: onsuccess: #2093: 1: Success after binutils/gcc: 4 commits new 9d64c47132 452: onsuccess: #2094: 1: Success after binutils/gcc: 4 commits new e1610add85 453: onsuccess: #2095: 1: Success after gdb-13-branchpoint-1 [...] new bcc95cfd97 454: onsuccess: #2096: 1: Success after gcc: 4 commits new 2d61fa2df8 455: onsuccess: #2097: 1: Success after binutils/gcc: 11 commits new 696496e702 456: onsuccess: #2098: 1: Success after binutils: 10 commits new a86def4cc0 457: onsuccess: #2099: 1: Success after binutils/gcc: 2 commits new af4d0ebea6 458: onsuccess: #2100: 1: Success after gdb-13-branchpoint-1 [...] new 3c24d5fc1f 459: onsuccess: #2101: 1: Success after binutils/gcc: 3 commits new 48842a0abc 460: onsuccess: #2102: 1: Success after binutils: 2 commits new 0a41bab338 461: onsuccess: #2103: 1: Success after binutils/gcc: 2 commits new 7045bc0e9e 462: onsuccess: #2104: 1: Success after binutils/gcc: 2 commits new fb188cdaa6 463: onsuccess: #2105: 1: Success after binutils/gcc: 10 commits new 1cb334a682 464: onsuccess: #2106: 1: Success after gcc: 9 commits new bb41ebde87 465: onsuccess: #2107: 1: Success after binutils/gcc: 6 commits new 74f65b402a 466: onsuccess: #2108: 1: Success after binutils/gcc: 5 commits new 10c2fd3bf6 467: onsuccess: #2109: 1: Success after gcc: 2 commits new 0f6a0af0b6 468: onsuccess: #2110: 1: Success after gdb-13-branchpoint-2 [...] 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 (e75e5dc7ab) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (0f [...] 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 1764 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 53020 -> 53116 bytes 04-build_abe-gcc/console.log.xz | Bin 236928 -> 239796 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3852 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2468 -> 2464 bytes 07-check_regression/console.log.xz | Bin 4408 -> 4352 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 18 +- 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 2858260 -> 2853248 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2457772 -> 2454160 bytes sumfiles/gcc.sum | 4848 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 916556 -> 918308 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217232 -> 217324 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 479968 -> 476040 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2587 insertions(+), 2595 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-defconfig updated (405f9ca295 -> 20fa07385a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 405f9ca295 31: onsuccess: #416: boot: Success after binutils/gcc/linux/ [...] new 20fa07385a 32: onsuccess: #417: boot: Success after binutils/gcc/linux: [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30564 -> 30072 bytes 04-build_abe-stage1/console.log.xz | Bin 87664 -> 86844 bytes 05-build_abe-qemu/console.log.xz | Bin 31616 -> 31516 bytes 06-build_linux/console.log.xz | Bin 3140 -> 3032 bytes 07-boot_linux/console.log.xz | Bin 5688 -> 5652 bytes 08-check_regression/console.log.xz | Bin 4128 -> 3372 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page: