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 82dbb614d0a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 8760c06b456 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 27db290a0fe 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards b6d2d6c6f6b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards a41fe8a6ed6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards a0f91f04750 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards f9678737b00 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 81500816d51 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 84887dce84a 108: onsuccess: #850: 1: Success after gcc: 2 commits discards ef2b9165701 107: onsuccess: #849: 1: Success after binutils: 5 commits discards d7115226963 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 38639a65436 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards d847130cf41 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 77c2166b351 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 789724a03a7 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 058c780d646 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards a927713ddf9 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 6d80d8725d9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 75ef36ded78 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 48ca6873dd3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards c6ffcb2fa1c 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards e52226e342f 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 4942667e380 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 4dac80139f6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards c6efa766566 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 66ea2eceff4 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards a9f4e26c6ed 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 7d84b89ce06 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards bf326ab5855 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards ac1003153b6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards af91aaf8ab9 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 1c53c1fd367 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 84fffef4c7e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards ad4713a7bc2 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 385fd6188a9 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 17f8044ca79 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 47e79572903 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 13e6cdcb52c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 2d2a286d573 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 137dfc1dc2f 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 55248fe8325 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 8b74ca1eb51 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 3228046e5bf 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards a3b14f88484 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards a60d7898b2b 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards b2184566e74 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 0646de39afa 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards c40709a75a5 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 3aff8928530 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 7cfb3f8efa0 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 7be8a153092 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards fbaec5cce89 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 6434a14e1aa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 14d130482f8 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 30832047039 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 846db273969 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards c974dc6adb6 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards a92592654f9 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 104a47d97f3 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 45ef188e309 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards cc9871a3b2e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards fa59b7f566f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 7f0a56b6d8b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 5ad3e010580 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 1d56ce0d105 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards ddaeb4d267a 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 1b7c51fe6dd 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 9264faa73b0 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 5d7b11e24ea 48: onsuccess: #782: 1: Success after binutils: 8 commits discards c8bc4d56cf3 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 5d8eec88af3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 60ff1151463 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards a75cf98d046 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 72f728fa28b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards f1fe2431b1c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 620504ebb2a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 8c53ccd47f3 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 85be3c9e363 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 7c576a7b977 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 13d1023d5de 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 69fb4c92101 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 14daeb25736 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 2554e2fe6e1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 5d7782eedab 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards bb3a4b12e19 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 4d21927aef8 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 968d977eedc 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 36c09c6c299 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 93578d7f3ce 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 0e87ddc9074 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards fb68a452d5a 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 777cdbbf12f 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 9ec68d2ea88 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards d90340ceea9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards eff85292727 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 777d861975b 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards df138a70b4d 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 08a8ddbfb3d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 6c797f2ac00 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8a4ecc86f94 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 78cb71c784d 16: onsuccess: 1: Successful build after binutils: 4 commits new a1356bf704c 16: onsuccess: 1: Successful build after binutils: 4 commits new 9c2696f0b23 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 5125295f7e2 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 38d7e14992b 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6861853b391 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 144125b2989 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new bffd38a4192 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new a635334c3d8 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 7f2b0951d30 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 88881cb4547 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 973982325cd 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 9586c845424 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 07839da339c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 0f1938a8a58 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 0a0245f078c 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 35668186f53 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 07e118838c3 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 756279b2cc8 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 2063f1f05af 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 149a615e7bd 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new a29630d6d37 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new adb2a1a133d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new c88359a8880 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new fd584ac3297 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new da2d70d467e 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 501ccf5ca5a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new a45d9bdfd18 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 612bcce173c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new f1ebda3bf06 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new fe99c4f1181 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new e5562e15e12 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new fd91cbf4d7a 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new e84b6253403 48: onsuccess: #782: 1: Success after binutils: 8 commits new e9ac5e0d943 49: onsuccess: #785: 1: Success after binutils: 12 commits new f013d2e6bd5 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 78dab1d3de8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 45deaf04ead 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new d6a9c5d47f4 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 5a63868cefd 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new d09d0fda76b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 511176289f5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 3fec95dbc55 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 2ec6f75f806 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 3777cef88fd 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new f563fd2cc5d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 9dfbef358a5 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 62bf2f51344 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 16f4e2ecb2a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new e872c349dd7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 2b0ee1099aa 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new f8d1fac818c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 6f44246be02 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new bc2132e9bcd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 29d460bf2a9 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new f9fc52f5ba5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 81598cfc19c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 2cf361fb8e1 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new d3f39085def 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new de30ab8a902 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new e1ee03affaa 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new c3dc70d46a5 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 17237923040 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new fe9ed2f32f0 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new ddba7881ee0 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 74c37202d6b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 20ec736541f 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 56728f2f1e3 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 0fcc244e57e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new cfdbe1fae53 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new be3dbb9f3ea 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 41f56e9bf9a 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 8263d82e33b 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new dddc7f043fd 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 64b76ed2468 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new f5e5e77349f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new f6a5cc217f6 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 156929c08e8 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 59c9ed5e8fc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 7e634b276ee 94: onsuccess: #832: 1: Success after binutils: 5 commits new c2d03cd1f15 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7dd3c737f28 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new acbc791f106 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new dcfb8230483 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 442b36b0b31 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 8b6c871522d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new fb0885f2c45 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 20a8791bbcd 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 73b6b21b7af 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new d749caccc1c 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 2bb316a52e5 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 781197c3025 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 106f340d4f8 107: onsuccess: #849: 1: Success after binutils: 5 commits new 9d93519a573 108: onsuccess: #850: 1: Success after gcc: 2 commits new 17b31598e95 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new b8ab31dbf3e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 7690cceafbf 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new d3c1edfb85b 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new f22a3607507 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new af7a0b9ca02 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 81226115b8c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 40efbef006b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 7d087f36a29 117: onsuccess: #861: 1: Success after binutils: 18 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 (82dbb614d0a) \ 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 1752 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39056 -> 39540 bytes 04-build_abe-gcc/console.log.xz | Bin 214372 -> 213456 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 8832 bytes 07-build_abe-glibc/console.log.xz | Bin 245628 -> 244988 bytes 08-build_abe-gdb/console.log.xz | Bin 38772 -> 38960 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3872 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2788 -> 2852 bytes 11-check_regression/console.log.xz | Bin 6152 -> 4780 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 61 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 3769508 -> 3750260 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3305656 -> 3289536 bytes sumfiles/gcc.sum | 4812 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1080036 -> 1082992 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231932 -> 231200 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453412 -> 453136 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2578 insertions(+), 2629 deletions(-)