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 fc70488a51 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 718c7cd12e 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 786a47f7dd 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 0ee117d8c5 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 0e9a49ec1e 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 27461a4d08 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 640e2ada37 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards eb3d3aa359 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 1f753c950b 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 1ddfdeb5c8 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 534f002b83 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards a958132909 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 362ba0578f 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 41095286cb 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 01c6f43a85 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 3882865984 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 6eb8632d15 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards e9129b30d6 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 880733cc16 93: onsuccess: #544: 1: Success after linux: 34 commits discards 726ec37c47 92: onsuccess: #543: 1: Success after glibc: 4 commits discards fcf73b3246 91: onsuccess: #539: 1: Success after linux: 27 commits discards 81834205b5 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 1ef569f559 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 7dadfff316 88: onsuccess: #534: 1: Success after linux: 12 commits discards 6beaf6ad9f 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 1d073c442e 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 560fe786f0 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 7939183964 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards b428878974 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 786b615ae4 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 85f69e4417 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 603afbfb05 80: onsuccess: #524: 1: Success after linux: 9 commits discards ce4ca8b7d1 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 1b551d08b1 78: onsuccess: #522: 1: Success after binutils: 10 commits discards c1f591dacd 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 6657fd0c85 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 25a4dda3cd 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 952124edb5 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 02328ab382 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 615a5ba163 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 42c561c114 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 0111a690ca 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards b14e34c1a1 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 14adfc6278 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards ed94699f17 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards ee1b98a2ea 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards a460bebc79 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 5b7b83996c 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards ffd57455f5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 42042388e0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards f598cfa19e 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards fa2f03a735 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards a8c91648df 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 32a3c84912 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 8d8ab501cf 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards bf3c946560 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards e6ffb15d73 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards a2a9028091 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards c052246116 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 2f596b5520 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards be903f8dd6 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 3d314a3d8d 50: onsuccess: #490: 1: Success after binutils: 6 commits discards aff05c8530 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 0c32951b95 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 32852ccfe8 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 18e875e286 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 72e34c08ab 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards c5352c96ff 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 725e71d92e 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 551d79fb3f 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards c606a60186 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 53e9e3a449 40: onsuccess: #476: 1: Success after linux: 69 commits discards 4186333b81 39: onsuccess: #474: 1: Success after binutils: 8 commits discards dd489baaec 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 91cd65a0a4 37: onsuccess: #470: 1: Success after binutils: 3 commits discards aabaf7f8eb 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards e9f92bfc5f 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 34e2a6037b 34: onsuccess: #465: 1: Success after binutils: 11 commits discards b5f7c9ab79 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 4c3c92bc38 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 0bac764b90 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 7d01a85af6 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 064143a160 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards d669c85923 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards fcbebc5d0d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 48c74a4ff4 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards a0ce029cce 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards bbd9a1ef61 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 46e44123e1 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards a9409c9c2f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d0a278cb03 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 28d8f12663 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b533208c7e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 74204ada5f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 889a352541 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1877c443b1 16: onsuccess: 1: Successful build after binutils: 5 commits discards 4040019f9f 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be945bba4a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f19f371cd 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a93bdf849f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 488556dce1 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c052c1f299 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ed272eef0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cacd3413ee 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d7640f19db 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61b44365c8 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 081e73eb37 16: onsuccess: 1: Successful build after binutils: 5 commits new 7da84320fd 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 52d1b75e04 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9f036b0fdd 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc24077300 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 518d3ea4b0 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 30320cc4a6 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new db8703fa1d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 2677631eb0 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 8153f7e4dc 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 0749447db7 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 0ee60987d3 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new c082fe5932 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 4cdd2c0ac5 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new f35b31903e 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new bc1d5cd87d 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new a7ac91e153 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new b4fbbc8e3f 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 303c112db7 34: onsuccess: #465: 1: Success after binutils: 11 commits new 9da3c90ef5 35: onsuccess: #467: 1: Success after glibc: 2 commits new dea5825837 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 0bb17ce59b 37: onsuccess: #470: 1: Success after binutils: 3 commits new a40f8e88da 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new b72a18ab3b 39: onsuccess: #474: 1: Success after binutils: 8 commits new 6d97a73f81 40: onsuccess: #476: 1: Success after linux: 69 commits new e7044d280a 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 2cd3299115 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 96d03ce4e0 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 4236e881ef 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 3ac7b9ca68 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 7cc95280aa 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new b05935a0ee 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new ee583b83d6 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 82bd942232 49: onsuccess: #487: 1: Success after binutils: 11 commits new 4bc5a24369 50: onsuccess: #490: 1: Success after binutils: 6 commits new 8773891f3e 51: onsuccess: #493: 1: Success after binutils: 13 commits new 8a99931839 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new c2a0e07797 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new dea0522a11 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new b600ec7cdb 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 2ef9f745b3 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new c74083b576 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new ef4a239cb0 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 2598335410 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 46f91b9aa0 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new d328c377b2 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new f98fdaf9e7 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 20b4020ed9 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 5894828bc0 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new a66d3db394 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 7578c532f9 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 448552dffe 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new b28652efc5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 74547241b4 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 5aecd68b5e 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 30bc02f1b2 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new a02ff34bd1 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new efa24fd597 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new a6cd0577b1 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 48fd87c897 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new c1d74a7597 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new a1c37b83c6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 6ff81a793e 78: onsuccess: #522: 1: Success after binutils: 10 commits new 44bc5a830d 79: onsuccess: #523: 1: Success after gcc: 25 commits new f8e409fef3 80: onsuccess: #524: 1: Success after linux: 9 commits new d090d87635 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new d1334b5f25 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 4ce0af84fb 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new bd93d64a40 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new cdd51380b7 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 8c44b73770 86: onsuccess: #532: 1: Success after gcc: 16 commits new 15301447c6 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 0cc6142845 88: onsuccess: #534: 1: Success after linux: 12 commits new 81dbabf2f2 89: onsuccess: #536: 1: Success after binutils: 27 commits new f97304b2ec 90: onsuccess: #538: 1: Success after glibc: 10 commits new ae5eec91c3 91: onsuccess: #539: 1: Success after linux: 27 commits new eb1e216c7c 92: onsuccess: #543: 1: Success after glibc: 4 commits new 090742b49f 93: onsuccess: #544: 1: Success after linux: 34 commits new 68237b9378 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 269fdbb72c 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new d78132da36 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 4d948a55f2 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new fbc8253c2a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 59796ea4aa 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new bf52c72891 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 79175aa444 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new e82eec3ed1 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 34ca2abde3 103: onsuccess: #555: 1: Success after binutils: 4 commits new bd209eea77 104: onsuccess: #558: 1: Success after binutils: 3 commits new d3cd1e18a7 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new e92735ec24 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 382f4768ce 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 5e3188cec3 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 10d0e521e8 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 509c537455 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 67a29ce01e 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 4bdea95096 112: onsuccess: #567: 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 (fc70488a51) \ 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 1680 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52440 -> 52472 bytes 04-build_abe-gcc/console.log.xz | Bin 235860 -> 233712 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 235704 -> 235524 bytes 08-build_abe-gdb/console.log.xz | Bin 51240 -> 50812 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2528 -> 2492 bytes 11-check_regression/console.log.xz | Bin 6776 -> 8536 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 79 +- 11-check_regression/results.compare | 36 +- 11-check_regression/results.compare2 | 442 ++- 11-check_regression/results.regressions | 42 - 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 | 81 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 42 - sumfiles/g++.log.xz | Bin 2908704 -> 2893192 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2518308 -> 2528816 bytes sumfiles/gcc.sum | 4837 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 950476 -> 948552 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 227924 -> 229084 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465820 -> 473616 bytes sumfiles/libstdc++.sum | 13 +- 43 files changed, 3014 insertions(+), 2882 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions