Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig updated (542ad05f97 -> 0bdbd80316)

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-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 542ad05f97 58: onsuccess: #14: 21863: [TCWG CI] Success after binutils/ [...] new 0bdbd80316 59: onsuccess: #15: 21863: [TCWG CI] Success after binutils/ [...] 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 2028 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 27388 -> 27228 bytes 04-build_abe-stage1/console.log.xz | Bin 71104 -> 71464 bytes 05-build_abe-qemu/console.log.xz | Bin 30892 -> 29704 bytes 06-build_linux/console.log.xz | Bin 8704 -> 8612 bytes 08-check_regression/console.log.xz | Bin 4368 -> 3780 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 15 files changed, 54 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (8cd97b9708 -> e820be74ae)

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-mainline-defconfig in repository toolchain/ci/base-artifacts. from 8cd97b9708 60: onsuccess: #10: boot: [TCWG CI] Success after binutils/g [...] new e820be74ae 61: onsuccess: #11: boot: [TCWG CI] Success 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 2000 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27132 -> 26864 bytes 04-build_abe-stage1/console.log.xz | Bin 88256 -> 89048 bytes 05-build_abe-qemu/console.log.xz | Bin 29336 -> 29632 bytes 06-build_linux/console.log.xz | Bin 5112 -> 4536 bytes 07-boot_linux/console.log.xz | Bin 5676 -> 5644 bytes 08-check_regression/console.log.xz | Bin 4120 -> 3720 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 16 files changed, 54 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-aarch64 updated (ec4bca0150 -> e065624e7a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from ec4bca0150 11: onsuccess: #16: 1: [TCWG CI] Success after binutils/gcc/ [...] new e065624e7a 12: onsuccess: #17: 1: [TCWG CI] Success after binutils/gcc/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2072 -> 2124 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 27316 -> 27044 bytes 04-build_abe-stage1/console.log.xz | Bin 71172 -> 71280 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8540 -> 8240 bytes 07-build_abe-glibc/console.log.xz | Bin 241576 -> 240452 bytes 08-build_abe-stage2/console.log.xz | Bin 201864 -> 201720 bytes 09-build_abe-gdb/console.log.xz | Bin 34664 -> 34588 bytes 10-build_abe-qemu/console.log.xz | Bin 31196 -> 30640 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3888 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2176 -> 2276 bytes 13-check_regression/console.log.xz | Bin 5128 -> 4552 bytes 13-check_regression/results.compare | 10 +++---- 13-check_regression/results.compare2 | 6 ++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 42 +++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 42 ++++++++++++++--------------- manifest.sh | 38 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62416 -> 62512 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150640 -> 150728 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 107652 -> 107604 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 74 insertions(+), 86 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig updated (10b07450ac -> a796cd7e7c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig in repository toolchain/ci/base-artifacts. from 10b07450ac 58: onsuccess: #10: boot: [TCWG CI] Success after binutils/l [...] new a796cd7e7c 59: onsuccess: #11: boot: [TCWG CI] Success after binutils/l [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2000 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 27468 -> 27284 bytes 04-build_kernel_llvm/console.log.xz | Bin 66152 -> 67480 bytes 05-build_abe-qemu/console.log.xz | Bin 30588 -> 31308 bytes 06-build_linux/console.log.xz | Bin 3412 -> 3488 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4208 -> 3332 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 38 ++++++++++++----------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++++--------------- manifest.sh | 24 +++++++++++----------- 16 files changed, 54 insertions(+), 57 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (90ec7263fe -> 71e6100893)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 90ec7263fe 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 914b5e3c9a 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 620bccfc50 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1178d8357a 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 1a75c99624 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a85ca36e2a 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards ebfdcdd190 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 98a17c7885 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c049afa818 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards aef850faac 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 86060fd064 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards a4ce4583b4 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards d39a7f3047 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 06a1174d66 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards d1db175f84 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 1d8fe57773 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards e10d29e306 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards a1f3e446a4 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 289fd6b0d8 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards f424103be8 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 6a49e93ad3 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 1c137b3976 212: force: #24: 1: Success after binutils: 2 commits discards dae6f9bded 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 81619fa4be 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 1de353322c 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 657c161504 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 916f1dbd5f 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 915acf9c81 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 7641532a4f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3f1db89adf 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 6ac569bf7d 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 3196df31a7 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 4121dfcbd8 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 87f27f6d47 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c9460be920 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards b1b28de358 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b9ad8ef3f7 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards edaabdfdb8 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 67759197ba 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 486d00f42b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 1fa3199a28 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 30931d2a19 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards d7801fe729 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7a1c906b1e 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards f7047f1d9d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards c9666b92c5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 566cbca8c7 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards eb339a619f 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 8a729988c8 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards ae349c5ac9 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards f42a4a2a2e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 4f15e40def 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 307c210a24 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 714e192a9d 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards e6f1fefe91 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 846a09ea0d 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 3de79818cc 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards d008efec04 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 0832197e14 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards a2138f06da 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards c7706734f4 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 8d3ca20b2e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards ee5f082d2d 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 08f5c78a36 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 24a499fc1b 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards edd025be49 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 7ffbc4ede9 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 9b49305df3 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 233bcfa617 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards b603c2d21d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 454e0302d5 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 13476910ea 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 81ef6a6ecb 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards a5948ebec8 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards bacaa21799 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 4c1b1dd084 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards ae9f1d3be9 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 01eef9638d 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 4db8d51ef3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 871b8311ef 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 02b428d7a2 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 7bd5bc0736 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards cc70a88255 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards aa5fc27cab 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards f5e6ed864d 149: onsuccess: #684: 1: Success after linux: 10 commits discards 923751ff20 148: onsuccess: #683: 1: Success after glibc: 9 commits discards d0f1a71f95 147: onsuccess: #681: 1: Success after gcc: 6 commits discards a4f731d57d 146: onsuccess: #680: 1: Success after binutils: 20 commits discards c96f1ee025 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards eca799afd4 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 71ed5866d5 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 1ff2571fb5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards fc852dda58 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards f5c2086b70 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 0d1e708844 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 948fcbd333 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 6fa480fbe8 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 01356c4dc9 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 50fe933616 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 54f081974a 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards e981a12a49 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new b4fe1a3630 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new a273cdd4ca 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 258830793a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 4ca7c133f9 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 03c2e78815 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 5c27634e5a 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new d26177f8ea 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 904461f0a6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 5026006869 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 17c510591c 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 047908f089 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 76c4628e80 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new d126ee297d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new e9cc97cd33 146: onsuccess: #680: 1: Success after binutils: 20 commits new eb5821b6c3 147: onsuccess: #681: 1: Success after gcc: 6 commits new afe064de43 148: onsuccess: #683: 1: Success after glibc: 9 commits new 6f025eded7 149: onsuccess: #684: 1: Success after linux: 10 commits new 7ba30ebbb8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 32f4f645fc 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new e012adbb91 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new fd94f10d8d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new fb1dd3785d 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 3922444950 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new f2db3a38f5 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 958a12c756 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new acdabc632e 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new ae4b55a761 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new c78e30963a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new add85d3e73 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 7ff1603441 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 2348da3e62 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new d12ff2ee7d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new cef6187cc7 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 177bf1aebf 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 36c8fd75ae 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new edbf9f6d15 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new d3aca0252e 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new abb3dbbbe7 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new aab7abb49d 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new c2e32796ff 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 5f21c74d6a 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 524646a565 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 7844f631d4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 2d2005ce69 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 37fc376a39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 1a47deca55 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 206bcd0faf 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 5cbee6e9f8 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new bbeac33a39 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new c344cbffce 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 57ed24eb30 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 9771d40812 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 3f114c0091 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 726a6bab5d 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 7609459d55 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 36cb9464d3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new a7ff15aa5d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 1737c54d9b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 16853e785a 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 554eb2d7fc 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new b31011f99c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 983e8ba0bf 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new e07e7072d0 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2670bf60dd 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new a3ad283aea 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new fd3452af6b 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f677eb1e28 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new bcd38e9926 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4e65e185e3 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 338345dda2 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new a1de534faf 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 567e87da45 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 222535023c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 30c667a8c7 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 81daf39637 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 7300c6649b 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 8279a8f572 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 1a1703f6e9 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 3c926352d3 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new fcac3ec321 212: force: #24: 1: Success after binutils: 2 commits new 92c3f12ddd 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 288728e749 214: onsuccess: #26: 1: Success after binutils: 12 commits new 60cbac2ed6 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 73a94fc0b0 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new b3c9f19106 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new fdad228d2d 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 75ac4895e6 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 4df74dbb8d 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a520c167d5 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 09ded43ca6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 1b038df1c2 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new b33e45053a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 9c481ffa82 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new d770a714f3 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 9ee92e712d 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new c14415c231 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 7e5e9bf38d 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new f84ef61dd9 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new c7d54d9605 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 021e47ca4d 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 229f26600a 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 71e6100893 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (90ec7263fe) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2072 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 34960 -> 35104 bytes 04-build_abe-gcc/console.log.xz | Bin 203668 -> 203348 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8456 -> 8280 bytes 07-build_abe-glibc/console.log.xz | Bin 240692 -> 240552 bytes 08-build_abe-gdb/console.log.xz | Bin 34640 -> 34704 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2148 -> 2300 bytes 11-check_regression/console.log.xz | Bin 4932 -> 4360 bytes 11-check_regression/results.compare | 10 +++---- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 42 ++++++++++----------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++++------------ manifest.sh | 32 ++++++++++----------- sumfiles/binutils.log.xz | Bin 63020 -> 63144 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150764 -> 150832 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122652 -> 122620 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 90 insertions(+), 102 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (4c4fe4b7d1 -> 1567cad330)

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 4c4fe4b7d1 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 8e14051e94 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 173759f924 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 8ae89a666f 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 12ff1f4900 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 63a92bb68d 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards f4e6a9b23b 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 26040ea0a1 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 7a7d766663 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 2b42bb4fd3 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 36231d2c7c 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 476134df18 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards e545482aad 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 06421462fa 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d2e0b01c74 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c32c545283 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 86ca54db7e 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards c1f4bf14c1 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards b2d72dc373 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards e953841f85 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards f29ad9591f 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 3042a11c7e 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 4b0d5f684f 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards fe15c98b8f 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards b095b961c9 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 4a60ce0b39 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards 4654609638 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards b165b8e91d 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 2b42ae9ca2 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards da3cc2050a 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards c2eb61abd5 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 5f9b103e94 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 899ac77f1a 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards b0a2e9604d 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 7ed24cb787 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards d92e5f0164 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards fd3f1b0c08 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 07a3d7db0c 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 4cb5b63875 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards e15022e060 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 65594fe163 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e9dd623383 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 7dccc98849 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 67fce5ad6d 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 677c939cb4 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards c320cb0127 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 0b71829a68 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 0092887c23 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards f7c22e071b 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 273a352f63 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards c56df392ce 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 934e059105 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 4a709e2708 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards a66d52c697 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 3dcae20172 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 5e85381c00 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 5c9497a3c3 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 849db024f1 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards cd2e54b485 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 487b180fa9 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 3cf532b8d8 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards a77892d7a7 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards d0898c2e45 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 5e3a138a22 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 4070819eee 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 5b6fd680a8 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 2386134258 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 579bdfdf75 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 3d763c8a5c 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards d75464a794 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 148122245e 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 2629d11920 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 9faf78542b 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 87c0742af4 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 0917ccdd2c 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 9a107b6485 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards f6c7607e89 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards db00e3f40c 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards bdfdc2bb61 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards b49d26fba5 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 724af9674d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards cc414fd02d 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 40af7385e7 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards b750ea0e6e 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 960bf04213 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 0ece222e04 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 4226e4c160 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 3a2080b83c 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 46eefa95c5 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 5c029b732e 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards de37c91bc8 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 6944cce0f9 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 3cbed7e0fe 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards a5e460bce4 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 764ef92885 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards f054adefbe 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 11a0b05013 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 833e48149b 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 2fdb1e0c83 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 263662c69d 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 794166978c 387: onsuccess: #2208: 1: Success after gcc: 2 commits new e70fc75f69 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 593997d6a5 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 655c0eadb5 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new b40f06ba33 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 0979ab4754 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 0308dde4f9 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new efc2dad03a 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new c6a343a9c5 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 54ecc311a2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 534000458a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new adf5946b59 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new d457a1f3c9 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new dc54aca077 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 4b84970f6a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d5935deec5 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 12fc485008 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 2bf7848e81 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 3d54c85195 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 72beff255b 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 8ab12d66d4 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new a4129391b7 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new cb56f3ad8d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 4202e87b50 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 596b6f1d64 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new c513d3b82f 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 0f6b2706e7 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 8aa536187f 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new b566543b3a 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new ff868585c1 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 3e0ec7a9bd 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new cef6e124c0 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new c9bacbf436 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 518c5840ed 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 50d767faa1 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 9a71808192 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 19cd800b45 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new d70ad2a2fe 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new e148910e24 424: onsuccess: #2248: 1: Success after gcc: 6 commits new d79b1973bc 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 806b13fefc 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 4f60212634 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 6b883d64e5 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 9d3e94fde8 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 607e178482 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new a969c2db61 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 799b749096 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 080425564b 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 3f5c79c7df 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new e9b3521a44 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 5e41dd9374 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 6ccbed95bc 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 7b4ee7b4bf 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 19bf70ee2e 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 57b9cae25c 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 9aa9b64632 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 9530d747d2 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new de9438ca9b 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 04104181ba 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new c347fdc1c6 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new ee255a07d4 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new f10cc3b68c 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a774bb38ea 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 22399d796f 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new e04d4e7510 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 8f33a0608c 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8ee0d2908d 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 4432be9c1c 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 55dd20c90a 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 7c07889550 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 697cde250c 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 3c489aa906 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 894b345ae9 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 30770d3e0b 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 874e388cb4 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 027faa32b2 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new c8aa08395f 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new 51f4e5adaa 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new a022114bd3 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new ada8f7279a 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 54d3638504 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new c38ec1da93 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9c3dadae4a 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 0d2ff7968f 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 52da1d0fa0 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new bf1d5397ca 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 98b74ccbf4 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 46aa82c86f 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 9357af3119 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 4022becb08 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 3e33526b80 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new a872db79f7 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new cfd84c2549 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 81076bb1b1 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 1e80fee5f4 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 5ebc59350a 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 677def1ffd 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new b3b66048eb 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new eb5a93f710 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d8341f13ef 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 7cea1d13fc 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new d96019a3f8 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 1567cad330 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (4c4fe4b7d1) \ 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 2084 -> 2136 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 26820 -> 26600 bytes 04-build_abe-stage1/console.log.xz | Bin 88836 -> 89164 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8284 bytes 07-build_abe-glibc/console.log.xz | Bin 232460 -> 232604 bytes 08-build_abe-stage2/console.log.xz | Bin 224988 -> 224936 bytes 09-build_abe-gdb/console.log.xz | Bin 33980 -> 33988 bytes 10-build_abe-qemu/console.log.xz | Bin 29496 -> 30392 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6920 -> 6816 bytes 13-check_regression/console.log.xz | Bin 6364 -> 5088 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 92 +- 13-check_regression/results.regressions | 26 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 40 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 42 +- manifest.sh | 38 +- results | 26 +- sumfiles/g++.log.sep.xz | Bin 137460 -> 146400 bytes sumfiles/g++.log.xz | Bin 2685932 -> 2683960 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 628 +-- sumfiles/gcc.log.sep.xz | Bin 108048 -> 143864 bytes sumfiles/gcc.log.xz | Bin 2217640 -> 2203344 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 8671 ++++++++++--------------------- sumfiles/gfortran.log.sep.xz | Bin 62316 -> 40980 bytes sumfiles/gfortran.log.xz | Bin 903428 -> 903664 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 4860 +++++++++-------- sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217536 -> 217344 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 15472 -> 10732 bytes sumfiles/libstdc++.log.xz | Bin 446260 -> 448552 bytes sumfiles/libstdc++.sum.sep | 511 +- 49 files changed, 5931 insertions(+), 9131 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[binutils-gdb] branch master updated (35aa3404bf7 -> 5f777caeebf)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 35aa3404bf7 Automatic date update in version.in new 5f777caeebf x86: Add inval tests for AMX instructions 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: gas/testsuite/gas/i386/i386.exp | 2 ++ gas/testsuite/gas/i386/x86-64-amx-complex-inval.l | 7 +++++++ gas/testsuite/gas/i386/x86-64-amx-complex-inval.s | 12 ++++++++++++ gas/testsuite/gas/i386/x86-64-amx-fp16-inval.l | 7 +++++++ gas/testsuite/gas/i386/x86-64-amx-fp16-inval.s | 12 ++++++++++++ gas/testsuite/gas/i386/x86-64-amx-inval.l | 22 ++++++++++++++-------- gas/testsuite/gas/i386/x86-64-amx-inval.s | 6 ++++++ 7 files changed, 60 insertions(+), 8 deletions(-) create mode 100644 gas/testsuite/gas/i386/x86-64-amx-complex-inval.l create mode 100644 gas/testsuite/gas/i386/x86-64-amx-complex-inval.s create mode 100644 gas/testsuite/gas/i386/x86-64-amx-fp16-inval.l create mode 100644 gas/testsuite/gas/i386/x86-64-amx-fp16-inval.s -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (7575dce04c -> 2774d5b4c0)

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 7575dce04c 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] discards 83caeff0b6 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] discards de59e39642 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits discards 9489db0f23 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 6009100f97 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards 2ebeae90e5 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards b4ac709cbe 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards 14225c79ba 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards d2f2512504 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 6ea5deb984 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards 989c24a5c1 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards 5e46543079 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 24569267aa 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards 81727e93ac 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards d263430122 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards cdc6b129da 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards ecc7b55f71 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards 98067250c2 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards f3cc13dcc7 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 05ec9762a3 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards dde292df9f 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards f9c0ae6636 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 394b5be2a1 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 8864e1fa26 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards afcb343e62 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 62e414eaf1 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 169179b4e4 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 441819db45 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 125265290d 228: force: #74: 1: Success after gdb: 53 commits discards b1d237af11 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 004588b093 226: force: #70: 1: Success after baseline build: no new commits discards f24c6bfaa9 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 186a7319ff 224: force: #65: 1: Success after gdb: 50 commits discards 752d4dc0c5 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 38e7c408b8 222: force: #60: 1: Success after gdb: 16 commits discards 5f47d0b7d1 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards e15ff92d3c 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 3a4a89be0e 219: force: #50: 1: Failure after linux: 2520 commits discards c8b8d23645 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards 7139fe1b4c 217: force: #45: 1: Success after linux: 1 commits discards a23d0bb406 216: force: #43: : Failure after baseline build: no new commits discards 5c7f94bd28 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 5eefdc5fd4 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 37e19602a0 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards c667c9e44b 212: force: #27: : Failure after baseline build: no new commits discards 81323625c2 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards bcea8d3e1e 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 33e0922174 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards fe8ba18cbb 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 38aaa6922d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 90ef8bb0a7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 1a3ac503d4 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 99dece041f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 856f935182 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards a029b66e36 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f1e58fb847 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 589b561333 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 27c07122d4 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards decb19ff34 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 206cd1b65c 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 994f72a507 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards eccf8f2f1b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards c7c0ec2e25 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 6a7a3fa9b7 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards c0a9554b4c 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards c8f61a061c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 24966be147 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards eba6940ca5 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards a7d1b0511d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards ef06996b50 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 492abec33f 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 90edc2a51f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 142bc16f2e 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards fb6d248577 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 0fe66cf5be 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards bca6c17f72 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards a9369c4b59 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 1bdcf91d46 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 68a0711d48 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards a17108e1cd 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 0d1583115f 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 81d70691e3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 385bda94b4 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 5a977960b1 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 707df07bf6 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 7d6e1d391f 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 8dff93e914 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 1a79cfc953 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 5b7b1d9687 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 1f6064d048 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 69c951ca0a 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 0cb4866ad8 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 28e982f466 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 221c0852e6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards d5f4bd6044 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 9aab2b2175 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 0321fb3ffa 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards f921e3d5cf 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards fe2b618802 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 249ede75dc 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 65cae27bd1 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 8801e12e25 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new b5094e8175 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new c3ec1cb5c1 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 23eba1a720 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 32359fba0e 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 8c384e418e 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new c89b74a019 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 9738293d83 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 02eb6a1592 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new c3f4a1854f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 1fcfbe3d66 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 486e48a0cb 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new de505266b4 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new a06524a75c 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 0150b2f5b4 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 4a6bc7742c 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 8d86229196 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 2c9ef803f6 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 527dd11c49 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new f52445bfe4 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new e06663edf0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 0a5c5e3325 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new be9d22d642 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 38726e94d2 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 2f70352f9d 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 680e5e9f48 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 791c18f292 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 4959e3f850 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new af52a37ed9 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new a575921ab6 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new acc41baff4 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 5d366837cb 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 4fea092234 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new a1d90ab8cf 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new b270f2497f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new b3d66143b6 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 0548c3d487 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 74c0e2962d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 9ba7bbdd19 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 6877ea1afb 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 9e4ffe4db6 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new c6ca7ac108 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new db684bcafe 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 67c4eb72da 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 5f25f99884 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b3c9b717f5 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new f6c509c22c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new bdec50bbbe 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new a06ac98d97 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 74971c1ab3 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new b76c4646c8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new dcd227071a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new c6452b3ebe 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9e15d67a69 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new c98d9d4b6c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 77ce1ca781 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 8b69c26355 212: force: #27: : Failure after baseline build: no new commits new 22acc897e5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new ac07ad27a9 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 7e669bb5d9 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new a5b25ee464 216: force: #43: : Failure after baseline build: no new commits new 9b3f448bdb 217: force: #45: 1: Success after linux: 1 commits new 797c15238d 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 8229d3eb29 219: force: #50: 1: Failure after linux: 2520 commits new 3057090230 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new ba1343ad9d 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new e5fce4325f 222: force: #60: 1: Success after gdb: 16 commits new 887bf201b2 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new f0518c9e88 224: force: #65: 1: Success after gdb: 50 commits new c7ddd7d67d 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 6206df6a5a 226: force: #70: 1: Success after baseline build: no new commits new a89703dec0 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 229a5800b7 228: force: #74: 1: Success after gdb: 53 commits new 45a86ab149 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new b467f56b2f 230: onsuccess: #78: 1: Success after gdb: 2 commits new 70654972d0 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new e4c8e9d213 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 4a83c3f829 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 31846c78a9 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 1bad7f7a64 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 6f1aa0755b 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 3e51036d6b 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 7e367451e9 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 45e6cf4737 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 8b6c1cbd61 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new bcd3ac6b56 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new f59b1b21ca 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 2a51df7cd7 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 47f0cfa9c5 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 377191333e 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new 20fabfd72c 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 6753ab2b79 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new 999d8cf829 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new ceb996129f 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 4f37edca32 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 6ef9b5de62 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new 7a67f87632 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 32050fe2ad 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new bc338448d2 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits new 97dd3c767a 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] new e1e5ce4004 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] new 2774d5b4c0 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] 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 (7575dce04c) \ 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 2108 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49092 -> 49076 bytes 04-build_abe-gcc/console.log.xz | Bin 235424 -> 235088 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8488 -> 8264 bytes 07-build_abe-glibc/console.log.xz | Bin 235044 -> 232168 bytes 08-build_abe-gdb/console.log.xz | Bin 47580 -> 46480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4656 -> 4580 bytes 11-check_regression/console.log.xz | Bin 11992 -> 10992 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 123 +- 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 41 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 35 +- manifest.sh | 32 +- sumfiles/gdb.log.0.xz | Bin 2854328 -> 2883892 bytes sumfiles/gdb.log.1.xz | Bin 165396 -> 143016 bytes sumfiles/gdb.log.10.xz | Bin 10104 -> 9908 bytes sumfiles/gdb.log.11.xz | Bin 10120 -> 10212 bytes sumfiles/gdb.log.12.xz | Bin 9928 -> 10044 bytes sumfiles/gdb.log.13.xz | Bin 9800 -> 9816 bytes sumfiles/gdb.log.14.xz | Bin 9920 -> 0 bytes sumfiles/gdb.log.15.xz | Bin 9956 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 58880 -> 19608 bytes sumfiles/gdb.log.3.xz | Bin 14536 -> 14476 bytes sumfiles/gdb.log.4.xz | Bin 14432 -> 9928 bytes sumfiles/gdb.log.5.xz | Bin 10124 -> 9872 bytes sumfiles/gdb.log.6.xz | Bin 10152 -> 9884 bytes sumfiles/gdb.log.7.xz | Bin 10112 -> 10040 bytes sumfiles/gdb.log.8.xz | Bin 10152 -> 10200 bytes sumfiles/gdb.log.9.xz | Bin 10148 -> 10152 bytes sumfiles/gdb.sum | 3653 ++++++++++++++- sumfiles/gdb.sum.0 | 3667 ++++++++++++++- sumfiles/gdb.sum.1 | 4758 +------------------ sumfiles/gdb.sum.10 | 24 +- sumfiles/gdb.sum.11 | 27 +- sumfiles/gdb.sum.12 | 41 +- sumfiles/gdb.sum.13 | 18 +- sumfiles/gdb.sum.14 | 2173 --------- sumfiles/gdb.sum.15 | 2189 --------- sumfiles/gdb.sum.2 | 8190 +-------------------------------- sumfiles/gdb.sum.3 | 42 +- sumfiles/gdb.sum.4 | 252 +- sumfiles/gdb.sum.5 | 37 +- sumfiles/gdb.sum.6 | 69 +- sumfiles/gdb.sum.7 | 38 +- sumfiles/gdb.sum.8 | 84 +- sumfiles/gdb.sum.9 | 52 +- 56 files changed, 7802 insertions(+), 17801 deletions(-) delete mode 100644 sumfiles/gdb.log.14.xz delete mode 100644 sumfiles/gdb.log.15.xz delete mode 100644 sumfiles/gdb.sum.14 delete mode 100644 sumfiles/gdb.sum.15 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig updated (da7c699f1a -> 60f50d69d8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from da7c699f1a 57: onsuccess: #10: boot: [TCWG CI] Success after binutils/l [...] new 60f50d69d8 58: onsuccess: #11: boot: [TCWG CI] Success after binutils/l [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2024 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27572 -> 26916 bytes 04-build_kernel_llvm/console.log.xz | Bin 67208 -> 65608 bytes 05-build_abe-qemu/console.log.xz | Bin 31172 -> 29848 bytes 06-build_linux/console.log.xz | Bin 2928 -> 2916 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3776 -> 3312 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 ++++++++++++++-------------- manifest.sh | 24 ++++++++++++------------ 16 files changed, 43 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_woa_build/master-woa64 updated (07a5f99856 -> 001a22be4e)

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_woa_build/master-woa64 in repository toolchain/ci/base-artifacts. from 07a5f99856 15: onsuccess: #19: 1: [TCWG CI] Success after binutils: 5 commits new 001a22be4e 16: onsuccess: #20: 1: [TCWG CI] Success after gdb-13-branch [...] 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 1872 -> 1844 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2504 bytes 04-build_abe-binutils/console.log.xz | Bin 24580 -> 24636 bytes 05-check_regression/console.log.xz | Bin 2356 -> 2160 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/changes-list-long.txt | 10 ++++------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 12 ++++++------ manifest.sh | 12 ++++++------ 10 files changed, 19 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023