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-arm in repository toolchain/ci/base-artifacts.
discards 4bdea95096 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 67a29ce01e 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 509c537455 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 10d0e521e8 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 5e3188cec3 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 382f4768ce 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards e92735ec24 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards d3cd1e18a7 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards bd209eea77 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 34ca2abde3 103: onsuccess: #555: 1: Success after binutils: 4 commits discards e82eec3ed1 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 79175aa444 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards bf52c72891 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 59796ea4aa 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards fbc8253c2a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 4d948a55f2 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards d78132da36 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 269fdbb72c 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 68237b9378 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 090742b49f 93: onsuccess: #544: 1: Success after linux: 34 commits discards eb1e216c7c 92: onsuccess: #543: 1: Success after glibc: 4 commits discards ae5eec91c3 91: onsuccess: #539: 1: Success after linux: 27 commits discards f97304b2ec 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 81dbabf2f2 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 0cc6142845 88: onsuccess: #534: 1: Success after linux: 12 commits discards 15301447c6 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 8c44b73770 86: onsuccess: #532: 1: Success after gcc: 16 commits discards cdd51380b7 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards bd93d64a40 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 4ce0af84fb 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards d1334b5f25 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards d090d87635 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards f8e409fef3 80: onsuccess: #524: 1: Success after linux: 9 commits discards 44bc5a830d 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 6ff81a793e 78: onsuccess: #522: 1: Success after binutils: 10 commits discards a1c37b83c6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards c1d74a7597 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 48fd87c897 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards a6cd0577b1 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards efa24fd597 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards a02ff34bd1 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 30bc02f1b2 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 5aecd68b5e 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 74547241b4 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards b28652efc5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 448552dffe 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 7578c532f9 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards a66d3db394 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 5894828bc0 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 20b4020ed9 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards f98fdaf9e7 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards d328c377b2 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 46f91b9aa0 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 2598335410 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards ef4a239cb0 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards c74083b576 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 2ef9f745b3 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards b600ec7cdb 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards dea0522a11 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards c2a0e07797 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 8a99931839 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 8773891f3e 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 4bc5a24369 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 82bd942232 49: onsuccess: #487: 1: Success after binutils: 11 commits discards ee583b83d6 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards b05935a0ee 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 7cc95280aa 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 3ac7b9ca68 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 4236e881ef 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 96d03ce4e0 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 2cd3299115 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards e7044d280a 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 6d97a73f81 40: onsuccess: #476: 1: Success after linux: 69 commits discards b72a18ab3b 39: onsuccess: #474: 1: Success after binutils: 8 commits discards a40f8e88da 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 0bb17ce59b 37: onsuccess: #470: 1: Success after binutils: 3 commits discards dea5825837 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 9da3c90ef5 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 303c112db7 34: onsuccess: #465: 1: Success after binutils: 11 commits discards b4fbbc8e3f 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards a7ac91e153 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards bc1d5cd87d 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards f35b31903e 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 4cdd2c0ac5 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards c082fe5932 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 0ee60987d3 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 0749447db7 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 8153f7e4dc 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 2677631eb0 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards db8703fa1d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 30320cc4a6 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 518d3ea4b0 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards cc24077300 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9f036b0fdd 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 52d1b75e04 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7da84320fd 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 081e73eb37 16: onsuccess: 1: Successful build after binutils: 5 commits discards 61b44365c8 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d7640f19db 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cacd3413ee 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ed272eef0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 826b7dd93b 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1d7af38af1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 110e34a069 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 42cea438f8 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 66f9840fed 16: onsuccess: 1: Successful build after binutils: 5 commits new 138cb3731f 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37611deea6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ca982c368d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 82f08f41c0 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17d0a1824b 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 3386f7c482 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new f8ed3dff32 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 806d908c15 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 1b030984c2 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 3fa1ba8fe4 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 19f3498642 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 31a3865983 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new dd3e43382e 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 09185a8ff3 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 4f99d8b277 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new f4fa79f75f 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new e430e5d682 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 9a9c5d7d99 34: onsuccess: #465: 1: Success after binutils: 11 commits new 6adf3ffa9f 35: onsuccess: #467: 1: Success after glibc: 2 commits new 39e6ac7216 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 86fc42edad 37: onsuccess: #470: 1: Success after binutils: 3 commits new 2f619784ca 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new cbffc75a7a 39: onsuccess: #474: 1: Success after binutils: 8 commits new 8ca9dbb71a 40: onsuccess: #476: 1: Success after linux: 69 commits new d7b08aa09d 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 721336ded0 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new aacf6acc33 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 399a76ab7e 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 8f12e8194d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 652ee12038 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new a97adccea9 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 3752e029e9 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 27ba5eabb4 49: onsuccess: #487: 1: Success after binutils: 11 commits new 5896abe026 50: onsuccess: #490: 1: Success after binutils: 6 commits new 0c5da81852 51: onsuccess: #493: 1: Success after binutils: 13 commits new fe5d4324ef 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new d64094cdd9 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a7ef8db185 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 98e492538c 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new d6a33ecfee 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new b26a35b583 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new d446a68d19 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new a91f83b1ce 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 283b0f5ab0 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 85c5e3e846 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 821e5b3f9c 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 646df1482c 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 2c75c545ee 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 03d9056f1a 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new e0271dab09 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 8ad51daf88 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new cd0e98332a 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new a9c13c4530 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new a34ba7413a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new fe9904709a 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 5d2a3b2fcd 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new d467645549 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 32e7cca528 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 218b98ba5a 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new ad3624d03c 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 96ac1942d5 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 4c8c7c833e 78: onsuccess: #522: 1: Success after binutils: 10 commits new 394ef4a30f 79: onsuccess: #523: 1: Success after gcc: 25 commits new fd8cab1be0 80: onsuccess: #524: 1: Success after linux: 9 commits new 90f8f05396 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 714516965b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 71f99c8c9a 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new f378a6823e 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new c2c678b5f7 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 933770982f 86: onsuccess: #532: 1: Success after gcc: 16 commits new d36b538845 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new e4f5d80302 88: onsuccess: #534: 1: Success after linux: 12 commits new 6eeedcad2d 89: onsuccess: #536: 1: Success after binutils: 27 commits new 500f118f52 90: onsuccess: #538: 1: Success after glibc: 10 commits new b9142d4f54 91: onsuccess: #539: 1: Success after linux: 27 commits new 849558613a 92: onsuccess: #543: 1: Success after glibc: 4 commits new 909d6fe85a 93: onsuccess: #544: 1: Success after linux: 34 commits new 108a150b0b 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 0dde7c3ba9 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new ab8abb0895 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 63862247c4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 9e29562ed1 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 8e9cae2b12 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 6269bf2fe7 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 34fb1c0c82 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new a801d83529 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new d794b270b3 103: onsuccess: #555: 1: Success after binutils: 4 commits new 5ef4e39fa4 104: onsuccess: #558: 1: Success after binutils: 3 commits new aa797acde3 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 43ab2554b3 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 5359424b13 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new d41abc135e 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 2408de5c76 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new b4450f078c 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 513a06ec84 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 69571f0718 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 7b5b37d556 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (4bdea95096) \ 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 1700 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 52472 -> 52200 bytes 04-build_abe-gcc/console.log.xz | Bin 233712 -> 235320 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8352 bytes 07-build_abe-glibc/console.log.xz | Bin 235524 -> 235456 bytes 08-build_abe-gdb/console.log.xz | Bin 50812 -> 50964 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2492 -> 3660 bytes 11-check_regression/console.log.xz | Bin 8536 -> 6824 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 27 + 11-check_regression/mail-body.txt | 89 +- 11-check_regression/results.compare | 51 +- 11-check_regression/results.compare2 | 519 +--- 11-check_regression/results.regressions | 47 + 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 91 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 47 + sumfiles/g++.log.xz | Bin 2893192 -> 2922656 bytes sumfiles/g++.sum | 167 +- sumfiles/gcc.log.xz | Bin 2528816 -> 2495128 bytes sumfiles/gcc.sum | 4790 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 948552 -> 949168 bytes sumfiles/gfortran.sum | 75 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229084 -> 229400 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473616 -> 460984 bytes sumfiles/libstdc++.sum | 13 +- 41 files changed, 2990 insertions(+), 3033 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