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 17ecd1e0f9 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 8021513e4e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards e73da6a995 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 531db87fcd 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 35e2da66ea 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 3abc68e12d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 90af853f70 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 4d4bc71c8c 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 86d874ef43 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards f16d49972f 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards b2836fcbf5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 85f57b2eae 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards d07a5ada51 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 2b3fc0f58b 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 16d7b6e367 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 201905811e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 14cdbbfe91 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 4cb53c4914 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 0225e51745 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9baa1e013b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 6ad5cb7d2e 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards e8aaf63b2f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 10e7743e25 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 6bfcc9ab57 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards bd7a097765 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 70b4545888 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards a95ab73a86 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards fbb57ddd25 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 7e46b71ad5 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 24b02b1d18 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards b16a50a556 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards b20641bdbf 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 60e0a58231 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards b636855c66 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 33fa8a23ef 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 50063c5081 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards aba336dfd8 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards d05f7a37e7 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards cd173f7a9d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 6b025ec522 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 4d31e12b54 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 72c532a80e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 75be994ae4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards dfb0af22ce 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 113d2d66ca 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards f57561d16e 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 84eab28200 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 39a8840b96 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards bca262068b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 1d4bf8fa02 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 6068980344 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 98f4354cdb 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 7da6ba605f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards bdb3eb5939 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 369a6310da 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards ad1f615109 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards cde7f379c7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 8738324826 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 0c2460f6f9 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 058246c192 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 46a7e32e95 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 0f59091717 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 745fee97c0 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards c9a84e47f9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards d26bd41df8 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 9b5ad0a79c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards de63bef12b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 6a25cd8b8b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards a6f4007594 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 3b8cfbd729 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 744f50b020 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 4c354174a4 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0749c3c2f2 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 788f04e0c0 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards c19c5ee173 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 9dfd1e551c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards ea85315b27 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards c3f9cd2aa5 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards b327bd8499 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards edc293cb96 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards aa81be09a2 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards d8bff7915e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 2e7ee697e3 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards fdcff7226c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards e9dcb45b3a 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 1441263ef8 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 43b356f605 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6799c9510f 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4520c8ccf5 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce30367b6b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8dd67756c6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10483fe461 16: onsuccess: 1: Successful build after binutils: 4 commits discards 48bc4b5fc8 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d65f8d2686 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d32b181058 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d945cdf276 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0a798b78e7 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9d65887bc 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 54b5960a58 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 15df8ec5f2 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a53b3ce05d 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new dfcddf6722 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5cb5bed021 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7e6b89afb7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0bfacbedb5 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 44871e03d6 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3e3bf34d8 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 529ff91d92 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5847d5ad00 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b7df4ab7b2 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5888679add 16: onsuccess: 1: Successful build after binutils: 4 commits new 820b4f7f10 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4aa3ae72a6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f817c19e26 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa31854a6b 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ee4ebf2a2f 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9932a60ae 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e2d8a96509 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ffb41512b0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 6a805d47e0 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 13b8c2916f 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 0f659fc0c4 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 806282dcb3 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new adc976bd4f 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new f59dba30df 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 12ebe01833 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 902a564de4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new e63028f2cf 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 4daac0136f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new fc113d1c8e 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 4e88d84acd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 84edb3294b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new d9541c070e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new edf5ff1073 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new de93a5c4ac 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 256ef00856 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new b8893843b9 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 2f2e9d8d39 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 9a96d14bd5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 5cdc78587d 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 6b2854a958 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 7bc310344f 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new e0c5970f20 48: onsuccess: #782: 1: Success after binutils: 8 commits new ec635d925b 49: onsuccess: #785: 1: Success after binutils: 12 commits new 8c5b3c242d 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 786b2e4ffc 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new f979158876 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 12b82c2da8 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new b011234662 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 0f7e0efbf3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 391f1ef152 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new c4b1af5743 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new fa526c2e57 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 310052cc9e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 98b7c36dfb 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 1e4437852f 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 3c343725c7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new ef470634f5 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 31d396f113 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 20de01a84c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 2285a2e267 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new d9fc3e062a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new dd5a9234bd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 354402f29c 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 45df6a7087 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 5ee9eccebc 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 2efa7eb87d 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new c8f4f54a54 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 33129cd52a 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new c0c3e219f5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 3c9f453ea3 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 957ad5804b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 2a24df2fa7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 9bb6505c7b 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 6e87bd7e7f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 7b18913d9f 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 8b315e9784 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 47d1852739 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 286d62a523 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 3a6b990f29 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 8bc8954408 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new bf453827b2 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 875e447e97 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 941288a17a 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new dd6ded46a2 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 082dc9645e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 84623a23b2 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 4ed021bb58 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 6a132ebdfa 94: onsuccess: #832: 1: Success after binutils: 5 commits new aafcb32cf8 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9181fd8775 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 874dc3caf5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 1fd3816b1a 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 833e8a3d2f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 5ea40677fc 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new d305f5e1c0 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new d4b91caa07 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 2fdfedae54 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new ebbb2a7fb5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 2c998cb13e 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new e21f8e63ca 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new c7e05bb0e6 107: onsuccess: #849: 1: Success after binutils: 5 commits new 4e17ac0fce 108: onsuccess: #850: 1: Success after gcc: 2 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 (17ecd1e0f9) \ 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 1748 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 40072 -> 40160 bytes 04-build_abe-gcc/console.log.xz | Bin 216264 -> 213568 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9632 -> 9688 bytes 07-build_abe-glibc/console.log.xz | Bin 246396 -> 244176 bytes 08-build_abe-gdb/console.log.xz | Bin 40492 -> 38940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3980 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2384 bytes 11-check_regression/console.log.xz | Bin 5524 -> 5320 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 79 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 27 - sumfiles/g++.log.xz | Bin 3774500 -> 3747608 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 3303828 -> 3324888 bytes sumfiles/gcc.sum | 4978 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1070508 -> 1068488 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231824 -> 231884 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451768 -> 458664 bytes sumfiles/libstdc++.sum | 12 +- 39 files changed, 2752 insertions(+), 2763 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