Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[binutils-gdb] branch master updated (7fd14d6f580 -> cc67f780ecd)

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 7fd14d6f580 sim: unify sim-signal.o building new cc67f780ecd sim: info: convert verbose field to a bool 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: include/sim/sim.h | 5 +++-- sim/common/cgen-scache.c | 2 +- sim/common/cgen-scache.h | 2 +- sim/common/sim-info.c | 2 +- sim/common/sim-module.c | 2 +- sim/common/sim-module.h | 4 ++-- sim/common/sim-profile.c | 12 ++++++------ sim/common/sim-profile.h | 2 +- sim/d10v/interp.c | 2 +- sim/erc32/interf.c | 2 +- sim/frv/profile.c | 4 ++-- sim/h8300/compile.c | 2 +- sim/m32c/gdb-if.c | 2 +- sim/m32r/sim-if.c | 4 ++-- sim/m68hc11/interp.c | 2 +- sim/mcore/interp.c | 2 +- sim/microblaze/interp.c | 2 +- sim/ppc/sim_calls.c | 2 +- sim/rl78/gdb-if.c | 2 +- sim/rx/gdb-if.c | 2 +- sim/sh/interp.c | 2 +- 21 files changed, 31 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (c76042777d -> d5d774a216)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards c76042777d 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] discards f406bb535f 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] discards 2d4a4424f2 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards d03df2b1cc 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 8f1af47734 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 5b45f8c83d 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 8f418d4041 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards 9e7e3ffdf9 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards dbe2a68679 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards e718c708e5 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards 0b28346544 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 57e0689095 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 334d67ce79 152: onsuccess: #903: 1: Success after linux: 22 commits discards a862d0f824 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 20d9f4506f 150: onsuccess: #900: 1: Success after gcc: 11 commits discards f7aac07811 149: onsuccess: #899: 1: Success after binutils: 15 commits discards c6fab153dc 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 3f5aee047d 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 6ce33b8973 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 44ac6788ec 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 1f66dd6bc1 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards d88ba257aa 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards e30b9471c5 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 2c04dc2c6a 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards da7a90e71f 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 98faa44c58 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards bcd26d8fd4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 61a7fec923 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 84d7701b95 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards a872d0e404 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 0aae4c50c7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 8cd54219a5 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards b7def3dac2 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 77e084c275 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 46669bb16f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards c90838b631 129: onsuccess: #878: 1: Success after linux: 3008 commits discards cce634fee1 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 6be7ae8482 127: onsuccess: #874: 1: Success after linux: 219 commits discards 178539176c 126: onsuccess: #873: 1: Success after glibc: 2 commits discards efa1a353f6 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 40bc0adbf3 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 1edcc9013a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 15eea36d02 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 55dc28ab69 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards e03d5e1d6f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards cabb308076 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 573b02836e 118: onsuccess: #863: 1: Success after linux: 12 commits discards 51e307ab54 117: onsuccess: #861: 1: Success after binutils: 18 commits discards b1cbb561fd 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 22085b112b 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards e9491effcf 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards f3475edf64 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards ea6580e828 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards daa3ab5991 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards d701332e5b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards eb47c18d9e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards bef04f5519 108: onsuccess: #850: 1: Success after gcc: 2 commits discards c0059c996d 107: onsuccess: #849: 1: Success after binutils: 5 commits discards d9d3ac0044 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards d95f1eafc0 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards edf256b350 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 7d4d3faaa7 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 5f569943c9 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards a56ef82ee5 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards d80c340deb 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards a5344e190e 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards c6969e40c7 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards b267cc3d50 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 7b2deef19f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards afc6be8932 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f4df154887 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 6f51d467f0 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards f4fb7f07d5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards e25e235d08 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards cbbcf149c1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards d28add0ca2 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 96d963610f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 1436dfe078 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 4f5c9068be 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 1f2cbb44c3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards b82dc92cf6 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 87d5204ce5 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 8e475aaede 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 3951c9b8db 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards bbcb3bd52b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 4d78dca1cb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards dab824ccba 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 52e41111a5 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards b4f4305233 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 039c627799 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 98c3504654 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 2c8db1d6a1 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards b0e5b4db80 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards c8d6db700c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 1fb071e3a3 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards ade90f4720 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 24f68f29a2 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 17cf4fa7b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 5f69bec7aa 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 36a8821e39 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 7186c268de 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new f6e13efe7e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new d2aa15eb0d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 5c5020a995 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 85b7bee377 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new c06dda841d 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 2c67284e6e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 6256b7c43c 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f977648254 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new bd2c659386 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 9ed3edaff6 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 89f1f609b9 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 2dc79d8d3a 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 51c4370969 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new dfeead319d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 85974325fc 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new cb7be14b7c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 8ec8f09874 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 2976956797 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new cb10f15c54 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 6749b878c5 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 07af348e96 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 4e17975e28 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 3fdd186ad9 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 88409a05ae 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9f9825356f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new df23c1c1b0 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new bbcac8699d 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 2f0b5882f7 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 4ec91500ae 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new efcbfd73ca 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 736f83fd78 94: onsuccess: #832: 1: Success after binutils: 5 commits new e7c8064c6f 95: onsuccess: #835: 1: Success after binutils: 3 commits new b99edd5b44 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 20f601330d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 2bc8919dba 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ec6ad53888 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new e4c95efe8e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 4c6c8a46ae 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 3d3e504f64 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 99a7cf9216 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new ba357c1e41 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new e5f0a7c81f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 608e9f7bff 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 65a83ae845 107: onsuccess: #849: 1: Success after binutils: 5 commits new 0a871851a5 108: onsuccess: #850: 1: Success after gcc: 2 commits new b6188672b9 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 0205174ad6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new f4b3137ab2 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new d6c5d55973 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 99401840bd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 4caa910d0b 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new a62f3e533f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 95fe1583fe 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 548b758e51 117: onsuccess: #861: 1: Success after binutils: 18 commits new 99f8b6032b 118: onsuccess: #863: 1: Success after linux: 12 commits new b1fbbdf6b1 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 8df6fa570e 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 3d6dbae8e8 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 1e68025284 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 6dc5e8b3c8 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 6b53b5bce4 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 42141c1170 125: onsuccess: #871: 1: Success after binutils: 26 commits new 21b41a29ef 126: onsuccess: #873: 1: Success after glibc: 2 commits new d0a7a10aa0 127: onsuccess: #874: 1: Success after linux: 219 commits new 41ee2a4a9e 128: onsuccess: #876: 1: Success after binutils: 12 commits new dc2540a7ad 129: onsuccess: #878: 1: Success after linux: 3008 commits new a6c5e15593 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 1d104eab7c 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 9b3be30403 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 7eb82f9275 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new bda3746cdf 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 1bcb10e567 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new a14d895186 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new a154914e13 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new a17d0be1a4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 5e508d2467 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 4b9b0efefc 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 2b27ddd115 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 50d925382b 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new fffbeb50d8 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new e64abf286c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 6b2b8d71dc 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 112e3c5175 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new e2c706ca31 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 930e9b74ad 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new f548fec3b4 149: onsuccess: #899: 1: Success after binutils: 15 commits new 69fbb656df 150: onsuccess: #900: 1: Success after gcc: 11 commits new ec301bb75b 151: onsuccess: #902: 1: Success after glibc: 8 commits new 28d7a157b7 152: onsuccess: #903: 1: Success after linux: 22 commits new 44f33bd1ca 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 017f1e3484 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 6e2f9895f3 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new d83aca84df 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new 7abbed7cd9 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 7e0f5e414b 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new e9848a2eef 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 420433c323 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 4a15578cca 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new c20c6929af 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new 309a4bbc70 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] new a2088eb8b1 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] new d5d774a216 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] 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 (c76042777d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39276 -> 39592 bytes 04-build_abe-gcc/console.log.xz | Bin 214276 -> 214040 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8848 bytes 07-build_abe-glibc/console.log.xz | Bin 246432 -> 244524 bytes 08-build_abe-gdb/console.log.xz | Bin 39480 -> 39028 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3880 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2604 bytes 11-check_regression/console.log.xz | Bin 7936 -> 6876 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 67 +- 11-check_regression/results.compare | 28 +- 11-check_regression/results.compare2 | 264 +- 11-check_regression/results.regressions | 26 + 12-update_baseline/console.log | 32 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 3763128 -> 3748368 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 3307164 -> 3293808 bytes sumfiles/gcc.sum | 5074 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081316 -> 1082644 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232340 -> 232320 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456708 -> 457812 bytes sumfiles/libstdc++.sum | 17 +- 43 files changed, 2868 insertions(+), 2970 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (f88fc3e3c1 -> 33f24376a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from f88fc3e3c1 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 33f24376a6 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1784 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39488 -> 39896 bytes 04-build_abe-gcc/console.log.xz | Bin 213632 -> 214632 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8872 bytes 07-build_abe-glibc/console.log.xz | Bin 245284 -> 244760 bytes 08-build_abe-gdb/console.log.xz | Bin 39084 -> 39044 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2584 -> 2572 bytes 11-check_regression/console.log.xz | Bin 6184 -> 6092 bytes 11-check_regression/results.compare2 | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14672 -> 14676 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 31 insertions(+), 31 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (001eac1285 -> c112aebfc6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 001eac1285 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards aaf6efe102 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 63d7f69861 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards d9797e64ea 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 36e0993d6d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 353984ecc1 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 07f39b9463 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards bacc0907d5 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 0843272a32 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 3180860a97 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 44b03c006c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards cf0f208c4a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards b3f287e2f9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 3a9dff103c 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards f3fd4873c3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 2f8557f91b 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 022c0a24b4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 3e36eb9411 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 863f3d0d6e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards e9432f579e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 188dfda93a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 26ee42bbd4 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards a268dc73f3 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 55d08a4182 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 7bbd6df282 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 6fb7e86c66 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards a7377886f1 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards ed95950054 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards f1dff39100 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 40c83d4105 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards b956dcb8fa 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards f64367b8ee 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards a654bdb0ce 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 50e5ee540f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards e59670e86f 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8021276627 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards ab17f86b18 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards a2f11867ca 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards f12c194469 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards e9246ccfd2 125: onsuccess: #614: 1: Success after linux: 12 commits discards 5793e193ea 124: onsuccess: #612: 1: Success after binutils: 18 commits discards cea8df590a 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards e5286ad2cb 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards e64fd547ed 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 3abbffd3a6 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 0e897ff86d 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 06481dc7ce 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 0090eeb730 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 4bfc461344 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 16ab0aa98d 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 84e5d57460 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 12380649a1 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards a5783558fc 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards b138880517 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 1c869d1e72 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 7509d760fb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards d1051c4e60 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards b235e879ea 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 95dda72d2c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 4dff8bfab8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 3edd6bbe08 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards f4c720910c 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 95f4697d33 102: onsuccess: #586: 1: Success after binutils: 5 commits discards bbb85b6fc3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards daeacaf61d 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards f15bd14bcd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards a0044dc3a8 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards cf13680f49 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 7caddac2db 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 0bd84ae8df 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 794ce110cc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards ec8560b518 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 67b3411f74 92: onsuccess: #575: 1: Success after linux: 34 commits discards 9ace9edfb9 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 89a990c888 90: onsuccess: #572: 1: Success after binutils: 15 commits discards c9aa058884 89: onsuccess: #570: 1: Success after linux: 11 commits discards b29820d989 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f14b42bc8e 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 126cb29c4a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f8949ab7e6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 8fdefaaf77 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards cf85425442 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 62db076dae 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 4030097922 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 60462e6c2a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 6fe44cf12d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards afe807d0c7 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 11312ec788 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 373aed3151 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards e9ecb2fe39 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 328cc67336 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards e9bb50516f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 96fe16be37 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 9250f8c99c 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards ae5b6fcd16 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 3e2b9c5c34 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards eef6a4f980 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 129cd36af2 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 56b81acc4b 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 78bd3ccd81 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 27ae63c048 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new ec7ea3680e 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new a7a99f2c06 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 3a542b369f 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new c164334e96 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7a01908fe7 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 25319b8307 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 3d8d049a4f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 19b3d1859a 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new e9afda2c75 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 9b422b110c 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 1d5a0b4e09 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new e488fb5137 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 12926a7fd3 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 805e92749d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 6aeedcbea5 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 1800be6507 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 0c9d47accf 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 72763aa430 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new dac991a51a 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 24de51630c 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 402e02e7f4 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 76c51e6768 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 0cd25dfe6d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 35168bee63 87: onsuccess: #567: 1: Success after binutils: 8 commits new 6cca8cb4a6 88: onsuccess: #569: 1: Success after glibc: 10 commits new caa59ea6e2 89: onsuccess: #570: 1: Success after linux: 11 commits new acb47d17a6 90: onsuccess: #572: 1: Success after binutils: 15 commits new bb057975ef 91: onsuccess: #574: 1: Success after glibc: 3 commits new 288980f034 92: onsuccess: #575: 1: Success after linux: 34 commits new b89dfc0885 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new cf83a4d7b0 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 21962abe8c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new b3e5755860 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 38367f4f9c 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new ee69446698 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 4686ebb3e3 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new c4e847cb5b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new ee997a1431 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new d57d2af18a 102: onsuccess: #586: 1: Success after binutils: 5 commits new a6b7bda777 103: onsuccess: #589: 1: Success after binutils: 3 commits new 9ec2572110 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new aea3f9c65b 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new fc9a60c4ef 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 7b380f914d 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new acfca53285 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 245ca37045 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new e051eedc07 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new dd535a907d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 72d8bfce61 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 4fe8039d3d 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 05e6138aa2 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 82436199fb 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 00a99b54ae 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 36bd668f42 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new d96133501a 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 9f25842e60 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 38fc5a92ce 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new ec73125011 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 542c8b1a22 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 65be05e0cd 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 5b62c85e00 124: onsuccess: #612: 1: Success after binutils: 18 commits new b549ab83ca 125: onsuccess: #614: 1: Success after linux: 12 commits new bf00ac4c37 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 3d99ee6d55 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e5693e426a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 6ff7c02aef 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 5b836755fa 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 483547868d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 055af74fad 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 000f7bbe47 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 459ab2d9bc 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new d1828c1675 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 537adffd84 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new cc364318da 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new a24531487a 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new faf4c65ccf 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 116d7f2ccd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new f8cd98d1ae 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 118fe9fbaa 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new d178d64d72 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new a9f3f91b04 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 7f7c0818ac 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 46a95de768 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f555d1b414 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 7369f81a11 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 22dc6025db 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 7b224bdaf0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 3e01c8fa63 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 212feb2bb4 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 39fd7f59bf 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 2a733bf8fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 764df0185a 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new c9081ea2e8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 102edb92f0 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 53dda8b9f9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 709d1046ed 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 5734acf629 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 1642b573df 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 83deef39ae 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 6137b165d9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new f90c105d66 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new c112aebfc6 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] 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 (001eac1285) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52520 -> 52716 bytes 04-build_abe-gcc/console.log.xz | Bin 236744 -> 237940 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8884 bytes 07-build_abe-glibc/console.log.xz | Bin 235920 -> 236384 bytes 08-build_abe-gdb/console.log.xz | Bin 51556 -> 51568 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2188 -> 2408 bytes 11-check_regression/console.log.xz | Bin 8020 -> 15916 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 31 +- 11-check_regression/mail-body.txt | 130 +- 11-check_regression/results.compare | 55 +- 11-check_regression/results.compare2 | 4022 ++++++++++++++++++++++++++++++- 11-check_regression/results.regressions | 55 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 132 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 55 +- sumfiles/gdb.log.xz | Bin 1797548 -> 1716192 bytes sumfiles/gdb.sum | 3958 +----------------------------- 30 files changed, 4236 insertions(+), 4294 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (fe0fef30d6 -> d00f3628fc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts. from fe0fef30d6 47: onsuccess: #532: boot: Success after v5.15.88-30565-g3fe [...] new d00f3628fc 48: onsuccess: #533: boot: Success after binutils: 127 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 1756 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32532 -> 32532 bytes 04-build_kernel_llvm/console.log.xz | Bin 66372 -> 64320 bytes 05-build_abe-qemu/console.log.xz | Bin 32420 -> 31484 bytes 06-build_linux/console.log.xz | Bin 4152 -> 3536 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2788 -> 2944 bytes 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 | 16 ++++++++-------- 14 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O2_LTO updated (0ac64eb2f4 -> 9e1b9a93d5)

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_speed-spec2k6/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from 0ac64eb2f4 59: onsuccess: #2: 1: [TCWG CI] No change after binutils/gcc [...] new 9e1b9a93d5 60: onsuccess: #3: 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 1800 -> 1868 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31712 -> 32884 bytes 04-build_abe-stage1/console.log.xz | Bin 73096 -> 75276 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 245664 -> 248276 bytes 08-build_abe-stage2/console.log.xz | Bin 178736 -> 189304 bytes 09-benchmark/benchmark-build.log | 118 +- 09-benchmark/benchmark.log | 116 +- 09-benchmark/console.log.xz | Bin 3876 -> 3860 bytes 10-check_regression/console.log.xz | Bin 7816 -> 7808 bytes .../csv-results-vs-first-0/results.csv | 373576 ++++++------- .../csv-results-vs-first-0/size.csv | 516084 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 44 +- .../csv-results-vs-first-1/perf.csv | 168 +- .../csv-results-vs-first-1/results.csv | 337569 ++++++----- .../csv-results-vs-first-1/size.csv | 482738 ++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 40 +- .../csv-results-vs-first-1/vect.csv | 40 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 170 +- .../csv-results-vs-prev-0/results.csv | 367669 ++++++------ 10-check_regression/csv-results-vs-prev-0/size.csv | 524579 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 46 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 44 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 168 +- .../csv-results-vs-prev-1/results.csv | 337569 ++++++----- 10-check_regression/csv-results-vs-prev-1/size.csv | 482738 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 40 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 40 +- 10-check_regression/mail-body.txt | 5 + 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 182 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1418 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 190 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1732 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../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 | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../436.cactusADM/results-metadata.json | 16 +- .../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 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 4 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../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 +- .../483.xalancbmk/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 46 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 0 -> 2929656 bytes save-temps/401.bzip2.tar.xz | Bin 0 -> 301040 bytes save-temps/403.gcc.tar.xz | Bin 0 -> 7625560 bytes save-temps/410.bwaves.tar.xz | Bin 0 -> 53080 bytes .../results.csv => save-temps/416.gamess.tar.xz | Bin 15456163 -> 17149476 bytes save-temps/429.mcf.tar.xz | Bin 0 -> 71796 bytes save-temps/433.milc.tar.xz | Bin 0 -> 370604 bytes save-temps/434.zeusmp.tar.xz | Bin 0 -> 530532 bytes save-temps/435.gromacs.tar.xz | Bin 0 -> 2368288 bytes save-temps/436.cactusADM.tar.xz | Bin 0 -> 1833968 bytes save-temps/437.leslie3d.tar.xz | Bin 0 -> 176528 bytes save-temps/444.namd.tar.xz | Bin 0 -> 674188 bytes save-temps/445.gobmk.tar.xz | Bin 0 -> 2723592 bytes .../size.csv => save-temps/447.dealII.tar.xz | Bin 11682457 -> 11643184 bytes save-temps/450.soplex.tar.xz | Bin 0 -> 1472664 bytes save-temps/453.povray.tar.xz | Bin 0 -> 2672576 bytes save-temps/454.calculix.tar.xz | Bin 0 -> 3557816 bytes save-temps/456.hmmer.tar.xz | Bin 0 -> 988732 bytes save-temps/458.sjeng.tar.xz | Bin 0 -> 322344 bytes save-temps/459.GemsFDTD.tar.xz | Bin 0 -> 640068 bytes save-temps/462.libquantum.tar.xz | Bin 0 -> 116332 bytes save-temps/464.h264ref.tar.xz | Bin 0 -> 3324868 bytes save-temps/465.tonto.tar.xz | Bin 0 -> 8355464 bytes save-temps/470.lbm.tar.xz | Bin 0 -> 52176 bytes save-temps/471.omnetpp.tar.xz | Bin 0 -> 1522300 bytes save-temps/473.astar.tar.xz | Bin 0 -> 160528 bytes save-temps/481.wrf.tar.xz | Bin 0 -> 9113560 bytes save-temps/482.sphinx3.tar.xz | Bin 0 -> 586712 bytes .../results.csv => save-temps/483.xalancbmk.tar.xz | Bin 15456163 -> 17713580 bytes 126 files changed, 1686204 insertions(+), 1742116 deletions(-) create mode 100644 save-temps/400.perlbench.tar.xz create mode 100644 save-temps/401.bzip2.tar.xz create mode 100644 save-temps/403.gcc.tar.xz create mode 100644 save-temps/410.bwaves.tar.xz copy 10-check_regression/csv-results-vs-prev-0/results.csv => save-temps/416.games [...] create mode 100644 save-temps/429.mcf.tar.xz create mode 100644 save-temps/433.milc.tar.xz create mode 100644 save-temps/434.zeusmp.tar.xz create mode 100644 save-temps/435.gromacs.tar.xz create mode 100644 save-temps/436.cactusADM.tar.xz create mode 100644 save-temps/437.leslie3d.tar.xz create mode 100644 save-temps/444.namd.tar.xz create mode 100644 save-temps/445.gobmk.tar.xz copy 10-check_regression/csv-results-vs-first-0/size.csv => save-temps/447.dealII. [...] create mode 100644 save-temps/450.soplex.tar.xz create mode 100644 save-temps/453.povray.tar.xz create mode 100644 save-temps/454.calculix.tar.xz create mode 100644 save-temps/456.hmmer.tar.xz create mode 100644 save-temps/458.sjeng.tar.xz create mode 100644 save-temps/459.GemsFDTD.tar.xz create mode 100644 save-temps/462.libquantum.tar.xz create mode 100644 save-temps/464.h264ref.tar.xz create mode 100644 save-temps/465.tonto.tar.xz create mode 100644 save-temps/470.lbm.tar.xz create mode 100644 save-temps/471.omnetpp.tar.xz create mode 100644 save-temps/473.astar.tar.xz create mode 100644 save-temps/481.wrf.tar.xz create mode 100644 save-temps/482.sphinx3.tar.xz copy 10-check_regression/csv-results-vs-prev-0/results.csv => save-temps/483.xalan [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[binutils-gdb] branch master updated (c064fab2476 -> 7fd14d6f580)

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 c064fab2476 sim: mn10300: minimize mn10300-sim.h include in sim-main.h new e5603897836 sim: v850: drop redundant define new c743e42e221 sim: v850: reduce extra header inclusion to igen files new 7fd14d6f580 sim: unify sim-signal.o building The 3 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: sim/Makefile.in | 17 +++++++++++------ sim/common/local.mk | 2 +- sim/common/sim-signal.c | 3 ++- sim/v850/sim-main.h | 8 ++++---- 4 files changed, 18 insertions(+), 12 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (e4a4219ccb -> 2d570da82f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards e4a4219ccb 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 71e339982c 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards d6e80013b7 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 8bdc58b3e5 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 231b110024 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards c89c4fc199 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 063a8c0a80 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 5c770f4e54 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 93e75e0059 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards 70758bf78a 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards f2a277e4fb 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards e1bb3a511f 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards ba2f494737 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 565b5a587f 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards f460f7e463 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 968f71c885 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 9bc4c019d1 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 8256f2dfd2 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 9b39a93139 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 0be70d0155 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 5c15f56e15 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 0e9bd3bbc0 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 424092cc0e 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards bb0ec66345 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards cb933ea05f 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 68eb1f894e 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards ff720cdcea 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards bd94f2a473 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards e6be2190b0 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards e8e01de37e 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards af21de8fa5 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards d3fe112b5f 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards acc696bfe8 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards b6d7c83dbc 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards dbe212d4e5 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 0183bab5ea 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 83d36821c4 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 1f97056640 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 447e3127fb 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 2e5062544e 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards b3d63c1501 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 392c3a82cf 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 0f0f9eedc4 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 321331da03 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 2aa2edd48b 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards cf11d54ff5 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards b8daed9b22 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards d312a45404 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 36a0b9882f 321: force: #2055: 7: Success after gdb: 2 commits discards 5aa3ec64bd 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 595fc82824 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 99ce89b4ca 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 8bc03102e8 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards 5c1b4662c8 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 8b78d294cd 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 039b1da1ba 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 04121c2cab 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 68a2c92579 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 515945a0a7 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 73b90ab387 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 883bbb5a5d 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 7fac289a30 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards ee6af4f790 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards b7bd53d342 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 9eb8f0cc80 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards 2e212b1180 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 7b258300d9 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 47676d0174 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 7c3d0fcea1 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards b1b4d39ceb 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards efee2a62de 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 01c8c0cf96 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards c777f842f1 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 566c1f43eb 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards e02721a58f 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards e09d3ec8b2 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards ffce617b43 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards d6c33699cb 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 612d575e16 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards f49c29351b 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 559ab7ef4b 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards 5457f9f38b 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 60e319a69b 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 77488fa129 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards 303b43b590 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards d85782dee7 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards 874eb55a31 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards c44d62f707 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards 0b36d1d52a 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards a0b3c0198b 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards b456ecd2ef 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards f6465cc1c6 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 5a857095be 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 2496e47bd8 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards e537f40933 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 932f841a10 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards afe82edd7a 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 0f52744f4c 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 006e55227b 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards a84bf2e435 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 7ca1d4fc2b 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 6e2fe82d51 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new afeeac95b5 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 278b778343 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new 1760b7c308 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 938d1a3fee 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new be7a6ca97f 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 7bcd9e2fe3 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 900034d387 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 239abc34ce 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 020ed0e970 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 892a136708 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new b64e783a35 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 76ee22aa6f 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new ad22f2b786 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new 344243db8c 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 99caa67ad7 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new c263448ee3 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new a6e90b1894 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 1036b9ba7a 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new 0385f0d2cd 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new a26616ac08 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new fc8e056c1a 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 9c91e082e7 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new 3ada521cb6 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 16040e16f1 293: onsuccess: #2022: 7: Success after gcc: 2 commits new d41231c5b8 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 3c2e0f73a2 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new 9a50c2b7d5 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 17bd2c1b66 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new f9f88d5be1 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 3da3a304f3 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 6b4ebaae22 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 9576862c4b 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new c19c550b8a 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new c0b770c1cc 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 761c1044bd 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new 68c8dcd6f7 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 7bea32d35c 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 8d6d1853e2 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new bb8897f79b 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new a014884162 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new d7677577c4 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 014f3a46f0 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 3adade356c 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new ed678c58ad 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new fe95446c45 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 5ee8575249 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new b8946443e6 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 291a4270ef 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 773b2772df 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 5b0957eb84 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 2e0ecc2423 320: onsuccess: #2050: 7: Success after gcc: 4 commits new e3e6580211 321: force: #2055: 7: Success after gdb: 2 commits new f0e7538229 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 8510c63b04 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new def8f64d88 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new d81e1beb68 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 6215530ab1 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new d6e1af98d6 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 727d0e8f6d 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new b3b808774e 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 3771398987 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new e884c4ea0f 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 9b0e725822 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 4a1cc9fa5b 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new ba8ee2662b 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new 4daad51728 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new a931a07f1c 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 11e7e8da58 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 8fa1cd2cf5 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new b8b841b905 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 51ae09d3b1 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 5b75665ae9 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new b9c17cb181 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 96e40ab3a4 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new cc79376597 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new fe3e771c12 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 09f15b2c55 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 2941e10b2d 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 974476b0ce 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new 80533cfb56 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 2a0293d0bf 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 14daac9d17 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new e1d391be6a 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new 5f7d734eed 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new a239144a58 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new cb3132fdde 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 45db2a7572 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new ee8c128cfa 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new 42b6e09617 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 067d503e66 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new 4a251f42e9 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 37e9050dee 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 07b7c17cf0 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 9a535f3362 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 1dd06ab24f 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 016f1b9dec 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 1f160cd031 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new ae5d418294 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 7f3be7d37b 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new f48ecb99ac 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 2d570da82f 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e4a4219ccb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 31700 -> 32172 bytes 05-build_abe-stage1/console.log.xz | Bin 92820 -> 92356 bytes 07-build_abe-linux/console.log.xz | Bin 8608 -> 8936 bytes 08-build_abe-glibc/console.log.xz | Bin 236476 -> 237220 bytes 09-build_abe-stage2/console.log.xz | Bin 228176 -> 229100 bytes 10-build_abe-gdb/console.log.xz | Bin 39096 -> 39148 bytes 11-build_abe-qemu/console.log.xz | Bin 31572 -> 31860 bytes 12-check_regression/console.log.xz | Bin 5288 -> 5072 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 ++++++++++++------------- 22 files changed, 65 insertions(+), 65 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch releases/gcc-12 updated (937b0f05910 -> 61ef24af3ce)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 937b0f05910 libstdc++: Avoid recursion in __nothrow_wait_cv::wait [PR105730] new 61ef24af3ce Daily bump. 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: gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 10 ++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch releases/gcc-11 updated (ed58809ea1a -> 5f30fae901c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from ed58809ea1a libstdc++: Unblock atomic wait on non-futex platforms [PR106183] new 5f30fae901c Daily bump. 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: gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 14 ++++++++++++++ 2 files changed, 15 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

Jump to page: