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 d04a13ae207 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards ac53ca3583f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 18a92f6494b 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards d1edaaeb629 118: onsuccess: #863: 1: Success after linux: 12 commits discards 75ae16f679b 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 795e13375ab 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 08f94db2ecb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards dbabd8cc56f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 3a1cdf1a147 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 680343463d6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 742a68a918e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 16e733e634c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 84ee35915ee 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards d455e0fc6fa 108: onsuccess: #850: 1: Success after gcc: 2 commits discards aee5cffd05a 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 6d7e069791a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 059457bacdd 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 395fb5addf4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards cd82797f6a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 8577c385c2d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards ecc98a64c88 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 9abac687911 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 8fa6ad95962 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards bb70f71dc60 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 7cfbb364a21 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards cc3d3f57c1a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards e7c009c91d5 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b4f5b9a7a35 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 7aaade82c24 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 3c708a5cb13 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 3ff8b02aa49 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards be62ad06e56 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards fc836ea4ecb 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 55a0f0ba1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 8876df3b2dd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards a52c3c8e038 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 84cecdc46a0 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards feab18af51e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 1dbcb05d1e0 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 38fcd727b0c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 13856fffc15 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 99e39120a9c 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 334adb95c18 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 9e9f635d719 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards bd106f71e95 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards d6a84952af9 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 75102afe700 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards c1ca7411af5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards a53d1fe6c5a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 94d75eb4d63 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards ac6930b5466 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 89a5c0738b3 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards cdc41291707 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 0eaf5bad93f 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 6cb1780ebe9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 146cb134aa5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 9724e52a190 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 85b5e42b8f9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 01caf8b0701 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 101d34c5208 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards b4cb9742696 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 5da817e231d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards db16fdc5df7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 0e2f011b1df 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards bf302f382e9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 0d04972b3de 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards b27108279d3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards a05f8e40ca0 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards f5b68dfe22b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards d0dc6a5f499 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 3acd5369329 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 1a329a896d3 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 755f69ad2ba 49: onsuccess: #785: 1: Success after binutils: 12 commits discards c4deaa5671f 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 623f6fffd32 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards c3e48d64dd9 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 9148f6776f3 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 851538ae099 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards a382d7ba1ac 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards afd9d778f2e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 0064ef484ba 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards b1456d77fa1 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards ad66afbb04e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards fcd868f4a22 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 14bdfe8c57e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 352da7305fb 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards c068f9ffd1e 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 45290253906 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 30d28ea9998 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 6edeccbec08 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 0814acfbb26 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 40b3948168b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 8d90163205e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards d0f3bd9e55d 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 359a4253e35 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 26f9a339173 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 18ef88a2997 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 1f437a786b0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 18c1b76b0eb 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards f239de4a29a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 6e5c310f839 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 40170aebb3e 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cffbe909eaa 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 2d99fcf2da6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new aee9ae88126 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new e019796ea5a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 35bacbd7022 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 87da2a93fd0 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 814639c6a0f 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 0128510115d 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 8e238301f88 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 4478425bf59 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 478733259e4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 710400165bb 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new bf722060785 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new b467311d5d0 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 8439aa53fa5 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 4eb3fe35c48 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new e56a464e25a 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new d66341d0bd0 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 67ce2b9c9b9 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new c35d11424dd 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 8fead16106d 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 5ccbda5c7fe 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 0b35e3c094a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new f7544c7f766 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 103d16e6ff8 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 44b5aa0f94c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 15f45cec913 48: onsuccess: #782: 1: Success after binutils: 8 commits new 342dc70dec6 49: onsuccess: #785: 1: Success after binutils: 12 commits new 19ea697dc23 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new d4fdefa67b5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 266a19c752a 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 874afaf62ea 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new e2597903787 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 48e6b4d64ee 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new a336c841771 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 83bdbca7130 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 92f3ac7119d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 07e85dfc293 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 68d6d6964c7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new a678af267c6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new c72451efbde 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 0da43428491 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new fc84cd0d4b0 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new c7794d5620c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 6855073f9b9 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 2988d02f48c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 36661108391 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 2c1a50cd5c4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 3efef04ece1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new b9fc13c07be 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new b93aea0a697 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 748df362bf8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 98dff52af97 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 30c650d9503 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 3fe6b7fa737 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 221a4b254f2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new e9272cc2ff2 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new d425672825a 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new e59b77d368f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 2d2b3722d60 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new f42cf02bb52 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new c1591ad500c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 6d74a0ac510 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new d7ce545e822 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 43ebe76f54c 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new e3bfb65eaf9 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 6f4024cc56f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new b94b5c8466c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new ccbb5abc929 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 31878b09c53 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new f4f540b0c2f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new a83a088a9b2 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new ea9c9e2bd4f 94: onsuccess: #832: 1: Success after binutils: 5 commits new 4769408e850 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9d08d42163d 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new b43336b9f3c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 31934640ca3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 81ae5437fd0 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 585330ade68 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 617107f8ef7 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 65ec78064a8 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 4f3d71a62a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 9325352def3 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 8e9dd2f9f97 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 2aba4dc57a2 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 971b1c040b3 107: onsuccess: #849: 1: Success after binutils: 5 commits new d05d5dbd5ec 108: onsuccess: #850: 1: Success after gcc: 2 commits new a76315a4bca 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new ea781c2d1cd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 9885b361c0e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 06f43ddf6b4 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 1550a7e6edd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new ac4bb239280 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new c60d51a2229 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 943ebf199f3 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new b1f047360f8 117: onsuccess: #861: 1: Success after binutils: 18 commits new ed5ba05234c 118: onsuccess: #863: 1: Success after linux: 12 commits new 8d707b2176c 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 0c5493d2502 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 11790d16ab0 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 938c8c2f5dd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/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 (d04a13ae207) \ 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 1740 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39676 -> 40060 bytes 04-build_abe-gcc/console.log.xz | Bin 212676 -> 214920 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8828 bytes 07-build_abe-glibc/console.log.xz | Bin 243216 -> 245532 bytes 08-build_abe-gdb/console.log.xz | Bin 39004 -> 39868 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2768 bytes 11-check_regression/console.log.xz | Bin 7728 -> 7896 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 54 +- 11-check_regression/results.compare | 33 +- 11-check_regression/results.compare2 | 321 ++- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 56 +- 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 | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 + sumfiles/g++.log.xz | Bin 3728288 -> 3732384 bytes sumfiles/g++.sum | 162 +- sumfiles/gcc.log.xz | Bin 3303216 -> 3319476 bytes sumfiles/gcc.sum | 4788 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1075860 -> 1080408 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231420 -> 231132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450116 -> 451804 bytes sumfiles/libstdc++.sum | 26 +- 43 files changed, 2911 insertions(+), 2775 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