Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (251fcd0fdd -> 17efaa0f9d)

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-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 251fcd0fdd 40: onsuccess: #433: all: Success after binutils/llvm/linux/ [...] new 17efaa0f9d 41: onsuccess: #434: all: Success after binutils/llvm/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 1760 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31832 -> 30948 bytes 04-build_kernel_llvm/console.log.xz | Bin 64664 -> 65244 bytes 05-build_abe-qemu/console.log.xz | Bin 31952 -> 32040 bytes 06-build_linux/console.log.xz | Bin 3112 -> 3112 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4356 -> 4432 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (e04c3b8656 -> 954f880616)

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 e04c3b8656 186: onsuccess: #938: 1: Success after binutils/gcc/linux/gl [...] discards 6b73f68509 185: onsuccess: #937: 1: Success after binutils/gcc/linux/gd [...] discards c939f5795a 184: onsuccess: #936: 1: Success after binutils/gcc/linux/gl [...] discards fa601320c8 183: onsuccess: #935: 1: Success after binutils/gcc/linux/gl [...] discards cb92803f7a 182: onsuccess: #933: 1: Success after binutils/gcc/linux/gl [...] discards 3527922b00 181: onsuccess: #932: 1: Success after binutils/gcc/linux/gl [...] discards 5a94150f2f 180: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 1814eeeda6 179: onsuccess: #930: 1: Success after binutils/gcc/linux/gl [...] discards 0d2fb21fae 178: onsuccess: #929: 1: Success after binutils/gcc/linux/gl [...] discards cf032c869c 177: onsuccess: #928: 1: Success after binutils/gcc/linux/gl [...] discards a9729be671 176: onsuccess: #927: 1: Success after binutils/gcc/linux/gl [...] discards 260ff7f076 175: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards d6dc895ae2 174: onsuccess: #925: 1: Success after binutils/gcc/linux/gd [...] discards 9de3b8ed97 173: onsuccess: #924: 1: Success after binutils/gcc/linux/gl [...] discards 05d91e3bda 172: onsuccess: #923: 1: Success after binutils/gcc/linux/gd [...] discards ca0bf3a403 171: onsuccess: #922: 1: Success after binutils/gcc/linux/gl [...] discards 633211b52b 170: onsuccess: #921: 1: Success after binutils/gcc/linux/gl [...] discards d8dd97e287 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 59a134daac 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] discards 204db70de7 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] discards 0efc40b18a 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] discards fff77dbb8f 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 608daeafef 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] discards 6ebfb95043 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] discards e6aeddb053 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards 798d021dad 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 72177a7f82 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 9b67a36d30 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 946b53b14e 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards 1cf0a73268 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards 6e6e679740 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards 528ecd4db6 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards d87af7163d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards f0aa76a35b 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards ee6e663e91 152: onsuccess: #903: 1: Success after linux: 22 commits discards 20bc4200fe 151: onsuccess: #902: 1: Success after glibc: 8 commits discards ccfeca8191 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 9bf3270900 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 32a7109035 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 00808725ac 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 175c1688cc 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 539b251c1a 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards dc3047d85d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards f8c29fc897 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards ab618504a0 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards d11d4fad13 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 0a22afe18e 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards b50af8fb9f 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 004a13eefa 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 3c0c2064c8 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 10e4bec2f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 1fa68012e4 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 24288e9ed9 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 3b78c66805 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 415bb4e5d2 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 599eee2cff 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 95a69c95a2 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 8eba52f092 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 6ee1ceba13 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 2f0b4577f5 127: onsuccess: #874: 1: Success after linux: 219 commits discards 8bf6af18b8 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 6295e2b175 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 06617d1164 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 624af52ca9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 336e2b4ef9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards ce0bbd51a5 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards c5d036f654 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 030252ed86 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 3a1346dad9 118: onsuccess: #863: 1: Success after linux: 12 commits discards 537d2c18d6 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 20f365d50d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 31dcadc101 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 282e7815d3 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 2a50aa4609 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 82babda646 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 3b6ddc2a66 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 1bc4b95378 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 4abfb8c48f 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 0ce6a22931 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 72573e62af 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 666b7c0700 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 1e663386ab 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 4096db34a3 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 37339bc061 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards a36cb2b866 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 58560ddc0f 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 6b31a71868 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards d799d2768f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 67cc784d57 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ed1b0ca0e7 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 9162574e2e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 43b2903299 95: onsuccess: #835: 1: Success after binutils: 3 commits discards e0d5b89c52 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 3ca40b0498 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0a43e5ea9e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 2ddaf57022 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards ce5f67d83b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards efaae231d0 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards e9e9ac7681 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 802e16558e 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards af6794dc2d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 1080bf4ccb 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 4905b0220a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 23017f2b05 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 192bca072b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0992cb084f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 0411e1cdfb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 2a7fe01483 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new ee861cbce7 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 4fe565c7c3 94: onsuccess: #832: 1: Success after binutils: 5 commits new 0d51d26460 95: onsuccess: #835: 1: Success after binutils: 3 commits new 679abc9661 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 2797c2033d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 412e3c29ed 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new a27986151b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 632734271f 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new aecb016c3c 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 4d5b9e5c80 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new cd49ae042b 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new d79e03fdc4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 594ac0f668 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 20e16ff9d7 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 8d33aa7546 107: onsuccess: #849: 1: Success after binutils: 5 commits new b69b402d4a 108: onsuccess: #850: 1: Success after gcc: 2 commits new b40566048a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new c524e2f032 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 2e26058e4e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 3cc4913a73 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new d641bff5ce 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 03aea6d7d1 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 1f5a378c25 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 35e607bec6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 21f1b2749f 117: onsuccess: #861: 1: Success after binutils: 18 commits new 0c891e0b8f 118: onsuccess: #863: 1: Success after linux: 12 commits new bc423a6d5e 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new b7de7ea939 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 42f28fae87 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 6689eb3074 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new b14e48163c 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new cde6b45aef 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 6596b5b24f 125: onsuccess: #871: 1: Success after binutils: 26 commits new 9f928aa487 126: onsuccess: #873: 1: Success after glibc: 2 commits new 8d3f5ddd88 127: onsuccess: #874: 1: Success after linux: 219 commits new 9af3ba7695 128: onsuccess: #876: 1: Success after binutils: 12 commits new ed843d8682 129: onsuccess: #878: 1: Success after linux: 3008 commits new 374db09d55 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 6117421f04 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 82ceb0adaa 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 1559125750 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 60fff13b2e 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new c9dfa4d77f 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 17a785508c 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 5a05684c40 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new af009a60d3 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new f3e70396b0 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new eafc418596 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 0a328a756b 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 8a70d2a6e0 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 4ca71364f0 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 49e8fe7e85 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 9092ae2a6c 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 23b4588169 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new d13b944bb6 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new a77b222fbe 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 80c59694d2 149: onsuccess: #899: 1: Success after binutils: 15 commits new 8695698d43 150: onsuccess: #900: 1: Success after gcc: 11 commits new fdadaa5fda 151: onsuccess: #902: 1: Success after glibc: 8 commits new 0f609b611e 152: onsuccess: #903: 1: Success after linux: 22 commits new 52861e3949 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new c88ea8d054 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 7e708af52d 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new bad5be1def 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new 3f6e0d6983 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 8255b5ba39 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new f664c568d8 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new f6d7982a85 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 8f1c2fc8c9 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new d14a2e7cf6 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new 929a4b6abd 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] new db8ff2f72d 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] new 9178d3b34d 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new b7ff73b5e3 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] new e399c156da 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] new d78244e652 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] new 86c57d12f3 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new b983edd8e4 170: onsuccess: #921: 1: Success after binutils/gcc/linux/gl [...] new fbfbbdd84f 171: onsuccess: #922: 1: Success after binutils/gcc/linux/gl [...] new 967a5a6140 172: onsuccess: #923: 1: Success after binutils/gcc/linux/gd [...] new fdabcd11b6 173: onsuccess: #924: 1: Success after binutils/gcc/linux/gl [...] new e7a0fb2dda 174: onsuccess: #925: 1: Success after binutils/gcc/linux/gd [...] new 7b7cc5a382 175: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new e378ec182f 176: onsuccess: #927: 1: Success after binutils/gcc/linux/gl [...] new 8223c917cf 177: onsuccess: #928: 1: Success after binutils/gcc/linux/gl [...] new 5728e00b2c 178: onsuccess: #929: 1: Success after binutils/gcc/linux/gl [...] new 6d582e5187 179: onsuccess: #930: 1: Success after binutils/gcc/linux/gl [...] new 1f638a39c5 180: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new d0a20784b5 181: onsuccess: #932: 1: Success after binutils/gcc/linux/gl [...] new 6bf9937537 182: onsuccess: #933: 1: Success after binutils/gcc/linux/gl [...] new c8c94fca27 183: onsuccess: #935: 1: Success after binutils/gcc/linux/gl [...] new ec43ebad37 184: onsuccess: #936: 1: Success after binutils/gcc/linux/gl [...] new 1e2844a8b7 185: onsuccess: #937: 1: Success after binutils/gcc/linux/gd [...] new 613f7e653a 186: onsuccess: #938: 1: Success after binutils/gcc/linux/gl [...] new 954f880616 187: onsuccess: #939: 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 (e04c3b8656) \ 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 1764 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 38660 -> 38968 bytes 04-build_abe-gcc/console.log.xz | Bin 214284 -> 214124 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 244624 -> 244448 bytes 08-build_abe-gdb/console.log.xz | Bin 38596 -> 38524 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2716 -> 2888 bytes 11-check_regression/console.log.xz | Bin 6764 -> 7812 bytes 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 296 +- 12-update_baseline/console.log | 58 +- 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 | 38 +- sumfiles/g++.log.xz | Bin 3761260 -> 3732032 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 3240844 -> 3241048 bytes sumfiles/gcc.sum | 4900 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1085560 -> 1088348 bytes sumfiles/gfortran.sum | 86 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235252 -> 235248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462812 -> 456424 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 3009 insertions(+), 2567 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (a7af40e369 -> 7b7bb9f3d5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards a7af40e369 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 0e3c83bcc4 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 3abbbccf0a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 0760f2ac6e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 8e62f715fd 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 253ae2c402 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards fa8678f78a 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 62a33d46e0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards e53449b702 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 7057df565d 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 0a2690d432 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards a55f2aca0f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 8bac394bd9 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 676746667d 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards a16caa9cf3 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 9c51358a54 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 1483a0962b 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards f0c8a5aedb 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards ec72f2d75f 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 1bc37e3eb8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 1487ddcfe7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 029c2d8d42 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards b9885757a5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards b2236a28d0 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards d3fc3f5bc7 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 8f54fa26c5 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 88117ed59c 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 77ead7ba3b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 5da64fe4e5 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 9fcfb4b057 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards f683f39b67 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 532e828c52 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards faa7bdf216 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 5e76a9ae54 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards c220405985 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9dc6bc3d85 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards b8058faa75 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards c1838be17b 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards c3304d95e7 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 5ae4151e68 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 9687fd383a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 90570d089b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 6e26fb2734 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 456decf138 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 272f2c97ee 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d2ceed6f7e 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 0113361e0c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ca719476f5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards f75dd51349 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f2cfb1ea0d 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 73a9676a28 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards ecbdfee09a 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 41d838e3f0 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards a4e0432ec0 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 811d8ec6ce 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards e77b076844 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d7e1525f32 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards afbd64d2f1 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 9444f6a5a4 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 5d023de303 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards eaea5621f8 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 80aa266ce8 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ae53e22c94 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards e01b8b7506 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards bd94a609ee 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards b62db5e393 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 2d980cdbed 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 93be0a932b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards e5e5f00d5a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 6b670ce323 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards cfdb4a4656 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 06224eca96 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 5faf509383 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 42bc6f1eda 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 355392176d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards fef0a9d3a2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ff8a8aacaa 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 98914b35a1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 2d25c47f8d 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 93a044241c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 902b557df8 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 9d0dfec783 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 7277881781 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 989b4fef40 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 23dd61e9bf 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards f17b28de14 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 633975c44d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 8d06762f88 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1e28e5d69f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 19bb7f830f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards c8183f9521 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 0c135a4280 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards df4189a200 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards d554a70724 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards feb9b4247a 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 6cea333c45 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a5a765a8bb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 084b565790 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 60cb6e7003 295: onsuccess: #2545: 1: Success after linux: 10 commits discards b7d480283e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 68edefb239 293: onsuccess: #2542: 1: Success after gcc: 5 commits new f70f0b0947 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 39bb2f7374 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 9c92074e87 295: onsuccess: #2545: 1: Success after linux: 10 commits new 9d136a9030 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 3d36b0a815 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 4f1d0901e6 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 0473f1b041 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new a630849dfd 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new c5db1ac50e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new e5358d45ab 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 3ae7f8791f 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new bc0ebe6102 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 5a6a7ca8d4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new a84688d9f9 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 0f30c89602 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 49d2ac0282 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b0909dec16 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new ee864d6d27 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new fde83f40fa 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 0cf2e7d66a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new d3db9d8bb0 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 7859f06220 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new f94318a154 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 42dbd7ce5f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new ecffcceaff 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new edefa32d9d 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new e4c5c15353 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 5e00069cfd 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 2d8df25eea 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 5bca365da2 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 0b7e79d3a5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 18fed1e934 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new b91acde4cf 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 7461601ec3 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new a76c7fa646 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new d676d07a60 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 690714c500 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new fad5fe811d 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new a4969f1a73 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 50e3c683a6 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a666661cdf 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 40b8448afd 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 02970ac3f4 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 716ffc723c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e4178ca5e6 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new e36bc7a6a5 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 19f862fb23 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 0342ec2005 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 7bf117de7b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new a4efee4adb 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new e9ce30a4e8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 2fb9ae7550 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6d51486b96 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 38f1dd9768 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new abfffb4c23 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 509c6d17e2 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 583e43836b 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new ef39328c3f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new e453601ecb 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new ff3ee161ce 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 3bbaa9ee6f 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b8d124feda 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 26acccc0d8 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 92c3183abd 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 99b942306b 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 890d033d0f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 45cec3fcfc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 42047a6e6b 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 1f8767812f 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 3b1b622cc7 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 3bbb4e5344 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 5b1317cf0d 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 99a450d1c2 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 6e21e586a4 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 5b694487a6 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 7f96ce326f 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 1bb08f0b99 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new f86e0f5e72 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new ee6350e71f 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 46f2612c70 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new adf5abdfbf 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new d25f1dc4b8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new a82ba39e56 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 345d97f17e 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 9ab9bf4aaa 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new befd500734 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 7f525037e7 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 8d22af4f29 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 756c8ff14d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 08ad079d39 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new e8f1e50a19 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new deb066d9f2 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 2a48751f85 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new c018ba8d61 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 63c02d3e99 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 655cb77f65 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new fbea9f62c5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new c55c25b5ea 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 822ff6e63b 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 79a10e2911 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new c6159504f3 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 7b7bb9f3d5 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/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 (a7af40e369) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31284 -> 31120 bytes 04-build_abe-stage1/console.log.xz | Bin 73516 -> 72968 bytes 06-build_abe-linux/console.log.xz | Bin 8932 -> 8896 bytes 07-build_abe-glibc/console.log.xz | Bin 245100 -> 244620 bytes 08-build_abe-stage2/console.log.xz | Bin 205364 -> 204124 bytes 09-build_abe-gdb/console.log.xz | Bin 38676 -> 38484 bytes 10-build_abe-qemu/console.log.xz | Bin 32572 -> 32512 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3944 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3072 -> 2800 bytes 13-check_regression/console.log.xz | Bin 6400 -> 6580 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 23 + 13-check_regression/mail-body.txt | 78 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 89 +- .../{mail-body.txt => results.regressions} | 79 +- 14-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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 80 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 43 + sumfiles/g++.log.xz | Bin 3408192 -> 3377912 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3014212 -> 3019984 bytes sumfiles/gcc.sum | 4168 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1033620 -> 1037340 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217540 -> 217572 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429844 -> 434376 bytes sumfiles/libstdc++.sum | 59 +- 43 files changed, 2448 insertions(+), 2369 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (73%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O2 updated (c655680691 -> 151a369e97)

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-arm-master-O2 in repository toolchain/ci/base-artifacts. from c655680691 73: onsuccess: #52: 1: [TCWG CI] No change after gcc: 275 commits new 151a369e97 74: onsuccess: #53: 1: [TCWG CI] No change after glibc: 14 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 1968 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31628 -> 31484 bytes 04-build_abe-stage1/console.log.xz | Bin 93648 -> 93732 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 237908 -> 237868 bytes 08-build_abe-stage2/console.log.xz | Bin 217948 -> 219040 bytes 09-benchmark/benchmark-build.log | 116 +- 09-benchmark/benchmark.log | 114 +- 09-benchmark/console.log.xz | Bin 3928 -> 3892 bytes 10-check_regression/console.log.xz | Bin 16336 -> 16556 bytes .../csv-results-vs-first-1/md5sum.csv | 2893 +- .../csv-results-vs-first-1/perf.csv | 3437 +- .../csv-results-vs-first-1/results.csv | 19954 +- .../csv-results-vs-first-1/size.csv | 534395 ++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 24352 +- .../csv-results-vs-first-1/vect.csv | 38 +- .../csv-results-vs-prev-0/md5sum.csv | 2754 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3379 +- .../csv-results-vs-prev-0/results.csv | 11809 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 565935 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 28274 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 42 +- .../csv-results-vs-prev-1/md5sum.csv | 2893 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3437 +- .../csv-results-vs-prev-1/results.csv | 19954 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 534395 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 24352 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 38 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3217 +- 10-check_regression/results-vs-first-internal.csv | 247 +- 10-check_regression/results-vs-first.csv | 247 +- 10-check_regression/results-vs-first.log | 1358 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 5 +- 10-check_regression/results-vs-prev-full.csv | 3485 +- 10-check_regression/results-vs-prev-internal.csv | 251 +- 10-check_regression/results-vs-prev.csv | 251 +- 10-check_regression/results-vs-prev.log | 1572 +- 10-check_regression/skipped-symbols.txt | 16 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/glibc_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results_id | 2 +- 90 files changed, 890327 insertions(+), 903517 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[newlib] branch master updated (588624da2 -> 1387ea9f9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository newlib. from 588624da2 Cygwin: regex: convert wchar_t to wint_t new 1387ea9f9 Cygwin: dumper: also link with libzstd, as libbfd may require it 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: .appveyor.yml | 1 + .github/workflows/cygwin.yml | 1 + winsup/configure.ac | 10 ++++++---- winsup/doc/faq-programming.xml | 2 +- winsup/utils/Makefile.am | 7 ++----- 5 files changed, 11 insertions(+), 10 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[newlib] branch main updated (588624da2 -> 1387ea9f9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch main in repository newlib. from 588624da2 Cygwin: regex: convert wchar_t to wint_t new 1387ea9f9 Cygwin: dumper: also link with libzstd, as libbfd may require it 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: .appveyor.yml | 1 + .github/workflows/cygwin.yml | 1 + winsup/configure.ac | 10 ++++++---- winsup/doc/faq-programming.xml | 2 +- winsup/utils/Makefile.am | 7 ++----- 5 files changed, 11 insertions(+), 10 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (5bed9dc992a -> 81aa19c303c)

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 5bed9dc992a [gdb/testsuite] Add xfail in gdb.python/py-record-btrace.exp new 81aa19c303c Do not cast away const in agent_run_command 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: gdb/linux-nat.c | 7 ++----- gdbserver/server.cc | 5 +++++ gdbserver/tracepoint.cc | 2 +- gdbsupport/agent.cc | 14 ++++++++------ gdbsupport/agent.h | 2 +- 5 files changed, 17 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (34b9cf9862 -> 7a3046da5c)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 34b9cf9862 195: onsuccess: #620: 6: Success after binutils/gcc/linux/gl [...] discards a2e19fd32c 194: onsuccess: #619: 6: Success after binutils/gcc/linux/gd [...] discards 99a994127a 193: onsuccess: #618: 6: Success after binutils/gcc/linux/gl [...] discards a597b5d30a 192: onsuccess: #617: 6: Success after binutils/gcc/linux/gl [...] discards 39ea4460f2 191: onsuccess: #615: 6: Success after binutils/gcc/linux/gl [...] discards 3ebce7fc98 190: onsuccess: #614: 6: Success after binutils/gcc/linux/gl [...] discards 4b64216148 189: onsuccess: #613: 6: Success after binutils/gcc/linux/gl [...] discards 7e98c50323 188: onsuccess: #612: 6: Success after binutils/gcc/linux/gd [...] discards f456ff1820 187: onsuccess: #611: 6: Success after binutils/gcc/linux/gl [...] discards 9f4522aab4 186: onsuccess: #610: 6: Success after binutils/gcc/linux/gl [...] discards 0e864cdcf7 185: onsuccess: #609: 6: Success after binutils/gcc/linux/gl [...] discards 1c4aaff57e 184: onsuccess: #608: 6: Success after binutils/gcc/linux/gl [...] discards a724f8b97e 183: onsuccess: #607: 6: Success after binutils/gcc/linux/gd [...] discards 79262c76b9 182: onsuccess: #606: 6: Success after binutils/gcc/linux/gl [...] discards 939fa22070 181: onsuccess: #605: 6: Success after binutils/gcc/linux/gd [...] discards b699b13a4d 180: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] discards 54a1be1423 179: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] discards feba00ec6b 178: onsuccess: #602: 6: Success after binutils/gcc/linux/gd [...] discards 70ddcf8b51 177: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] discards 0ede38d449 176: onsuccess: #600: 6: Success after binutils/gcc/linux/gd [...] discards 5c945a8d04 175: onsuccess: #599: 6: Success after binutils/gcc/linux/gd [...] discards 6d5cc7c2ab 174: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] discards ad28f53d6e 173: onsuccess: #597: 6: Success after binutils/gcc/linux/gl [...] discards 636825b3c4 172: onsuccess: #596: 6: Success after binutils/gcc/linux/gl [...] discards 545518db89 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] discards cde610761f 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] discards a874e79d60 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] discards aaf0116959 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] discards c3c652be50 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] discards 5a038edadf 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] discards 059616a670 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] discards b0fd1f388b 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] discards 346b44cffc 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards 9471089132 162: onsuccess: #579: 6: Success after gcc: 11 commits discards daa5453750 161: onsuccess: #578: 6: Success after binutils: 15 commits discards e116e74509 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards 56ef9fbd9e 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards 0b19a536f5 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards 8b7c5cc5b1 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 8b5af6d1ed 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards dd1a50bdf1 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards 6613452aa9 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards db451d1621 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards f770ae032e 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards 3cb65cbbc2 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards b64d9d77fd 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards 4b093f1227 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 5a438b5b3c 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards 57a6dc3fe2 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards b68231256a 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards 857bea4948 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards 0083a43120 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards f32a56488c 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards 3f561b1b71 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards d010c4d0f1 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards c4e64c2062 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 56eace0d57 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards 236e4b90dd 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards c61e25237a 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards 86acbc8285 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards ac4035406f 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards 8c9baa7eb6 134: onsuccess: #544: 6: Success after binutils: 18 commits discards b3c14c8c8e 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards b826799633 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards f88a963e1c 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards 26e8ef8354 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards 0a138ec611 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards f7f768badf 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards 97aeec75dc 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 12fd58e645 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 06d6c556b3 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards b77e86818f 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 6ce03d9582 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards 42052f7200 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards a4a986e943 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 2682a4a5e3 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards bcdf8998eb 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards 1ebaf7f235 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards dcb22742b9 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards 98b0d5fd4c 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards 1cd23c260b 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards d9d52591d2 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 6d2dec347a 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 36cf26b043 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 0843726031 111: force: #520: 6: Success after gcc: 9 commits discards bc2d2988f1 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 79590f58ab 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards e969906dea 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 5c3797e623 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards 45d488e387 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 82758b3a86 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards 63c02f890f 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 5724b58b44 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 01a229f84c 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 716b27706e 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards cfac3f5e4b 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards a518a45012 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards e4c76d5613 98: force: #504: 6: Success after gcc: 18 commits discards b18ba0e9ac 97: onsuccess: #503: 6: Success after linux: 11 commits discards 0125c0deb6 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 1223e2ee18 95: onsuccess: #500: 6: Success after binutils: 8 commits new 8af6d1cb13 95: onsuccess: #500: 6: Success after binutils: 8 commits new 1096746946 96: onsuccess: #502: 6: Success after glibc: 10 commits new f1286829d6 97: onsuccess: #503: 6: Success after linux: 11 commits new cfe61c7196 98: force: #504: 6: Success after gcc: 18 commits new f905b1086d 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new abd5f5c43a 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 5ef6d4bf95 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 5d9dd12ced 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 59eb7142d6 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 05e3d2f367 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 296bccc552 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new 0814d974c2 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new b64ec53640 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new bf4a44681f 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new afef9dff1b 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 0f6498d98a 110: onsuccess: #518: 6: Success after binutils: 5 commits new de45a760bf 111: force: #520: 6: Success after gcc: 9 commits new 36ec330b81 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new c94b710356 113: onsuccess: #522: 1: Success after gcc: 12 commits new 5d7f5ecb65 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 82129e304b 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new c1b30ac066 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new ea1a42ce11 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new 922e469c65 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new 1bc0762bad 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new 928862c0d1 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new 10329a49a9 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 3bc4a67c33 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new 04c39eff25 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new 68a1bbf227 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new e7b50fc884 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new d26b04136d 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 3578e1e1a7 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 0f0d6cd06a 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new afad57e9b7 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new e70d50a116 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new 0121fd9989 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new c7aa72857e 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 422ae63d53 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new 47a8702fab 134: onsuccess: #544: 6: Success after binutils: 18 commits new faffe2dca8 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new a35e496ff8 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new f9f7765f1e 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new f55c14acd6 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 4e903a1c4f 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new 66722202d8 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 9dcd79cd4f 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new 1140529cc3 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 8ab3ad6c7d 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new e37c452754 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new 5e1f7f61f3 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new c0e82faa91 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new ff57491880 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new 7d996ab968 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new abc1b420bb 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 5c583a7220 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new 6b26f03c52 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new 2cd17e0abb 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new 17e86ef3dc 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 33a832730e 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 5f27b247b6 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new 6e99806eaf 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new c9c4106abd 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new 9f49f42238 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new 7a051bd3a0 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new 1da311e3c4 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new ee2f767858 161: onsuccess: #578: 6: Success after binutils: 15 commits new a4476f1448 162: onsuccess: #579: 6: Success after gcc: 11 commits new c4b3dc4b51 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new 6551494363 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] new 8cf4740245 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] new f1e3b914b7 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] new 6f30ba1e32 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] new 178166a90e 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] new 7bea0bcb5b 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] new 59ef161ad5 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] new 2498729b3e 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] new 9daae9c2b3 172: onsuccess: #596: 6: Success after binutils/gcc/linux/gl [...] new 025d0341fb 173: onsuccess: #597: 6: Success after binutils/gcc/linux/gl [...] new 226ba7bf37 174: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] new 054af9b5ca 175: onsuccess: #599: 6: Success after binutils/gcc/linux/gd [...] new b8b8a9c379 176: onsuccess: #600: 6: Success after binutils/gcc/linux/gd [...] new 81fc03b7af 177: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] new f8610faf41 178: onsuccess: #602: 6: Success after binutils/gcc/linux/gd [...] new b9d109d884 179: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] new 9236fe1051 180: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] new 662c280c0d 181: onsuccess: #605: 6: Success after binutils/gcc/linux/gd [...] new bc625444d7 182: onsuccess: #606: 6: Success after binutils/gcc/linux/gl [...] new 78a9d5151f 183: onsuccess: #607: 6: Success after binutils/gcc/linux/gd [...] new cde535be80 184: onsuccess: #608: 6: Success after binutils/gcc/linux/gl [...] new 8c2cff73bc 185: onsuccess: #609: 6: Success after binutils/gcc/linux/gl [...] new 56b6ae5b04 186: onsuccess: #610: 6: Success after binutils/gcc/linux/gl [...] new 6f527a0908 187: onsuccess: #611: 6: Success after binutils/gcc/linux/gl [...] new 641094f0a8 188: onsuccess: #612: 6: Success after binutils/gcc/linux/gd [...] new 6614f33b37 189: onsuccess: #613: 6: Success after binutils/gcc/linux/gl [...] new 65a8da038e 190: onsuccess: #614: 6: Success after binutils/gcc/linux/gl [...] new ddf81aa70e 191: onsuccess: #615: 6: Success after binutils/gcc/linux/gl [...] new 8eb9406bd8 192: onsuccess: #617: 6: Success after binutils/gcc/linux/gl [...] new 4f9acdbb14 193: onsuccess: #618: 6: Success after binutils/gcc/linux/gl [...] new 537b09304b 194: onsuccess: #619: 6: Success after binutils/gcc/linux/gd [...] new 0c92c67937 195: onsuccess: #620: 6: Success after binutils/gcc/linux/gl [...] new 7a3046da5c 196: onsuccess: #621: 6: 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 (34b9cf9862) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 52108 -> 52152 bytes 05-build_abe-gcc/console.log.xz | Bin 238788 -> 237224 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8360 -> 8848 bytes 08-build_abe-glibc/console.log.xz | Bin 235784 -> 235624 bytes 09-build_abe-gdb/console.log.xz | Bin 51352 -> 50564 bytes 10-check_regression/console.log.xz | Bin 4408 -> 4400 bytes 11-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (db02c13a3b -> b0c667ff52)

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 db02c13a3b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards d8edf22157 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 72ea92fc25 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 2bfb8070d3 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 196eb0ff71 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 4ca5bb6cd5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 4a7a08f448 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 1ffa95c3a6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 0f88a2cb16 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards ea3bce674b 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards b1235d2e79 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 3758e7a15d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards b0e1a2d18d 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 598f7b6149 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards e58b2a9c93 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 6e218611db 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards e27ded7949 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 25bbc8c7bc 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 09eba0a063 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 9be1ae5105 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards a53d6b13f2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards efa16e222e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 3018e9befa 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 1d59c72483 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 47e7ad35e8 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards ea6f181021 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 24683fe104 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards f91a559953 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards a8d81f46bc 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 95677d8f52 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 061a30de01 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 529a5024eb 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 9b215b512f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 6e4a98d8d7 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards c4e05e0679 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 82243b2cbe 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 219538348e 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards b1a6c9a153 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 8fed835360 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 9f705789f8 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards c3c8bd23f0 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards a6c98f170e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards dbe6863dab 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 8b85b410e2 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 3ee42182f7 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 7f8ae1f9a0 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards a043be0c68 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 72c0eb404b 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards f5b2e65348 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 0dd4882bfd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards e0d3f3664a 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards f47389d59a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards fcc78d439c 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 813a5cb539 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards e9df20a433 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 3371dda5e1 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 8b426cdf4c 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards ea6fd13a19 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards c5b71e6510 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 578e85c5aa 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 7a218e4e15 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards ee8fa7f357 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards b0c086cef1 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 106a9b0956 125: onsuccess: #614: 1: Success after linux: 12 commits discards 875325a4bb 124: onsuccess: #612: 1: Success after binutils: 18 commits discards a5dc8c757b 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards f9ce3760f7 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards aed7ea3c95 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 584542d10a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards a2187a45c7 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 3cc62179f0 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 7ccb574306 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 48ccbebe93 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 9ceac1f7a1 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 5929356dca 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 2f70d1506b 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 00af2491fb 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards c5b398bb21 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards ebf6a7361c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 38cdb13426 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards a88753f663 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards d66f7a13c7 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards b8b4a3359c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 204d57f2fd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 78d43d6198 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 4a3c6acace 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e33a20e5aa 102: onsuccess: #586: 1: Success after binutils: 5 commits discards d6bbb6a8e4 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards e24fd7164a 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 4488d464d0 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 0df8649dcc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards cde5e8c2ce 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 70fe77fb1e 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 9088b0c864 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 2ffd981946 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 170fe25f83 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 7ac28a2b80 92: onsuccess: #575: 1: Success after linux: 34 commits discards 3397ce8835 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 13f66cd52b 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 2db3f312c1 89: onsuccess: #570: 1: Success after linux: 11 commits discards 503b423b12 88: onsuccess: #569: 1: Success after glibc: 10 commits new 030ccb1cdf 88: onsuccess: #569: 1: Success after glibc: 10 commits new 50ae9531dd 89: onsuccess: #570: 1: Success after linux: 11 commits new 58f5008fa2 90: onsuccess: #572: 1: Success after binutils: 15 commits new a973dfed67 91: onsuccess: #574: 1: Success after glibc: 3 commits new 3e314ea829 92: onsuccess: #575: 1: Success after linux: 34 commits new b2a76ce97b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 6207688b9d 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 20a4ae4d80 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 6416d023f4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 15a9cec444 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new c9aea07307 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 644e3efb5f 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new f11e18dafd 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 2d40eefc0c 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 074aa57bfd 102: onsuccess: #586: 1: Success after binutils: 5 commits new e91ac0fbb4 103: onsuccess: #589: 1: Success after binutils: 3 commits new 95f572a900 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new a6ee5a00e4 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 44b96d3429 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new ae9aaae4cf 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 1b21224d2a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 0277375d6a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 54a1c285ef 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new b1313cf833 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new cc6d72cb3c 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new aadc489013 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 0062146411 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 26b06183fa 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 429250a2b7 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 59d936d2fb 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 37e5e44290 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 9b687a4f9e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 2d5cb7a31c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new deb933b139 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 13e618f680 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 87f364cd98 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new eacca464bf 124: onsuccess: #612: 1: Success after binutils: 18 commits new 0e7ce00529 125: onsuccess: #614: 1: Success after linux: 12 commits new de23a21a01 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new d2151d6a82 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new a6f819f265 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new a578c53b23 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 87d2160bf2 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 9ecc058c3c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 9d7914ba3b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 72a5d0d51a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 91f3a66b9d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 7606e4a881 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 0d339b14ce 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 327a5551ba 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new f63a2e1829 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 3ab9f2f13d 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new c8d8c9d240 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 571c39c4f5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 0d6f61a2d6 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 3b8c5880e7 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 801ac9f130 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 2200c3440d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 487812b573 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 68f14950ba 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new d2f3a30ab1 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 3394fa3970 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 1d13871b5e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 427a2e7798 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 1d354583e6 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 4d25c8be5f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 20f215f6e6 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 45660149f6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new addea34fe5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 29427a3e0b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 30ca4e8fa3 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new bf9009e933 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 0a1a0c1293 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 2ab7b8e890 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 30a366f5ad 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 1436cda49b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 19b229cf72 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new bf7d07157f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 284d06b2a6 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 9be430e87e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 29d3e1588a 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 956d07d2c2 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 2a4f1a36e2 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 48d4269d0b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 4499f79e2d 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new dbc5cef510 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 949cfa7975 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new a7eba945b3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new aa248b6f75 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 2e479b048f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 919b1ba0ea 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new a2939a7bfa 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new b87fb396f5 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 9bebbeabec 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new c2f0766f10 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 4e220446fd 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new bef95c4f3a 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new fb0f8ca09d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new b7199f1633 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new e1580b47dc 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new fc6e550653 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new b0c667ff52 189: onsuccess: #683: 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 (db02c13a3b) \ 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 1740 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 51764 -> 52308 bytes 04-build_abe-gcc/console.log.xz | Bin 237984 -> 236996 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 236628 -> 236816 bytes 08-build_abe-gdb/console.log.xz | Bin 50824 -> 51732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2476 -> 2704 bytes 11-check_regression/console.log.xz | Bin 10808 -> 15252 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 40 +- 11-check_regression/mail-body.txt | 156 +- 11-check_regression/results.compare | 72 +- 11-check_regression/results.compare2 | 5441 ++++++++++++++++++++++--------- 11-check_regression/results.regressions | 72 +- 12-update_baseline/console.log | 54 +- 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 | 158 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 72 +- sumfiles/gdb.log.xz | Bin 2816596 -> 2844416 bytes sumfiles/gdb.sum | 3937 ++++++++++------------ 30 files changed, 6037 insertions(+), 4021 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O2 updated (1cf6499bfb -> 8daeb48b96)

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-coremark/gnu_eabi-arm_eabi-master-O2 in repository toolchain/ci/base-artifacts. from 1cf6499bfb 45: onsuccess: #10: 1: [TCWG CI] No change after binutils/gc [...] new 8daeb48b96 46: onsuccess: #11: 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 1816 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31680 -> 31508 bytes 04-build_abe-stage1/console.log.xz | Bin 89592 -> 89872 bytes 06-build_abe-newlib/console.log.xz | Bin 14444 -> 14584 bytes 07-build_abe-stage2/console.log.xz | Bin 165020 -> 165576 bytes 08-benchmark/benchmark-build.log | 103 +++++++++++---------- 08-benchmark/benchmark.log | 101 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3824 -> 3832 bytes 09-check_regression/console.log.xz | Bin 4936 -> 5024 bytes 09-check_regression/results-vs-first.log | 4 +- 09-check_regression/results-vs-prev.log | 6 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 36 +++---- mail/mail-body.txt | 36 +++---- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++--- results_id | 2 +- 24 files changed, 184 insertions(+), 178 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023