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 d2ed90dff 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards fa0a792f0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards adb1bb1fc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards bf14c7d42 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards ca1f0e2f3 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards d407e308a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 0c3d867e0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 861818112 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 440615694 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 672cd83d2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 8ffee6286 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 32d0fa872 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e69116749 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 4237725ce 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards a7802bd3f 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 902fdbf3a 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 8be909091 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 9c8268601 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 9646abac9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a493b74f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 20cefa9f7 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards e9c046729 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards a321cb351 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e7add2c8f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 538598a27 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards a9cd095c8 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ebafaf2c7 74: onsuccess: 1: Successful build after linux: 44 commits discards 64bf43d99 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a4ee0a7d6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6b87c5e30 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards e1a7834a0 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards be13f61f2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 5fa88e21a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 852fa270d 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 552d24c7e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 158b43b37 65: onsuccess: 1: Successful build after gcc: 4 commits discards 2b76b24a2 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fec54d2e6 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a624284f7 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 8baef285b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b555fde77 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 0f688d6c7 59: onsuccess: 1: Successful build after glibc: 2 commits discards dec43e5c9 58: onsuccess: 1: Successful build after binutils: 2 commits discards 523860f83 57: onsuccess: 1: Successful build after gcc: 7 commits discards 66ab0288d 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards de1af9098 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e1a818d2c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards f2e201663 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 01c1b9f8f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 7db5b8f5c 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards effbdf26d 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 01011fbc3 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 53dd824c6 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 612373547 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 77bc4aee9 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 30c72c404 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5fa61c9d7 44: onsuccess: 1: Successful build after linux: 34 commits discards 33a854543 43: onsuccess: 1: Successful build after gcc: 2 commits discards 7ed02ef69 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 2e49c69e9 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 554cb5984 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ff5cf550c 39: onsuccess: 1: Successful build after gcc: 2 commits discards 6edc55d44 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7b7e9e08a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 341bebabd 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d6369bb30 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9d2a8a4f1 34: onsuccess: 1: Successful build after gcc: 3 commits discards 95df6ae80 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6bde0ca2c 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 097472d0d 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 861f28909 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 6598594df 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 74d1ac37b 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 2a7e86a00 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b7d2e3e78 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 62159a842 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e6f08859f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d9b7ad261 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c6c447d9b 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 14b1e5f71 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 097856b5b 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2442da06d 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b6c4127c6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bc63701ea 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d4d69f3fa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ce2f7d57c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7e58661b1 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 93a53d4d2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8e0f4afd0 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5025b7a4e 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 06dbc6805 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f90df1463 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c534dc230 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4878f869b 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8bd5de076 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ca4a33c15 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b3cc09a27 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0fbe7b78f 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 04c669768 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cf18bc381 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3ba7e08fe 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1 new 63b48c948 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2c6b4337c 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9432b2885 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 24f5facb0 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0e3f0a990 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3b047815a 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0c9862ae4 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2943524fd 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ba9cf493a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bf3b784f9 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5e1fff907 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0a0656697 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 705d12dac 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e386290ca 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8cc1cec3d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0c5cd7f51 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d1efdd4f0 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bb38408ee 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4c4d166ad 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a31c8e58a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f81d6668c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 740e4d9d7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a8d5fc0f9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 00fb745ff 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b07d60db8 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fa9a7b096 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 01d383214 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a72bae61f 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 25da159ae 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9f2c60613 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d87679178 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new d5c2a122e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 01cdbf133 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new d7ef8109f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f1b1120b0 34: onsuccess: 1: Successful build after gcc: 3 commits new 64cbe11be 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8d7b043e7 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 497b114fd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8377983b4 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 70f1887d4 39: onsuccess: 1: Successful build after gcc: 2 commits new 44e3d1b11 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d8c07bdcd 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 09420c11f 42: onsuccess: 1: Successful build after baseline build: no n [...] new f521a780f 43: onsuccess: 1: Successful build after gcc: 2 commits new 51ab46709 44: onsuccess: 1: Successful build after linux: 34 commits new 7c5b0f333 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6a51f5658 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 5fcc8686b 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 81a58a7ee 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new a7e3eea77 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 29d2ef211 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 88c72ca63 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 238bee70c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new a6d808975 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new d1935df8c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2f24f69ec 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a3e357cc4 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c19d8296c 57: onsuccess: 1: Successful build after gcc: 7 commits new a0463854e 58: onsuccess: 1: Successful build after binutils: 2 commits new a37577950 59: onsuccess: 1: Successful build after glibc: 2 commits new 778717fc0 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 3132033f4 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 105e779e2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 659e6ffe8 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a46f32a97 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 609c86280 65: onsuccess: 1: Successful build after gcc: 4 commits new 5b12f244e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3101e4ce0 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a76fb6978 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5d10bf3fd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new c1fbe24be 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 86b067285 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 48f951c64 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5790f8c08 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 95f6a300b 74: onsuccess: 1: Successful build after linux: 44 commits new 4abedd5a4 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cdf70b895 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 91f645574 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e1c791fd1 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 14edfce62 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 6530cdb25 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new d1970cc77 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 49b443b55 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1e423bb4d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 810bb8e10 84: onsuccess: 1: Success after gcc/glibc: 9 commits new b1dce0ce1 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 6f11ecd25 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d40542e33 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 0cd0e3907 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 5d09f501b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 59aa59fa4 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0ae4b6077 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 1853cab70 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new d2696e85d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new b4830d68d 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 6df4ca562 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new dfaa1447a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 0e452e5c0 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 877a19266 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new c64fbdcc3 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 2dfbe3f6f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 6847d8d12 101: onsuccess: #1693: 1: Success after glibc: 14 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 (d2ed90dff) \ 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 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30304 -> 29612 bytes 04-build_abe-stage1/console.log.xz | Bin 91040 -> 90816 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9124 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 234504 -> 235240 bytes 08-build_abe-stage2/console.log.xz | Bin 223196 -> 225696 bytes 09-build_abe-gdb/console.log.xz | Bin 37476 -> 37448 bytes 10-build_abe-qemu/console.log.xz | Bin 32060 -> 31864 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2448 -> 2456 bytes 13-check_regression/console.log.xz | Bin 4736 -> 4592 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 11 + 13-check_regression/mail-body.txt | 45 + 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 52 +- 13-check_regression/results.regressions | 45 + 14-update_baseline/console.log | 39 +- dashboard/dashboard-generate.sh | 4 +- dashboard/dashboard-push.sh | 6 +- dashboard/squad/dashboard-push-squad.sh | 14 - dashboard/squad/score/results-functional.json | 1 + dashboard/squad/summary-annotation.txt | 0 dashboard/squad/test/results-functional.json | 4 - dashboard/squad/test/results-metadata.json | 12 - dashboard/squad/test/results-metrics.json | 3 - git/glibc_rev | 2 +- jenkins/dashboard-push.sh | 6 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +- results | 45 + sumfiles/g++.log.xz | Bin 2656544 -> 2672612 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2223788 -> 2206728 bytes sumfiles/gcc.sum | 2348 +++++++++++++------------ sumfiles/gfortran.log.xz | Bin 878328 -> 880932 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 199784 -> 199688 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422516 -> 423600 bytes sumfiles/libstdc++.sum | 15 +- 49 files changed, 1604 insertions(+), 1363 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions delete mode 100755 dashboard/squad/dashboard-push-squad.sh create mode 100644 dashboard/squad/score/results-functional.json delete mode 100644 dashboard/squad/summary-annotation.txt delete mode 100644 dashboard/squad/test/results-functional.json delete mode 100644 dashboard/squad/test/results-metadata.json delete mode 100644 dashboard/squad/test/results-metrics.json