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_build/master-arm in repository toolchain/ci/base-artifacts.
discards abd34fa1da 507: onsuccess: #54: 7: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4b4c764c9b 506: onsuccess: #53: 7: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2585f4d530 505: onsuccess: #52: 7: [TCWG CI] Success after binutils/gcc [...] discards 4953488199 504: onsuccess: #51: 7: [TCWG CI] Success after binutils/gcc [...] discards e08ba0502b 503: onsuccess: #50: 7: [TCWG CI] Success after binutils/gcc [...] discards 8b9c2432d7 502: onsuccess: #49: 7: [TCWG CI] Success after binutils/gcc [...] discards 0758026930 501: onsuccess: #47: 7: [TCWG CI] Success after binutils/gcc [...] discards 8c395e75a7 500: onsuccess: #46: 7: [TCWG CI] Success after binutils/gcc [...] discards 247bb3ee1e 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/gcc [...] discards facd3f0c2d 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/gcc [...] discards 7445926e56 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/gcc [...] discards 79d59ee141 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/gcc [...] discards 772bf09ee5 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/gcc [...] discards fa1bf0aec5 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/gcc [...] discards 68da4051b3 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/gcc [...] discards 7212474917 492: onsuccess: #37: 7: Success after binutils/gcc/linux/gli [...] discards abf103128c 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gdb [...] discards 5dcabb7ce6 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gdb [...] discards 8ef7f70ba3 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gdb [...] discards be5753b714 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gli [...] discards 84d8167f9c 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gdb [...] discards 01e5b7a7d4 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gdb [...] discards 888a7f825d 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gdb [...] discards 1deb34ba88 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gdb [...] discards c83d98a418 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gdb [...] discards 21e57d6f75 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gdb [...] discards 7c1c4a2d58 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gli [...] discards 670364374d 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gli [...] discards 5a68971f91 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gdb [...] discards 0a9036d548 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gdb [...] discards 0975795b19 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gli [...] discards ecb04b6be9 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gdb [...] discards 758ee4259b 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gli [...] discards 32e5e7d5eb 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gli [...] discards 95d40e8ce1 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gli [...] discards 31946a0932 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gdb [...] discards b86eb98b13 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gdb [...] discards 61f5a3f6ec 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gdb [...] discards 71bd782ff5 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gli [...] discards b52ca8929d 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gli [...] discards 98ac6fd3d5 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gli [...] discards f7ef175edf 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gli [...] discards 2dea5c714e 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb: [...] discards cf99d62807 464: onsuccess: #8: 7: Success after binutils/gcc/linux/glib [...] discards 634481386e 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits discards 1d2ffe99f3 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits discards 2a08e86e1c 461: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] discards e926fe3dce 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits discards 8db22d5814 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] discards b8979fcef8 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits discards c692b5c112 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] discards 3869428b3a 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] discards cce4f871e8 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] discards 6e0c642f28 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] discards 86c12202fd 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] discards c05c4401a4 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] discards 22c8e45ad1 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] discards 410e112764 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] discards d24da811e6 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] discards 4fa17dacfa 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] discards 7da54de1ef 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] discards 8d3f5cfed0 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] discards a091bb9986 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] discards bf15dda60a 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] discards a6ecb5f4e5 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards a4c2614077 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] discards 460bdb16f9 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards 91ea514094 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits discards f17d438a01 439: onsuccess: #2176: 7: Success after linux: 11 commits discards 824fe1eaad 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards d5857688b9 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards c1e41ad182 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] discards 29c47960f1 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] discards c01a1373a2 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards bf88768c0d 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] discards 0da59fd95b 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] discards 21f246bc5e 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] discards b4046fe063 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] discards bf409167f6 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] discards f6957f7c3e 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] discards 491f3d8269 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards ee60e29f2c 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] discards c991c321cc 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] discards e9f698f147 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] discards ac446a3fc6 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits discards e377acf241 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] discards c6d5065c82 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] discards ba5bb4626c 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards b4aa5a00b8 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards bcdd9125b1 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards 92dbf9137d 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 93ebf40982 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards aea32ccf1a 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards 09e7dda5ec 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards b67b6db2e8 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards c470a8ff82 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards e64d92137f 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 82dd0e57c8 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 0dba1aa4b5 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards a3a1279129 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards d14cd9eb6f 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new f7ab072bfe 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new 9adb3cea85 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new 5379132758 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 61bd4b00ed 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new 4c3eed7175 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new dae9b3a631 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new 19dbd5d01d 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new e915f1230b 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 4f906890d6 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new 653313e56c 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 5182831573 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 91503c7330 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new ee4aca1685 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new ac19c4ab54 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new 5853a7213d 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] new 3f3ce4d6a3 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] new e28e30c7b1 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits new e2d2e5f644 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] new af030b91da 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] new 32c24ec895 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] new aae3cd7a74 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new f8d1afdf8d 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] new 33f5236957 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] new def9e69f2b 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] new ce5edff09a 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] new 01f720e5b4 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] new 4efa8559f5 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] new e770866c33 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new 5f9316cfe5 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] new c062a333b5 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] new 89d799eff7 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new d4db2147b8 438: onsuccess: #2175: 7: Success after gcc: 7 commits new a785157f02 439: onsuccess: #2176: 7: Success after linux: 11 commits new 7dbb0d9fe6 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits new 5d2f7ddd74 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new b965c5b3d6 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] new f6f800a11f 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new d63c2e4122 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] new 994877df70 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] new 32106d3562 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] new 998224054c 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] new 7ff104aa63 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] new 04bff70807 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] new 9cfc05df19 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] new e4200d2dc3 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] new 55486da3f8 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] new 2a524bd409 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] new ddfdb709f3 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] new 57732e2fd5 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] new 15bc71a425 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] new e3794106bb 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] new 4346de18b4 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits new 3b0817846a 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] new b6074b65c0 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits new 4c42e893a3 461: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] new 24c5dac053 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits new 362d2ad4fd 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits new 74df9f131a 464: onsuccess: #8: 7: Success after binutils/gcc/linux/glib [...] new 2062de7fa4 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb: [...] new 44a8a2e2e5 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gli [...] new a0b9490f23 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gli [...] new 1707e7aafa 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gli [...] new 5bc100a9ec 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gli [...] new 31622fc64a 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gdb [...] new 0ea29ff182 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gdb [...] new b7ac7e09de 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gdb [...] new d6921b2be9 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gli [...] new 3608299a12 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gli [...] new 5324bf9276 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gli [...] new d013e1b052 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gdb [...] new 1a43cda92c 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gli [...] new 14e229bad9 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gdb [...] new 14f21ea093 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gdb [...] new 516b812598 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gli [...] new 15070dd10d 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gli [...] new c122109009 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gdb [...] new ef374ad0ca 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gdb [...] new 50b3e54a52 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gdb [...] new d1c6413283 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gdb [...] new 05e337b1fa 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gdb [...] new a122bd5b82 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gdb [...] new 9da657acdd 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gli [...] new 7c1df7d4c3 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gdb [...] new e2e248ce84 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gdb [...] new 50bfc6cd32 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gdb [...] new c0db8b7cd7 492: onsuccess: #37: 7: Success after binutils/gcc/linux/gli [...] new 1a748d3884 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/gcc [...] new cb64a938b2 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/gcc [...] new 128aa6d9a4 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/gcc [...] new 45788aa193 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/gcc [...] new f3cd7c0796 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/gcc [...] new 06421123bd 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/gcc [...] new 71026518d3 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/gcc [...] new 512a845178 500: onsuccess: #46: 7: [TCWG CI] Success after binutils/gcc [...] new 815f2ea679 501: onsuccess: #47: 7: [TCWG CI] Success after binutils/gcc [...] new 875bfa02d5 502: onsuccess: #49: 7: [TCWG CI] Success after binutils/gcc [...] new d817022010 503: onsuccess: #50: 7: [TCWG CI] Success after binutils/gcc [...] new d0abdcc9ff 504: onsuccess: #51: 7: [TCWG CI] Success after binutils/gcc [...] new ba89f37303 505: onsuccess: #52: 7: [TCWG CI] Success after binutils/gcc [...] new bb28db1a3b 506: onsuccess: #53: 7: [TCWG CI] https://ci.linaro.org/job/ [...] new 3dc2f4e183 507: onsuccess: #54: 7: [TCWG CI] https://ci.linaro.org/job/ [...] new e6b5b70a1d 508: onsuccess: #55: 7: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (abd34fa1da) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 2268 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2512 bytes 04-build_abe-binutils/console.log.xz | Bin 26836 -> 26936 bytes 05-build_abe-stage1/console.log.xz | Bin 89372 -> 89460 bytes 07-build_abe-linux/console.log.xz | Bin 8624 -> 8804 bytes 08-build_abe-glibc/console.log.xz | Bin 232472 -> 232756 bytes 09-build_abe-stage2/console.log.xz | Bin 225116 -> 224944 bytes 10-build_abe-gdb/console.log.xz | Bin 34584 -> 34644 bytes 11-build_abe-qemu/console.log.xz | Bin 31628 -> 30900 bytes 12-check_regression/console.log.xz | Bin 1300 -> 552 bytes 13-update_baseline/console.log | 44 ++++++++++---------- dashboard/dashboard-generate.sh | 17 -------- dashboard/dashboard-push.sh | 7 ---- .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 ---- jenkins/notify.sh | 2 +- manifest.sh | 46 ++++++++++----------- 23 files changed, 51 insertions(+), 85 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh