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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts.
discards e26de80a863a 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 7b7feddcba9d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 2f9dc38fbdc9 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 55a39b9f2a1f 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 7b5b1601be12 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 905ee3414d9c 123: onsuccess: #655: 1: Success after binutils: 22 commits discards e22a7dcd29d6 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards afb84407bd48 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 78c3b7f7a0f7 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 48b0eb3adb2f 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 55fbc7d720cb 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 15a164d5785a 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 463dea14e17e 116: onsuccess: #647: 1: Success after linux: 3 commits discards 801132b1e3ec 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 9059b3b9172d 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards b194f5ddb53f 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 2387d4da28b4 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards ed84fbe53c53 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards 0c4d9d0b9b89 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards 4147d4938cb8 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards 9b0876512ec9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 14a01c4b22f5 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards b851a109a691 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 7f81f884c1e1 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 3e1db567f588 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards 6165fac1e635 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] discards b870974e0291 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] discards 1f77a59c6461 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards dc22c40e629e 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 0ea70a7dab15 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards db5519d83df7 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 1e8f2eae7c1f 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 4349d9f4688e 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 485707054d97 95: onsuccess: #619: 1: Success after binutils: 5 commits discards a07be42185b8 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 612a2bc5ee92 93: onsuccess: #613: 1: Success after binutils: 19 commits discards bf12d2fad1bb 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards cb0d25a038b2 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards e8e4d0622098 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 832620739bcc 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 18a5f688b77e 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 9ff4fdae7eec 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0a3163595952 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 1f9ce9baebe9 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards bd3ba3728dae 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 5c2d445925e5 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards ee5c80e473bf 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 98434079438c 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 1e591f587131 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 92143c1944ed 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 42e03cd9534a 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 8cf9a09b6829 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards ffcce32d4ef0 76: onsuccess: #592: 1: Success after linux: 63 commits discards 9e3f93ffe431 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 2f3a80af5ee8 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 9c3b2d34fd58 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards c5b5f5913718 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards df36f01c8588 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 92e38ae037d2 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 7651b3b05d2a 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 867f12fc2136 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 8369e1e7af92 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards 3eaa7df5029f 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards fe1400f967a9 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards a334ac891858 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards dba9b0d0f79e 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 26eca6349d23 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards da789fc16694 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards f7704efe86dc 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards e10779461e92 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 26b1bdca79c4 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 3e9cc160710d 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards bc48fd7b9a2d 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 154c1b6333da 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards b4f0d4a6a567 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 664f8c8b383d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards c90bd4fc03ec 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards d6d3d2d260da 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 375c19daae4e 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 148a018b2631 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 0949683d9b1b 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 80cc5a89b702 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 8ed342c0707f 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 95b63acc9ca8 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 4ab9984b90cc 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 33818566a6df 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 4474675a1568 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 445ce749a0a3 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] discards 714af9ba3b61 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards ab9ede92130a 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] discards 743432f434b1 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 36782a686c24 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] discards e5f09b32538b 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards f59fda3e808e 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 439cf73d0e16 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 6cead925b534 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards c86c96ef481b 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 838ac1bfc850 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 57711f95b20d 30: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] discards 76a41a08c342 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 7205ecd3dcaf 28: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new f2c2e321dd88 28: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 0a116ff0deed 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 1ba96c305b57 30: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new 56ccc9be66b2 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 1698972210aa 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new f64b1665179f 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new 11c9daf7c2e3 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 2ecb524c2705 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new d1c508493619 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 6b5e94d97462 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] new 08809b5448e6 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 848ba603546e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] new b412b2741bdf 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 9f2e85f3d10b 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] new bc2f1758b496 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new b8d20d1aa06c 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new c5f4ae5dc9a0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new cce4ab75f1e9 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 6ede67f0e9e8 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new fffd93467b43 47: onsuccess: #556: 1: Success after binutils: 12 commits new c6f71c4ccb98 48: onsuccess: #559: 1: Success after binutils: 6 commits new df2d2bd0d1c8 49: onsuccess: #562: 1: Success after binutils: 9 commits new f85e7364501b 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 62b6c2643d00 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 2a089516543d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new bd79c794b99f 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 13c6aa366a76 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new a5e8dae70e4d 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 584b19159b90 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 568823a53e39 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 3989eda37e93 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 38f76eacd0e1 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 145dfd1abfc6 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new ae3ec9f89488 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new ea290649d27a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 52841b001612 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 360501971794 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 1e820ba667bd 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new 65048ad59c2d 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new ee2517dd32e9 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 2694e66b7aaa 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 4749c4d80182 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 9e434b5493da 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 7294a5ece2f7 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 09b5fc839b78 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new ffbcac1c1770 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 5d0e081f1c51 74: onsuccess: #590: 1: Success after binutils: 16 commits new 9d7982dbdee2 75: onsuccess: #591: 1: Success after gcc: 25 commits new e4d7a31b39fc 76: onsuccess: #592: 1: Success after linux: 63 commits new 770861bdfe1b 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 272452375ab4 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new e5e1dd672127 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new f7e6f0cc4209 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new d1a20cf74af8 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 8725a80b845e 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 83bf4b6562ec 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new c5a1d17128ca 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 8ea33feed6b1 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new b61a6de3ddd8 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 7c95ffaadd38 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new aad1051b5377 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new c9d4e8f2e85f 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new fb84d5a0fbb1 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 0e3fbaf3097e 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 77659fb94424 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 96bac62075b3 93: onsuccess: #613: 1: Success after binutils: 19 commits new 911762e5030f 94: onsuccess: #616: 1: Success after binutils: 2 commits new fd74f1e3b8d1 95: onsuccess: #619: 1: Success after binutils: 5 commits new 41c501670b06 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 712c4010b783 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new eef8b9e72406 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new e7a4ea4cca3b 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 59a7d957bf64 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new d1b074fb3d0d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new b7e54e774301 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] new c60b4cdecb02 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] new 4fce703f385c 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new 473ea4b304b0 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new 3687cd214871 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 71bbbc04a4e1 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new 9bc96422867c 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new b6c7d6da3045 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new 2afeac9e86da 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new ab325b0866d1 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 3dfa0f6d9053 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 104abdf86d73 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new b1d49c1afdb2 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 907a4f7767d3 115: onsuccess: #645: 1: Success after binutils: 27 commits new 2b1ebe550ed3 116: onsuccess: #647: 1: Success after linux: 3 commits new 022e803ea546 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new 28b9b5bd251e 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 64909d66a9f1 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 7d017a8a6d05 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new b0b80f7eea7c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new e1a9727906dc 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 93a03d3587c4 123: onsuccess: #655: 1: Success after binutils: 22 commits new 67e194627247 124: onsuccess: #657: 1: Success after glibc: 2 commits new c98dc08ffc91 125: onsuccess: #658: 1: Success after linux: 3224 commits new 05abb3adc7d3 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 87a5ee122f89 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new d0460eed1c8d 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new f9ce3baa051f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...]
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 (e26de80a863a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
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 1768 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40360 -> 40696 bytes 04-build_abe-gcc/console.log.xz | Bin 215972 -> 216176 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 243968 -> 243760 bytes 08-build_abe-gdb/console.log.xz | Bin 40464 -> 40164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2484 -> 2620 bytes 11-check_regression/console.log.xz | Bin 6436 -> 6068 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 29 ++- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 63136 -> 63452 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 83804 -> 83856 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 121740 -> 121916 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 409 insertions(+), 399 deletions(-)