Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[binutils-gdb] branch master updated (0961e631575 -> 6752dd75f76)

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 0961e631575 PR30217, dynamic relocations using local dynamic symbols new 3e8b13bf774 cpu/mem.opc whitespace tidy new 6752dd75f76 Re: Add --enable-linker-verssion The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: cpu/mep.opc | 117 ++++++++++++++++----------------- ld/scripttempl/arclinux.sc | 5 +- ld/scripttempl/avr.sc | 4 +- ld/scripttempl/dlx.sc | 5 +- ld/scripttempl/elf.sc | 5 +- ld/scripttempl/elf32cr16.sc | 4 +- ld/scripttempl/elf32crx.sc | 4 +- ld/scripttempl/elf32msp430.sc | 4 +- ld/scripttempl/elf64bpf.sc | 2 +- ld/scripttempl/elf64hppa.sc | 4 +- ld/scripttempl/elf_chaos.sc | 4 +- ld/scripttempl/elfarc.sc | 4 +- ld/scripttempl/elfarcv2.sc | 4 +- ld/scripttempl/elfd10v.sc | 4 +- ld/scripttempl/elfd30v.sc | 4 +- ld/scripttempl/elfm68hc11.sc | 4 +- ld/scripttempl/elfm68hc12.sc | 4 +- ld/scripttempl/elfm9s12z.sc | 4 +- ld/scripttempl/elfmicroblaze.sc | 4 +- ld/scripttempl/elfxgate.sc | 4 +- ld/scripttempl/elfxtensa.sc | 5 +- ld/scripttempl/epiphany_4x4.sc | 5 +- ld/scripttempl/ft32.sc | 13 ++-- ld/scripttempl/i386beos.sc | 2 +- ld/scripttempl/i386go32.sc | 2 +- ld/scripttempl/ia64vms.sc | 2 +- ld/scripttempl/ip2k.sc | 5 +- ld/scripttempl/iq2000.sc | 5 +- ld/scripttempl/mep.sc | 5 +- ld/scripttempl/misc-sections.sc | 2 +- ld/scripttempl/mmo.sc | 2 +- ld/scripttempl/nds32elf.sc | 5 +- ld/scripttempl/pru.sc | 5 +- ld/scripttempl/v850.sc | 5 +- ld/scripttempl/v850_rh850.sc | 5 +- ld/scripttempl/visium.sc | 2 +- ld/scripttempl/xstormy16.sc | 5 +- ld/scripttempl/z80.sc | 4 +- ld/testsuite/ld-scripts/ld-version-2.d | 1 - opcodes/mep-asm.c | 9 ++- opcodes/mep-dis.c | 38 +++++------ 41 files changed, 151 insertions(+), 170 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (3033b7a4da2 -> 1c60231cba7)

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-arm in repository toolchain/ci/base-artifacts. discards 3033b7a4da2 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards a52b148ebf3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c8ff8dd2042 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards d83d260efc4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 2b3d4a97b77 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 8d6969ed639 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 3551736db70 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6b5ee3a4a87 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 56e46a7f88a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bb6eb6add36 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 41418ede423 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b0a1df2f1ba 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f39a61d3096 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards ad23f629d0b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 282e2acb3a2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4a2eeea1a51 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 09e1bb29e66 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards f3f95708344 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 92e85a20a8a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards cb15f070be9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7a789b69ad1 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 887fe6b5a47 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 606db981805 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 8003c0d3ab7 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards c6126b88e5b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 84967e6908c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards b3b0881790a 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 5a7b527a899 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 49d299b3fa3 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6fef78f33b6 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 9f7be33e91f 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards ef886800974 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 3d9e7c16910 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 7884ea906d0 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 1f254cf1c61 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards c04d8cf4e84 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 184d91310d0 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 2196926849e 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 71297c27e6a 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards b984d1beeb2 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 4ce6a5aebab 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards ebfd56be6e7 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 13483a2f873 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 6233dd9f904 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 3814437d93f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 8e37b95392d 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards dba49c2ad54 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 20fd5c5782d 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 985940c6b8b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 094349b7a1e 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2f0b135ed2e 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 22ff44fb8ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d9a288cd11c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 31c3272894c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 6c5d88969eb 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards a076c633f89 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards ebf9d25a52b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards b4231f96d32 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards cfc88aa2256 154: onsuccess: #583: 1: Success after linux: 10 commits discards cbe9470b8c8 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 527eff037df 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 6aed906c9d9 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 3ac7b0a8293 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 3375d1e5bba 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 5d26d6f88e7 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 383f671eb9c 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 22bbb0bb99d 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 09573350125 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards bfec93d055c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards c0b87c427ca 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards e6f53f0bb91 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 7ceb03134b1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards c19423e63b1 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 1fa8c1498ee 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 90105eb3303 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 71902a4b010 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 43fbffe132a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards abbd5c07204 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 0c53571467f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards a6298667fba 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards fc3c5f67e86 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 7f67fb7b83c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards b0c5d86f2e9 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 5b8aefbd940 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 5e65e299f40 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 43afb9943cf 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 4f0686b365d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards d9169882284 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 556b50e025f 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 9fd28d0c51f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards ea269161cde 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 1d4bdd085d2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 63b04672f7f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards a34c52561a8 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 5525963c3ff 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 05d62926687 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards d0247bffe33 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 1e16a001eb9 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards fefaa054c3c 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 58e113dc178 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 1b62ff39cc5 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 3ab6a2733fd 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new a60a59c2e4b 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 31dbe5e92a2 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 456e3c5858e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 59ba16ed939 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 9df08219cb4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 244da427af4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 570ed5ac484 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 7620d4a1e37 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 101442b6358 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 1c410ac3c33 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new fa1474f204d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new c0f4e2e8b56 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 9f5cc4edc2f 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 5344a87c34d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 16a23d4c386 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new e0bb0abdf06 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 55f291dfdf8 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new d2c057dff0b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new e95df942bc4 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 77d1d168424 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 0243dcaa98f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new b0ebc669ecc 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 0ab9cddb219 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 006298c86ac 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new a1bb92b4b7e 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 0c7622ce489 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new d8b987f265c 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 84531b51c58 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 22cd64ba22c 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 477469588bf 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 736a0c6a347 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 90ff893db34 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new f5623edff3d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 0df7f27e42f 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 309d79396ce 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 4fdeb620ce6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 36bf3d07048 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new cdd239c2758 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 824a37cdde6 151: onsuccess: #579: 1: Success after binutils: 21 commits new 3465f4f1efc 152: onsuccess: #580: 1: Success after gcc: 6 commits new bc4fb832b26 153: onsuccess: #582: 1: Success after glibc: 9 commits new e561fe471fa 154: onsuccess: #583: 1: Success after linux: 10 commits new 9864bf4ddaa 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new ae879913a68 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 6293bc36ecc 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 75b9abb2a0e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 0bcde9bef5c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 39d0a5f354f 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new fa1c1e13cdf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new dc92098b11f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 5b249d7b0f3 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 973582ae8c1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 3f24fed0aa0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 82277251756 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new f119b31eaa6 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 981c3ce6f4a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 842de85df1e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new dd84a694a8e 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 29664a9cd55 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 9c00a31a50a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 4948a62836c 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 7146d1b147e 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 530d2fefee9 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 5c37a259756 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new bc396fbf7e7 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 7e9f1265c05 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5b9ecdfbfb4 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 82199722aaf 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 8caf9aadb79 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 68cd9ae5641 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 6660bfe9597 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new eedab659d51 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new ea1e80e2085 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 06db2aa8a05 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new ecf970bb80c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 4fb640db543 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 7a7366b5ca0 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 54631dfd82b 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 556d5ff6377 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 59aef198d7c 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new b090748e5fa 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 668984a803d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 72ef2d065e0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 103cd9f39df 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new de4c7a24815 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 86475f0715b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 41017edf370 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f2ea457fa3d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 43445161685 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 43f43cbbd8c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b2cf729781a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new be1da56c667 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 2bd2f54619a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 30f54119510 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new f89081a832b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9fdb5af572e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9d4297cbd4b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3c774a45276 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 829a1ad714a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ce0915780b1 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 1c60231cba7 213: force: #24: 1: Success after binutils: 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 (3033b7a4da2) \ 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 1912 -> 1944 bytes 02-prepare_abe/console.log.xz | Bin 3428 -> 3440 bytes 03-build_abe-binutils/console.log.xz | Bin 52324 -> 52632 bytes 04-build_abe-gcc/console.log.xz | Bin 238472 -> 236672 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 235712 -> 235404 bytes 08-build_abe-gdb/console.log.xz | Bin 50212 -> 50456 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2116 -> 2196 bytes 11-check_regression/console.log.xz | Bin 4484 -> 3156 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 45 +--- 12-update_baseline/console.log | 40 ++-- 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 | 20 +- sumfiles/binutils.log.xz | Bin 62652 -> 62720 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100592 -> 100656 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 132072 -> 132024 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 26 files changed, 378 insertions(+), 423 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-arm-master-O3_LTO updated (0a101cec339 -> a55dbd6529d)

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-code_vect-spec2k6/gnu-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 0a101cec339 3: onsuccess: #4: 1: [TCWG CI] No change after binutils/gcc [...] new a55dbd6529d 4: onsuccess: #5: 1: [TCWG CI] No change 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 1816 -> 1852 bytes 02-prepare_abe/console.log.xz | Bin 2860 -> 3464 bytes 03-build_abe-binutils/console.log.xz | Bin 30732 -> 31176 bytes 04-build_abe-stage1/console.log.xz | Bin 89696 -> 90032 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 235928 -> 236344 bytes 08-build_abe-stage2/console.log.xz | Bin 210116 -> 210584 bytes 09-benchmark/benchmark-build.log | 110 +- 09-benchmark/benchmark.log | 108 +- 09-benchmark/console.log.xz | Bin 4136 -> 4124 bytes .../compare-results-vs-first-internal.csv | 78 +- .../compare-results-vs-prev-internal.csv | 80 +- 10-check_regression/console.log.xz | Bin 8112 -> 9844 bytes .../csv-results-vs-first-1/perf.csv | 153 +- .../csv-results-vs-first-1/results.csv | 8702 +- .../csv-results-vs-first-1/size.csv | 431679 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 5522 +- .../csv-results-vs-first-1/vect.csv | 195 + 10-check_regression/csv-results-vs-prev-0/perf.csv | 145 +- .../csv-results-vs-prev-0/results.csv | 8607 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 8501 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 153 +- .../csv-results-vs-prev-1/results.csv | 8702 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 431679 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 5522 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 195 + .../output-bmk-results/error_code-1 | 0 .../output-bmk-results/exe.regression | 5 + .../output-bmk-results/exe.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 73 +- 10-check_regression/results-vs-first-full.csv | 155 +- 10-check_regression/results-vs-first-internal.csv | 85 +- 10-check_regression/results-vs-first.csv | 85 +- 10-check_regression/results-vs-first.log | 1116 +- 10-check_regression/results-vs-prev-brief.csv | 73 +- 10-check_regression/results-vs-prev-full.csv | 171 +- 10-check_regression/results-vs-prev-internal.csv | 87 +- 10-check_regression/results-vs-prev.csv | 87 +- 10-check_regression/results-vs-prev.log | 1126 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../400.perlbench/results-metrics.json | 5 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 5 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 5 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/416.gamess/results-metrics.json | 3 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 5 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 3 +- .../436.cactusADM/results-metadata.json | 16 +- .../436.cactusADM/results-metrics.json | 5 +- .../437.leslie3d/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 3 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 5 +- .../450.soplex/results-metadata.json | 16 +- .../squad-vs-first/450.soplex/results-metrics.json | 5 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 16 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 421 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 45 +- mail/mail-body.txt | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 105 files changed, 454074 insertions(+), 460220 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/error_code-1 create mode 100644 10-check_regression/output-bmk-results/exe.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-defconfig updated (14b43f29627 -> 61f46024ccf)

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-stable-defconfig in repository toolchain/ci/base-artifacts. from 14b43f29627 57: onsuccess: #5: boot: Success after binutils/gcc/linux/q [...] new 61f46024ccf 58: onsuccess: #6: boot: Success after binutils/gcc/linux/q [...] 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 1748 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 3472 bytes 03-build_abe-binutils/console.log.xz | Bin 30524 -> 31092 bytes 04-build_abe-stage1/console.log.xz | Bin 89576 -> 89820 bytes 05-build_abe-qemu/console.log.xz | Bin 30928 -> 30876 bytes 06-build_linux/console.log.xz | Bin 5448 -> 5464 bytes 07-boot_linux/console.log.xz | Bin 5652 -> 5652 bytes 08-check_regression/console.log.xz | Bin 4184 -> 4264 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (b83339e1efc -> 3033b7a4da2)

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-arm in repository toolchain/ci/base-artifacts. discards b83339e1efc 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ac6feebb5cb 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e0d0fb82dee 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards af974603bcb 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 484a53b59db 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 711092558c7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 3684b54a2e0 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards de0515a80c0 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 639ef25b454 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 13faf9367b3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2ba09f57ba7 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5b52181cc1a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b62b4518d5d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6bf46f1b51a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 41fcc47a135 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 67102708492 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4f55654235b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6cdb045c2d3 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards f580b61b28e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 95b5544fe45 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards c0935b453f8 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 51e66971cff 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards c4cc894de1e 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 554c69f5b75 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards beaadebf45e 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards ed4895fc79a 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards c5f7490c85a 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards a69b1b21868 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6fa3d2cf058 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 54f3297ea86 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 0a7880eda4a 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 824c7d37a8e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e475477404f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards e366eff3286 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards fe913889333 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c9fb755f1b5 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards a8daac184b6 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 423e718e4e1 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 6bb12fbf4b5 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 1923330d5e8 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 21cd2c5052b 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 260abba1ce4 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 7beb3950104 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards bdbddc0fb4a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b75a4865949 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards b8d91b43ea3 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 6aab03e3543 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0a772a45109 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards f7f99a88cb7 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 36e96c80d43 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 81b1bd3f1ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d0eb2a991a8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 393ff07bfa2 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 1d05132bc8e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards ec752e28ccc 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 6647cffc944 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 423178a5ef6 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 1a06ee76d52 154: onsuccess: #583: 1: Success after linux: 10 commits discards dd5a4e2c27d 153: onsuccess: #582: 1: Success after glibc: 9 commits discards e7ac80a849d 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 841709c0024 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 302e8f7295f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 6085f58353a 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 51953e2822e 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards e7f7a563c7e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 7581c1fb6c4 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 99519f91341 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 6ea3d580e6f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 83fb5fb56a5 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards d2fde46a9fe 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 6972f25f88a 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 36373c1f787 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 94de2fcf5a7 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 32b1c1970ed 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 49f435da185 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 4bcbb10524a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 378553bab6d 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards cb2163c894b 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards b59eb2319da 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 21d280f23e9 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards ee124894a16 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 184baf4a229 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards aa8c34a24fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 67735d10990 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 4642cda4545 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards a23488d319a 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 552c185c9e9 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards ac2f0b625f0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards be1c2f93797 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards cd9e9f4a2b2 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 24bae56fe7f 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 9558fd7191b 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 1384257d929 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 3541e9fb444 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 7d28851f911 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 0cd31e43a96 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards c1f409fe98b 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 9be94802ca5 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards dfa1f700a51 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards da2ad8ac19a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 48007a3c94a 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 2f1775851a4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 1b62ff39cc5 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 58e113dc178 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new fefaa054c3c 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 1e16a001eb9 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new d0247bffe33 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 05d62926687 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 5525963c3ff 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new a34c52561a8 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 63b04672f7f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 1d4bdd085d2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new ea269161cde 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 9fd28d0c51f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 556b50e025f 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new d9169882284 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 4f0686b365d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 43afb9943cf 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 5e65e299f40 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 5b8aefbd940 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new b0c5d86f2e9 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 7f67fb7b83c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new fc3c5f67e86 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new a6298667fba 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 0c53571467f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new abbd5c07204 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 43fbffe132a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 71902a4b010 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 90105eb3303 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 1fa8c1498ee 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new c19423e63b1 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 7ceb03134b1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new e6f53f0bb91 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new c0b87c427ca 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new bfec93d055c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 09573350125 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 22bbb0bb99d 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 383f671eb9c 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 5d26d6f88e7 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 3375d1e5bba 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 3ac7b0a8293 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 6aed906c9d9 151: onsuccess: #579: 1: Success after binutils: 21 commits new 527eff037df 152: onsuccess: #580: 1: Success after gcc: 6 commits new cbe9470b8c8 153: onsuccess: #582: 1: Success after glibc: 9 commits new cfc88aa2256 154: onsuccess: #583: 1: Success after linux: 10 commits new b4231f96d32 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new ebf9d25a52b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new a076c633f89 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 6c5d88969eb 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 31c3272894c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new d9a288cd11c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 22ff44fb8ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2f0b135ed2e 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 094349b7a1e 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 985940c6b8b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 20fd5c5782d 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new dba49c2ad54 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 8e37b95392d 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 3814437d93f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 6233dd9f904 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 13483a2f873 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new ebfd56be6e7 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 4ce6a5aebab 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new b984d1beeb2 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 71297c27e6a 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 2196926849e 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 184d91310d0 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new c04d8cf4e84 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 1f254cf1c61 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 7884ea906d0 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 3d9e7c16910 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ef886800974 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 9f7be33e91f 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 6fef78f33b6 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 49d299b3fa3 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 5a7b527a899 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b3b0881790a 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 84967e6908c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new c6126b88e5b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 8003c0d3ab7 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 606db981805 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 887fe6b5a47 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 7a789b69ad1 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new cb15f070be9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 92e85a20a8a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new f3f95708344 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 09e1bb29e66 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4a2eeea1a51 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 282e2acb3a2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new ad23f629d0b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f39a61d3096 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b0a1df2f1ba 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 41418ede423 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bb6eb6add36 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 56e46a7f88a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 6b5ee3a4a87 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 3551736db70 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8d6969ed639 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2b3d4a97b77 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new d83d260efc4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c8ff8dd2042 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a52b148ebf3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3033b7a4da2 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 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 (b83339e1efc) \ 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 1728 -> 1912 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 3428 bytes 03-build_abe-binutils/console.log.xz | Bin 52324 -> 52324 bytes 04-build_abe-gcc/console.log.xz | Bin 236908 -> 238472 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9088 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 237264 -> 235712 bytes 08-build_abe-gdb/console.log.xz | Bin 50700 -> 50212 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2036 -> 2116 bytes 11-check_regression/console.log.xz | Bin 6140 -> 4484 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 42 ++-- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++- sumfiles/binutils.log.xz | Bin 62292 -> 62652 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100576 -> 100592 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 132036 -> 132072 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 28 files changed, 390 insertions(+), 392 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig updated (151c9e16186 -> d5db0964248)

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-next-allmodconfig in repository toolchain/ci/base-artifacts. from 151c9e16186 52: onsuccess: #7: 23403: Success after linux: 1124 commits new d5db0964248 53: onsuccess: #8: 23419: 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 3448 bytes 03-build_abe-binutils/console.log.xz | Bin 30864 -> 31004 bytes 04-build_abe-stage1/console.log.xz | Bin 89800 -> 89980 bytes 05-build_abe-qemu/console.log.xz | Bin 32460 -> 29568 bytes 06-build_linux/console.log.xz | Bin 8772 -> 8932 bytes 08-check_regression/console.log.xz | Bin 3120 -> 4376 bytes 08-check_regression/mail-body.txt | 22 +++++++++++----------- 08-check_regression/results.regressions | 11 ----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 ++++++++++++------------ mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 13 +------------ 19 files changed, 48 insertions(+), 67 deletions(-) delete mode 100644 08-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-cpu2017rate/llvm-arm-master-O3_LTO updated (2ae8f39f74e -> 3241bad11df)

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-code_vect-cpu2017rate/llvm-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 2ae8f39f74e 1: onsuccess: #2: 1: [TCWG CI] No change after llvm: 201 commits new 3241bad11df 2: onsuccess: #3: 1: [TCWG CI] No change after llvm: 468 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 1776 -> 1760 bytes 02-build_bmk_llvm/console.log.xz | Bin 233016 -> 244100 bytes 03-benchmark/benchmark-build.log | 106 +- 03-benchmark/benchmark.log | 104 +- 03-benchmark/console.log.xz | Bin 3872 -> 3848 bytes .../compare-results-vs-first-internal.csv | 37 +- .../compare-results-vs-prev-internal.csv | 39 +- 04-check_regression/console.log.xz | Bin 4880 -> 5468 bytes .../csv-results-vs-first-1/perf.csv | 87 +- .../csv-results-vs-first-1/results.csv | 4189 ++- .../csv-results-vs-first-1/size.csv | 4117 ++- 04-check_regression/csv-results-vs-first-1/sve.csv | 1 + 04-check_regression/csv-results-vs-prev-0/perf.csv | 81 +- .../csv-results-vs-prev-0/results.csv | 29734 +++++++++++++++++-- 04-check_regression/csv-results-vs-prev-0/size.csv | 29657 ++++++++++++++++-- 04-check_regression/csv-results-vs-prev-0/sve.csv | 2 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 87 +- .../csv-results-vs-prev-1/results.csv | 4189 ++- 04-check_regression/csv-results-vs-prev-1/size.csv | 4117 ++- 04-check_regression/csv-results-vs-prev-1/sve.csv | 1 + 04-check_regression/results-vs-first-brief.csv | 36 +- 04-check_regression/results-vs-first-full.csv | 91 +- 04-check_regression/results-vs-first-internal.csv | 40 +- 04-check_regression/results-vs-first.csv | 40 +- 04-check_regression/results-vs-first.log | 587 +- 04-check_regression/results-vs-prev-brief.csv | 36 +- 04-check_regression/results-vs-prev-full.csv | 95 +- 04-check_regression/results-vs-prev-internal.csv | 42 +- 04-check_regression/results-vs-prev.csv | 42 +- 04-check_regression/results-vs-prev.log | 707 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-functional.json | 4 +- .../500.perlbench_r/results-metadata.json | 10 +- .../500.perlbench_r/results-metrics.json | 2 + .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 70 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 65 files changed, 68938 insertions(+), 9634 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-coremark/gnu_eabi-arm_eabi-master-Os_LTO updated (2848e06e406 -> 4e82e3dd73e)

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-code_size-coremark/gnu_eabi-arm_eabi-master-Os_LTO in repository toolchain/ci/base-artifacts. from 2848e06e406 64: onsuccess: #7: 1: [TCWG CI] No change after binutils/gc [...] new 4e82e3dd73e 65: onsuccess: #8: 1: [TCWG CI] No change after binutils/gc [...] 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 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 3500 bytes 03-build_abe-binutils/console.log.xz | Bin 30472 -> 30960 bytes 04-build_abe-stage1/console.log.xz | Bin 87308 -> 87828 bytes 06-build_abe-newlib/console.log.xz | Bin 14496 -> 14400 bytes 07-build_abe-stage2/console.log.xz | Bin 162416 -> 162860 bytes 08-benchmark/benchmark-build.log | 106 +++--- 08-benchmark/benchmark.log | 104 +++--- 08-benchmark/console.log.xz | Bin 4040 -> 4020 bytes 09-check_regression/console.log.xz | Bin 7020 -> 8320 bytes .../output-bmk-results/error_code-1 | 0 09-check_regression/results-vs-first.log | 2 +- 09-check_regression/results-vs-prev.log | 4 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Coremark/results-metadata.json | 12 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- .../squad-vs-first/coremark/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 406 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 32 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results_id | 2 +- 26 files changed, 388 insertions(+), 376 deletions(-) delete mode 100644 09-check_regression/output-bmk-results/error_code-1 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (8e687fcf1b5 -> a5976c17dc1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. discards 8e687fcf1b5 182: onsuccess: #23: 2: Success after binutils/gcc: 42 commits discards e7e1e32fda3 181: onsuccess: #22: 2: Success after binutils/gcc: 59 commits discards ec0342e199d 180: onsuccess: #21: 2: Success after binutils/gcc: 13 commits discards eeaeddf1941 179: onsuccess: #20: 2: Success after binutils/gcc: 14 commits discards 91431a7990b 178: onsuccess: #19: 2: Success after binutils/gcc: 60 commits discards 240f4554751 177: onsuccess: #18: 2: Success after binutils/gcc: 34 commits discards 7d2dcd57e14 176: onsuccess: #17: 2: Success after binutils/gcc: 42 commits discards b46082a740a 175: onsuccess: #16: 0: Success after binutils: 24 commits discards 8527866e937 174: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards 94095e9bfee 173: force: #14: 2: Success after binutils: 10 commits discards 1df0bdcd69f 172: onsuccess: #12: 2: Success after binutils/gcc: 41 commits discards e019c8dd729 171: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 792933da429 170: onsuccess: #10: 2: Success after binutils/gcc: 11 commits discards 172b7b0b777 169: onsuccess: #9: 2: Success after binutils/gcc: 50 commits discards c71fbe6abcc 168: onsuccess: #8: 2: Success after binutils/gcc: 35 commits discards 26e6c53d574 167: onsuccess: #7: 2: Success after binutils/gcc: 395 commits discards 3030840a919 166: onsuccess: #581: 2: Success after binutils/gcc: 190 commits discards aa94c4e9fc9 165: onsuccess: #575: 2: Success after binutils/gcc: 86 commits discards 5f55d732b78 164: onsuccess: #574: 2: Success after binutils/gcc: 114 commits discards 3e3f9bb65ba 163: onsuccess: #572: 2: Success after binutils/gcc: 147 commits discards 2387ee49b8a 162: onsuccess: #571: 2: Success after binutils/gcc: 75 commits discards 4bec2646e5d 161: onsuccess: #570: 2: Success after binutils/gcc: 57 commits discards 7e008efb26d 160: onsuccess: #568: 2: Success after binutils/gcc: 20 commits discards 2e09ab40cf1 159: onsuccess: #567: 2: Success after binutils/gcc: 28 commits discards 39d81265791 158: onsuccess: #566: 2: Success after binutils/gcc: 7 commits discards 66d2126a28f 157: onsuccess: #565: 2: Success after binutils/gcc: 79 commits discards a0ef478dde2 156: onsuccess: #562: 2: Success after binutils/gcc: 47 commits discards 1b6c8e37421 155: onsuccess: #561: 2: Success after binutils/gcc: 108 commits discards 147bf365165 154: onsuccess: #560: 2: Success after binutils/gcc: 59 commits discards a227127c5c4 153: onsuccess: #558: 2: Success after binutils/gcc: 28 commits discards 7fd5f3fe8f6 152: onsuccess: #556: 2: Success after binutils/gcc: 129 commits discards 330f14f8d7f 151: onsuccess: #555: 2: Success after binutils/gcc: 27 commits discards b6254ec328f 150: onsuccess: #554: 2: Success after binutils/gcc: 80 commits discards 33e4ef56c4f 149: onsuccess: #553: 2: Success after binutils/gcc: 28 commits discards 6fcd0feafd3 148: onsuccess: #552: 2: Success after binutils/gcc: 35 commits discards 19949c1fb49 147: onsuccess: #551: 2: Success after binutils/gcc: 6 commits discards 3694465b1c7 146: onsuccess: #550: 2: Success after binutils/gcc: 39 commits discards acdf712feeb 145: onsuccess: #549: 2: Success after binutils/gcc: 33 commits discards 005b5706c88 144: onsuccess: #548: 2: Success after binutils/gcc: 35 commits discards e1dc2f700b9 143: onsuccess: #547: 2: Success after binutils/gcc: 77 commits discards a5c6968bbcf 142: onsuccess: #546: 2: Success after binutils/gcc: 37 commits discards 7474c175f53 141: onsuccess: #545: 2: Success after binutils/gcc: 123 commits discards e85959310f8 140: onsuccess: #544: 2: Success after binutils/gcc: 46 commits discards 5caa896da15 139: onsuccess: #543: 2: Success after binutils/gcc: 111 commits discards 630f3d5c677 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits discards 02af4f0798e 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits discards f66c87f4ff1 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits discards 825fc75fdcd 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits discards bd5e381f3df 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits discards 5ac6e8c2457 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits discards 90a0db07263 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits discards 2e2133cabd6 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits discards 00091f42a45 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits discards 10ed98664f7 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards d4138f4cf48 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits discards baa7e456f29 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits discards b3fc06a3f1a 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits discards c5f4b409d42 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits discards ee830629052 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits discards b61bef91e14 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits discards 525c250f2c7 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits discards a237baca723 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits discards e6354a3b051 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits discards 0aae87c2f9a 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits discards fc6669b8a49 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits discards 4ad99fff5c2 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits discards 8561afed319 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits discards abeed5ac3c9 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits discards db55447fc4b 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits discards a686d2ae1c4 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits discards a7e537b93d0 112: onsuccess: #510: 2: Success after binutils/gcc: 3 commits discards 6db2e37710f 111: onsuccess: #509: 2: Success after binutils/gcc: 36 commits discards 636103608d7 110: onsuccess: #508: 2: Success after binutils/gcc: 31 commits discards 70ea72d9f41 109: onsuccess: #507: 2: Success after binutils/gcc: 27 commits discards cbed4d24e50 108: onsuccess: #506: 2: Success after binutils/gcc: 47 commits discards ae3b796b6db 107: onsuccess: #505: 2: Success after binutils/gcc: 32 commits discards 3cbff929ffb 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits discards f9e3ebad94a 105: onsuccess: #503: 2: Success after binutils/gcc: 8 commits discards 2821c3a32db 104: onsuccess: #502: 2: Success after binutils/gcc: 31 commits discards acc5b065284 103: onsuccess: #501: 2: Success after binutils/gcc: 37 commits discards 2484030e3f0 102: onsuccess: #500: 2: Success after binutils/gcc: 27 commits discards 8c288abad6c 101: onsuccess: #499: 2: Success after binutils/gcc: 172 commits discards 447cdcc6cb3 100: onsuccess: #498: 1: Success after gcc: 85 commits discards b09d0a680d3 99: force: #497: 1: Failure after basepoints/gcc-13-4227-g0 [...] discards 63bb320b18f 98: force: #496: 2: Success after gcc: 9 commits discards 762f76f71bc 97: onsuccess: #493: 2: Success after binutils: 49 commits discards afc7cfc37a9 96: onsuccess: #484: 2: Success after binutils: 14 commits discards 919b906aa6a 95: onsuccess: #482: 2: Success after binutils/gcc: 51 commits discards 6544dc65fe0 94: onsuccess: #481: 2: Success after binutils/gcc: 367 commits discards a6933ca24bf 93: onsuccess: #477: 2: Success after binutils: 4 commits discards 75098956e94 92: onsuccess: #475: 2: Success after binutils/gcc: 58 commits discards 4236f709d70 91: onsuccess: #474: 2: Success after binutils/gcc: 50 commits discards 45894d2c452 90: onsuccess: #473: 2: Success after binutils/gcc: 61 commits discards 4922cf2f3f1 89: onsuccess: #472: 2: Success after binutils/gcc: 67 commits discards 51d30f792a7 88: onsuccess: #471: 2: Success after binutils/gcc: 71 commits discards b9bf8628bdc 87: onsuccess: #470: 2: Success after binutils/gcc: 13 commits discards 21fdffdc373 86: onsuccess: #469: 2: Success after binutils/gcc: 22 commits discards 891f8f20713 85: onsuccess: #468: 2: Success after binutils/gcc: 72 commits discards 050f94c245b 84: onsuccess: #467: 2: Success after binutils/gcc: 42 commits discards e0b3982f682 83: onsuccess: #466: 2: Success after binutils/gcc: 33 commits discards e788757d78f 82: onsuccess: #465: 2: Success after binutils/gcc: 26 commits new e2b53ae6fbf 82: onsuccess: #465: 2: Success after binutils/gcc: 26 commits new 5b345c2aaee 83: onsuccess: #466: 2: Success after binutils/gcc: 33 commits new fb9c100bf77 84: onsuccess: #467: 2: Success after binutils/gcc: 42 commits new 053f26f1208 85: onsuccess: #468: 2: Success after binutils/gcc: 72 commits new cd501cdb670 86: onsuccess: #469: 2: Success after binutils/gcc: 22 commits new ba6e5fd05fc 87: onsuccess: #470: 2: Success after binutils/gcc: 13 commits new 658e8252cc4 88: onsuccess: #471: 2: Success after binutils/gcc: 71 commits new 04c9cf67a71 89: onsuccess: #472: 2: Success after binutils/gcc: 67 commits new 5f19743b819 90: onsuccess: #473: 2: Success after binutils/gcc: 61 commits new 51abb3d3a59 91: onsuccess: #474: 2: Success after binutils/gcc: 50 commits new f53a2d978fb 92: onsuccess: #475: 2: Success after binutils/gcc: 58 commits new e10af6b17f7 93: onsuccess: #477: 2: Success after binutils: 4 commits new acd716b589a 94: onsuccess: #481: 2: Success after binutils/gcc: 367 commits new c5ada210cd8 95: onsuccess: #482: 2: Success after binutils/gcc: 51 commits new 4bfb65f83a0 96: onsuccess: #484: 2: Success after binutils: 14 commits new d0d9690768c 97: onsuccess: #493: 2: Success after binutils: 49 commits new 28b5f5fca00 98: force: #496: 2: Success after gcc: 9 commits new 61818cd781a 99: force: #497: 1: Failure after basepoints/gcc-13-4227-g0 [...] new d0381761966 100: onsuccess: #498: 1: Success after gcc: 85 commits new 2a3dcc912a4 101: onsuccess: #499: 2: Success after binutils/gcc: 172 commits new 4cd0772a769 102: onsuccess: #500: 2: Success after binutils/gcc: 27 commits new ab17ae3a37e 103: onsuccess: #501: 2: Success after binutils/gcc: 37 commits new 606d0ea5d9a 104: onsuccess: #502: 2: Success after binutils/gcc: 31 commits new c7251ce61e0 105: onsuccess: #503: 2: Success after binutils/gcc: 8 commits new 253012ecf30 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits new 34e242396d6 107: onsuccess: #505: 2: Success after binutils/gcc: 32 commits new 7688d9d746a 108: onsuccess: #506: 2: Success after binutils/gcc: 47 commits new 3c7276df6d1 109: onsuccess: #507: 2: Success after binutils/gcc: 27 commits new a89da598884 110: onsuccess: #508: 2: Success after binutils/gcc: 31 commits new 442f5f0434a 111: onsuccess: #509: 2: Success after binutils/gcc: 36 commits new afa921c4628 112: onsuccess: #510: 2: Success after binutils/gcc: 3 commits new ef9bbd9cb39 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits new 0238185825d 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits new c64d9a6bc30 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits new d7258e79597 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits new 1afca9e1304 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits new 8f754699756 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits new 36b139dfaef 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits new 1cefa110bcd 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits new c88ecbd06f1 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits new cfb24bccb1f 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits new f0424ea4349 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits new 530d768b1f7 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits new 22b70db2d9e 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits new 437f0dafffa 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits new eefe2a9c8a4 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits new 49dc3473989 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits new dfa89fa99b6 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new 7b9778ee609 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits new 9d44d3d355c 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits new 9879cf397a2 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits new 9de6b9dcad6 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits new 2dc0071071c 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits new 2fa07704d2f 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits new 3f04fa0e433 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits new dfe9af2afaa 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits new 6c850ed18d9 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits new 94d0b797cd9 139: onsuccess: #543: 2: Success after binutils/gcc: 111 commits new 581ec4bfc50 140: onsuccess: #544: 2: Success after binutils/gcc: 46 commits new 0bec2a52ee7 141: onsuccess: #545: 2: Success after binutils/gcc: 123 commits new 164c21f8562 142: onsuccess: #546: 2: Success after binutils/gcc: 37 commits new 3c77ab21f0a 143: onsuccess: #547: 2: Success after binutils/gcc: 77 commits new 8453bd6caf1 144: onsuccess: #548: 2: Success after binutils/gcc: 35 commits new b0aec0993ae 145: onsuccess: #549: 2: Success after binutils/gcc: 33 commits new c9822c9ab7b 146: onsuccess: #550: 2: Success after binutils/gcc: 39 commits new 29dc748eded 147: onsuccess: #551: 2: Success after binutils/gcc: 6 commits new 402ffa1080c 148: onsuccess: #552: 2: Success after binutils/gcc: 35 commits new 48f4bd0ab3e 149: onsuccess: #553: 2: Success after binutils/gcc: 28 commits new f794c806e26 150: onsuccess: #554: 2: Success after binutils/gcc: 80 commits new 75ee3eedf15 151: onsuccess: #555: 2: Success after binutils/gcc: 27 commits new de9816551d2 152: onsuccess: #556: 2: Success after binutils/gcc: 129 commits new bce5c02cd8c 153: onsuccess: #558: 2: Success after binutils/gcc: 28 commits new f15c2628bbe 154: onsuccess: #560: 2: Success after binutils/gcc: 59 commits new 145f8f857dd 155: onsuccess: #561: 2: Success after binutils/gcc: 108 commits new 651f08fa9be 156: onsuccess: #562: 2: Success after binutils/gcc: 47 commits new fa464ac1831 157: onsuccess: #565: 2: Success after binutils/gcc: 79 commits new 3895145196f 158: onsuccess: #566: 2: Success after binutils/gcc: 7 commits new ccd55d4e01d 159: onsuccess: #567: 2: Success after binutils/gcc: 28 commits new ce2655483f4 160: onsuccess: #568: 2: Success after binutils/gcc: 20 commits new a7b727a19d7 161: onsuccess: #570: 2: Success after binutils/gcc: 57 commits new 703a63cb8ab 162: onsuccess: #571: 2: Success after binutils/gcc: 75 commits new 6a4ebe8c4bf 163: onsuccess: #572: 2: Success after binutils/gcc: 147 commits new 7cde3b3a6b3 164: onsuccess: #574: 2: Success after binutils/gcc: 114 commits new 40b81e01f4d 165: onsuccess: #575: 2: Success after binutils/gcc: 86 commits new 32d0acdc22c 166: onsuccess: #581: 2: Success after binutils/gcc: 190 commits new 12481100ee2 167: onsuccess: #7: 2: Success after binutils/gcc: 395 commits new 4c6b6f5356a 168: onsuccess: #8: 2: Success after binutils/gcc: 35 commits new 94c5f91a951 169: onsuccess: #9: 2: Success after binutils/gcc: 50 commits new b702012b724 170: onsuccess: #10: 2: Success after binutils/gcc: 11 commits new 0127a01ead3 171: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new b9a23bbce14 172: onsuccess: #12: 2: Success after binutils/gcc: 41 commits new 69277254690 173: force: #14: 2: Success after binutils: 10 commits new c0411886524 174: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new 9da0ecbfaac 175: onsuccess: #16: 0: Success after binutils: 24 commits new bcc57102bf5 176: onsuccess: #17: 2: Success after binutils/gcc: 42 commits new d017a58fed3 177: onsuccess: #18: 2: Success after binutils/gcc: 34 commits new ccc8c6f1a75 178: onsuccess: #19: 2: Success after binutils/gcc: 60 commits new 45cf9bdf892 179: onsuccess: #20: 2: Success after binutils/gcc: 14 commits new 230ba8c7e50 180: onsuccess: #21: 2: Success after binutils/gcc: 13 commits new 4fdf0996ee3 181: onsuccess: #22: 2: Success after binutils/gcc: 59 commits new d4d21ac33a4 182: onsuccess: #23: 2: Success after binutils/gcc: 42 commits new a5976c17dc1 183: onsuccess: #24: 2: Success after binutils/gcc: 38 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 (8e687fcf1b5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 3468 bytes 04-build_abe-binutils/console.log.xz | Bin 52992 -> 53184 bytes .../console.log.xz | Bin 603416 -> 603948 bytes 06-check_regression/console.log.xz | Bin 3064 -> 3060 bytes 07-update_baseline/console.log | 42 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++----- 13 files changed, 37 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (82258019aa7 -> bf3bec12f14)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 82258019aa7 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 27da5733953 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9b4b015406b 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 68ab1973726 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 152a307b82c 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 84ad1237216 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 12db392322e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 61acc11b700 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ce92d8243dd 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 79801c68448 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards c39a146b184 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 5cb896ab557 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 3a367c91209 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0d7cfb992e0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards c5dc698712b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards be2e782a3ca 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c4fd60b9509 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 05276e1d6ae 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 08ffa3d5a99 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards bc073743683 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4982e28001e 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 8b1a789ad8f 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 6a2ad6252fe 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards f8bfdbfca46 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 88bb800d84d 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 4d87100aa60 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 57e0b2d756e 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards eec4cf5b5f6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards f78cbce655d 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 1440b1c688a 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 0f878ba05bf 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 630bf0795d4 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 05af3204bfa 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 8d53bf4c692 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 1bfde0ccee4 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards f87ce222ef9 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 809238de55f 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 585596c9d18 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 102b07c590a 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 0461ec5d5a5 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 02197bad848 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 1fcaf8626dd 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 33e2b96782e 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards c5a2993bd40 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 5955a788ac8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 3a50db02813 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards b2401eeb054 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 5219d1a6d74 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards c325597e25b 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards ecafe5b9c53 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards c95e0b36e08 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards d90bebcd3e7 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards ffb5eab14d9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards c9d4bd3aa65 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 01932610fa9 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 62f19875bf0 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards d079e33d08c 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards d516e7880a6 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 972545aaf0d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 30793880f1d 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards c312e047a22 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 0f178447a48 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 589056f65ed 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 7eecf054e80 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 4815c27de95 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 38af6c34353 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 43fc455d18f 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards d9a16973310 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards c9f6d0d53ba 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 1cc84766045 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 9d59532ab68 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 123c075cf6c 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 5d81619a17e 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards a3808ab53af 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards cbfe7102b2b 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 7e5d1ccea8e 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards dc650121f02 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards a2a1b23d46b 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 1dbe4893a72 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards e6ed3555171 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards ab8a89c4200 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards f978b931302 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards ab0a0dee42f 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards d02adb7ccba 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 5e2e95a7483 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 25b4cc06c3f 41: onsuccess: #51: 1: Success after binutils: 12 commits discards cf3722465a7 40: onsuccess: #49: 1: Success after linux: 219 commits discards 388cb54a214 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 8b35fdf1f2f 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 4d5e5254caf 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards ba1a40c2e26 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 15a6fd29196 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards c0be689b448 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 191ed039c02 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards 788145a931a 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 5017447d08e 31: onsuccess: #38: 1: Success after linux: 12 commits discards 826625ca8e2 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 05b1c6b3688 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 7a08251a29b 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 8efe27439ac 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 18230b5a291 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 17ed9c5dce9 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c2e4687858f 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 4ebaaac3450 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 8a64e46c146 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 6022d72008f 30: onsuccess: #36: 1: Success after binutils: 18 commits new 15a01cb05ba 31: onsuccess: #38: 1: Success after linux: 12 commits new c7825971591 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 97c7ea9d717 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new fe6bc565882 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 20ab8601f86 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 6d688266b1b 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new ea51b5d83a2 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new cd977ba6416 38: onsuccess: #46: 1: Success after binutils: 26 commits new ac54dac0339 39: onsuccess: #48: 1: Success after glibc: 2 commits new 62c327d3c62 40: onsuccess: #49: 1: Success after linux: 219 commits new 859aa3c8107 41: onsuccess: #51: 1: Success after binutils: 12 commits new 8b79af23729 42: onsuccess: #53: 1: Success after linux: 3008 commits new 3354cbeae72 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new f95e345aca2 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 6e4fbb70516 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new e7bd8d53418 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new ad502572639 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 40959f4b766 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 2b71054d782 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 37ef82075c2 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 4d41d80b2d9 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new fb40931d277 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new e96b47144ba 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 9c8c20c6066 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 01d0e52b7b9 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new d4ad047f1f1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new e4fa956cfc3 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new befe0b88eac 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new c17c1b1f3ea 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new f9040b700e1 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new f5d8ef02e3e 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 7f3259f8ae5 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 59dca166421 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new f208d53d1fe 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new cc4529b5774 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new cc2b6d7fece 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 3aae7e308ea 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 28adf79126b 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new a1cdb1b4823 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new cd0644cb9ea 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 5a12cd5eead 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 444506f8cf2 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new cb1b2e6654d 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 66296c211fd 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new bc1eff16c86 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 1eda85ec53e 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new aae718a35c0 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 2ccce22d3c9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 78ed5e20c2b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new c5bf6c82369 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new b89b87f1224 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new d99c77be83f 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new e181f3ebc6f 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new d6ab0efb3b2 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new dc6b8b439dd 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new c8aaee03300 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new c9fd886945e 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new ef76228d24d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 0c8e3f20211 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 8f74dd31fdd 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 226fb7afe65 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new ce8df79a1fa 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new e8dd8c73765 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 6aa10ec8c57 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 6189d701dd3 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 9a37954a35d 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 8d10a17e0d5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new c96f11812e3 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new b523485b34c 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 1f8b4a70b45 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 12063313878 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 727638960e6 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new ac18600442d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 29ef675bf88 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 78b0709bdd7 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new ba3a7275432 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 1d9ac0bff9e 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new aba6544afa8 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3d711e37daa 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 75509c474d1 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ded5f0573d1 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 73dd078c642 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a8e8f534ce0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 00f5fbcd4ec 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e267a4bfcc2 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7b3b5ad2001 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 96f1963ddfa 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 6428b9e90f8 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 363c5c9188b 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 041902c9579 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2d0506b2d72 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 3e51cf9bbce 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 6d1cf9dac0d 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 4da674099a7 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new ef24b14f91e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 32396829936 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new bf3bec12f14 127: force: #27: : Failure after baseline build: no new 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 (82258019aa7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1748 -> 1932 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 3444 bytes 03-build_abe-binutils/console.log.xz | Bin 39080 -> 39156 bytes 04-build_abe-gcc/console.log.xz | Bin 203888 -> 204728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 243948 -> 245664 bytes 08-build_abe-gdb/console.log.xz | Bin 38588 -> 38932 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2568 -> 1348 bytes 11-check_regression/console.log.xz | Bin 6100 -> 2564 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 7 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 7 - 11-check_regression/results.compare2 | 42 ---- 11-check_regression/results.regressions | 2 + 12-update_baseline/console.log | 44 ++-- dashboard/dashboard-generate.sh | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 7 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +-- results | 6 +- sumfiles/gdb.log.xz | Bin 11916 -> 0 bytes sumfiles/gdb.sum | 396 -------------------------------- 26 files changed, 52 insertions(+), 496 deletions(-) delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 create mode 100644 11-check_regression/results.regressions delete mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023