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-arm in repository toolchain/ci/base-artifacts.
discards 68c6bc796e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 8ed1b6c335 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 713c91de09 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 9898da4527 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards d799c6ddec 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 0232a82286 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b48a4d6c67 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards a23636e8c1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards cabc41cb6c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ad7a3943c1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e81f6d71e4 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 0d8ff268ab 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 49dcdb1984 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 7093248b68 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f4ce6d3f73 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards a26e61489c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ded1079cfd 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d8382c41d0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 895338c080 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards ca35406e94 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards bee4ee6a0d 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 8710f88e24 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 74e377a225 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 80ef7c9477 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 1bb731cb4d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 73be7b7eb1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c197bafc02 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 5deb93c8cc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 21b0b48746 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3700eb112b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be113203e8 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 9ed5bd9cca 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24f18710d9 74: onsuccess: 1: Successful build after linux: 44 commits discards b3bab9d064 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0177a41f92 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ad25a1aeb3 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards d4ebaa0de7 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards b53781fcfe 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 553f6e8f9f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b91e4f9fb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3c0d849e1 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8023dfd518 65: onsuccess: 1: Successful build after gcc: 4 commits discards fb1c0c38d7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92aabb69dc 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b0da992dd6 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 9fae3404e7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 948aea6482 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 26eb1864b5 59: onsuccess: 1: Successful build after glibc: 2 commits discards 2f3793e59a 58: onsuccess: 1: Successful build after binutils: 2 commits discards b9a18d4884 57: onsuccess: 1: Successful build after gcc: 7 commits discards 43597fc912 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d6a22debcb 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c2930cbfb3 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 9150dce748 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 192559c1b2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 40e8a67465 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 05d990cd5a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 826750db48 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f8bbe16bcf 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a60c1a758d 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9607f5f16 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 4c49f08f6f 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a0e42385c 44: onsuccess: 1: Successful build after linux: 34 commits discards 42ece4c6e0 43: onsuccess: 1: Successful build after gcc: 2 commits discards 0b44c1923d 42: onsuccess: 1: Successful build after baseline build: no [...] discards 43f4c842e5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9e1f3ad6f 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c145675fab 39: onsuccess: 1: Successful build after gcc: 2 commits discards de03bf3b2e 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 818e90bd90 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 25a28f43b2 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4fe49d9a56 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 45d7a55a69 34: onsuccess: 1: Successful build after gcc: 3 commits discards 4397ffc737 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b650ad00d1 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 7255ea3cc8 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cb96c2bf40 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards c9420d769b 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards db008e5e2c 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 59aff2dcfc 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ae8f3d59be 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 52bb4dd59f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e7063eb688 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 25a73d5f84 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5e86024a65 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8c5700423d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2236cb17e3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 32c74b0b07 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a6064e2f6c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5193ed4294 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 01e6e39389 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2712d7b6ae 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eda44fe668 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a29c18aacc 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1026504c7c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6cc7c1a22e 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8b76c7fde2 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0f67fca95c 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 818201c92a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c5875a60d0 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7465676c35 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2a411260f0 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7ee3c50fb0 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8949ac312c 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7f3ea2cef4 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 17c1bd196b 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ca5c67d60 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b9e70264c7 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 194de195c2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a78ba57480 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new df214d17c4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b6b86948d9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 30d0fc1695 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dc516e545e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ba30c93fe 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new aef029d994 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e6016ee31d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ac055f48a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7e1a6ca3c8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e53bbc4bd4 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 895f20ff6d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f895094252 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 21872ed293 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9ebbafc1a8 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b6197d9193 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18bb267bc2 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 0490e0850a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 27a609e36d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new b6a2cd5d2e 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f1ca5579d 34: onsuccess: 1: Successful build after gcc: 3 commits new 83ef60dad3 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5469dc6e4b 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 287623755f 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5ce2c91155 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6752971aa 39: onsuccess: 1: Successful build after gcc: 2 commits new f50318db8a 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46dc21173c 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20c8452a5b 42: onsuccess: 1: Successful build after baseline build: no [...] new 02e416a11b 43: onsuccess: 1: Successful build after gcc: 2 commits new 8b9abcf74a 44: onsuccess: 1: Successful build after linux: 34 commits new faac3f9534 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6f00e76f3 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 4784448446 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74347fdcaf 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new e8539ce43f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 18a202fd05 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 47d5a0ee8e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ac86fdf74f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b3db204ecb 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new dbde0bb9b1 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b9fb0cce6c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ec77e4d2d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cb4c9a5b7c 57: onsuccess: 1: Successful build after gcc: 7 commits new 97434561fc 58: onsuccess: 1: Successful build after binutils: 2 commits new 62365ffb88 59: onsuccess: 1: Successful build after glibc: 2 commits new cab83a4596 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ad49bd104c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 569d986a4a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c7365b3879 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7235f5ef89 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93883b81c5 65: onsuccess: 1: Successful build after gcc: 4 commits new 4596614932 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 78526e1945 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 263abe4926 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37db33b538 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5699e31d1f 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 48ff41a310 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 7618648ecb 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ecd2200422 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 244549c5bc 74: onsuccess: 1: Successful build after linux: 44 commits new 9bc994461e 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9744764c16 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 1e8b24dcc2 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new faea5e2147 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bb799d06e1 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 20902eae2e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 7c4ea452cc 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 429aa3bd25 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 75acce6221 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 9c0bb3f15c 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 5ac1253750 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new df2e3926f3 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new a059c3597f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f585e0e317 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e43e423aa1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b525ff7e88 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3d9feecf27 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b340758fd2 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 8c371a4d3e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e29c782e21 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 676f2a7a11 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b7f5b30449 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d39daa612c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 85665bc36a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 4715bb62c8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new d80f5dee81 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new ceb17611aa 101: onsuccess: #1693: 1: Success after glibc: 14 commits new fd293db8be 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4563482b0a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8b05a72c8c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7a8a678c14 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a8da0c9018 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2adfa206a2 107: onsuccess: #1700: 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 (68c6bc796e) \ 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 1676 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29876 -> 30180 bytes 04-build_abe-stage1/console.log.xz | Bin 90268 -> 90908 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 234416 -> 233668 bytes 08-build_abe-stage2/console.log.xz | Bin 222976 -> 223788 bytes 09-build_abe-gdb/console.log.xz | Bin 37016 -> 37344 bytes 10-build_abe-qemu/console.log.xz | Bin 31872 -> 31304 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2792 bytes 13-check_regression/console.log.xz | Bin 5252 -> 5404 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 67 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 70 +- 13-check_regression/results.regressions | 41 +- 14-update_baseline/console.log | 62 +- 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 | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 +- sumfiles/g++.log.xz | Bin 2658780 -> 2658708 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2230276 -> 2209524 bytes sumfiles/gcc.sum | 2236 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882176 -> 879452 bytes sumfiles/gfortran.sum | 83 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201292 -> 201008 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429104 -> 424208 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1520 insertions(+), 1279 deletions(-)