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_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 4d9d5799c6 478: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b919151adb 477: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c548464485 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards aaedb0b8cc 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 95b38da96e 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards dd32fd1d87 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 614ac825b5 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bc84efcd2a 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards dec4f6a5be 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards f7fc583ce2 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards b65cdc8d91 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards cdefe24706 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards d7daf0ed77 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 97b8a2b34a 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards a3b4b6ed31 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards abd61d0913 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards ec787bce83 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 2241ff4da4 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6ebfde9a49 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards e88b311423 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 38c33141b2 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards e9e8ffa757 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards dbce2c9865 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 550ca2b93f 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 90e7264de0 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 10593048c6 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards cebc8b9f0b 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards f52dbfa9dc 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 58cc0929ef 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 114b5b0502 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 4bb7c13409 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards aedda156cd 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards f954d6f1b1 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards e4e8d81408 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards bb474f7cb5 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 23d51cc42c 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards 249450e488 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards f363cf7944 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards d4bc7f2d23 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards f08942865c 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a9df56a984 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 812dbb845f 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 28ef0b6d3d 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards f4cf8cf7bb 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 540597cd1a 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards ac65f80b11 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 99cf21305a 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards bc65da3a46 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 18c9487550 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 0650cc6062 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 0dd7eaeac1 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards e1fc956008 427: onsuccess: #7: 1: Success after linux: 26 commits discards ec1fb262dd 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 9991b4c5fc 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 1f850e1830 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 5aaac4e22a 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 98bafd16da 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards d173aa11d0 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 2820e5e4e4 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards edae340c58 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 07d2e68c47 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 83471006e2 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards bc7457eb43 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 17c40817d8 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 3a57d678a4 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards d423432cc8 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 08e9816620 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards bce276b7b1 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards eeec17c956 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards f54096f61d 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 2982802386 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 3e735c4016 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards e69676bcd5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 7baaf074fb 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 7ae6530524 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 4c0946c369 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 13a2621f2b 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards d79cc98cb7 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards d87eca4fe0 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 9c7db59dee 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 52a502c7a1 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 6294840169 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 89da4cb12a 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 26a7fcbdd9 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards a87b9bd10a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards e1c515bbbf 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards ecbaf44c5c 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards de12b2fd36 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 16bbcdf27c 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 4e96c6b427 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 4061f2919a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards e533e8f61c 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 47369f55bd 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards dd90189833 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 0d43bb645e 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards cada6b04a0 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 5a1817d90f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 44ef7d1dfb 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards d4bf86c984 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards f7303396d8 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 5028abb8ce 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new bc64eba0f7 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new f8cf76c18c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 04688bc47e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 7862c50f87 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 94ef75864b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 6dbb9aea00 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new f5af287ade 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 54d6926fe3 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 02f37003f4 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 9bdf287735 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 8bc166fda7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new e36cc78258 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 7918427ed8 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 63f80dba85 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 2d17c0fff6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new bc81190210 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 19cd9b951a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 8e86d1faf2 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new a438babb56 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 0e8db05994 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new b8a9af3d09 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 0f4e51b371 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 64ec80c051 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 0585776520 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 1f772852f7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 0357fdf424 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new b396d442b2 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new fb9f473107 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 40fa5b2192 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new f6c05be69d 407: onsuccess: #2661: 1: Success after gcc: 7 commits new f369dc2729 408: onsuccess: #2662: 1: Success after linux: 11 commits new c98e0bd4f5 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 39cc4faeab 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new de5411c6d5 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 269c6b675b 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new a160e13733 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 3e31811b66 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 4f5ea3e715 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new e9c4f6f83e 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 127f299771 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new d7fa759281 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 0fea1755c7 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 1e53a4a16b 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 9de9c02539 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 8be2b133ad 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 667406bb8a 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new acc389c7b5 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new cfa6d52af5 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 368d06f243 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 054721a496 427: onsuccess: #7: 1: Success after linux: 26 commits new 9e6cb7978f 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 82aca5a7af 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 3955d8d6db 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 47222d7d25 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new d634839754 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new 3a5d64bd5a 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 04373854b8 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 09e02b0d7e 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 40c3f34395 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new cead5744ef 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 83fdb5cd78 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new c74053c2dd 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new da2bf9cdfa 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 9ed69cffdc 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new a45ab40991 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 3b74d65564 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 6b51969be0 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new 6d0fd5c0e1 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new c9beaac9ae 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 5a946a6a07 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 1880db4d86 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 475d0ac59d 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 7ba112fed6 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new c54e99d9c6 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 1ad50a53f4 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new ee7a931381 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 1c3e788f2b 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 1f6acc2116 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new a4b2c38bf3 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new c4e7d7ae3f 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 352f368f62 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 78d888f89c 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 53534e3714 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 7580aea5ec 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new fafe0756a3 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 4c33f491b1 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 5e08a65215 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 9cead6db70 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new c95b1cee5f 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 1e3159127f 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new b9e8af478a 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a3b0d7a939 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 414440e1a3 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new af14c910ba 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4ebc17859f 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d99745bfe2 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 94d78f4aeb 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ad1b226a87 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c0c022654c 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new aafb0c4a43 477: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 64aad292c1 478: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c440fbf2a6 479: onsuccess: #65: 1: [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 (4d9d5799c6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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: 00-sumfiles/g++.log.0.xz | Bin 0 -> 3405888 bytes sumfiles/g++.sum => 00-sumfiles/g++.sum.0 | 0 00-sumfiles/gcc.log.0.xz | Bin 0 -> 3033920 bytes 00-sumfiles/gcc.log.1.xz | Bin 0 -> 124008 bytes sumfiles/gcc.sum => 00-sumfiles/gcc.sum.0 | 12 +- 00-sumfiles/gcc.sum.1 | 8813 ++++++++++ 00-sumfiles/gfortran.log.0.xz | Bin 0 -> 1047120 bytes .../gfortran.sum => 00-sumfiles/gfortran.sum.0 | 0 00-sumfiles/libatomic.log.0.xz | Bin 0 -> 2312 bytes .../libatomic.sum => 00-sumfiles/libatomic.sum.0 | 2 +- 00-sumfiles/libgomp.log.0.xz | Bin 0 -> 217888 bytes sumfiles/libgomp.sum => 00-sumfiles/libgomp.sum.0 | 2 +- 00-sumfiles/libitm.log.0.xz | Bin 0 -> 2676 bytes sumfiles/libitm.sum => 00-sumfiles/libitm.sum.0 | 2 +- 00-sumfiles/libstdc++.log.0.xz | Bin 0 -> 436868 bytes .../libstdc++.sum => 00-sumfiles/libstdc++.sum.0 | 6 +- 01-reset_artifacts/console.log.xz | Bin 2076 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2448 -> 2416 bytes 03-build_abe-binutils/console.log.xz | Bin 27240 -> 27256 bytes 04-build_abe-stage1/console.log.xz | Bin 71480 -> 71216 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 241052 -> 241704 bytes 08-build_abe-stage2/console.log.xz | Bin 201444 -> 201292 bytes 09-build_abe-gdb/console.log.xz | Bin 34824 -> 34912 bytes 10-build_abe-qemu/console.log.xz | Bin 31016 -> 29860 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 5952 -> 6432 bytes 12-build_abe-check_gcc/flaky.xfail | 1 + 13-check_regression/console.log.xz | Bin 2984 -> 1792 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 43 - 13-check_regression/results.compare | 74 +- 13-check_regression/results.compare2 | 107 +- 13-check_regression/results.regressions | 93 - 14-update_baseline/console.log | 60 +- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 74 +- mail/results.regressions | 93 - manifest.sh | 29 +- results | 93 - sumfiles/g++.log.sep.xz | Bin 175364 -> 0 bytes sumfiles/g++.log.xz | Bin 3397124 -> 0 bytes sumfiles/g++.sum | 4 + sumfiles/g++.sum.sep | 17187 ------------------- sumfiles/gcc.log.sep.xz | Bin 242392 -> 0 bytes sumfiles/gcc.log.xz | Bin 3032060 -> 0 bytes sumfiles/gcc.sum | 50 +- sumfiles/gcc.sum.sep | 7577 -------- sumfiles/gfortran.log.sep.xz | Bin 199812 -> 0 bytes sumfiles/gfortran.log.xz | Bin 1045120 -> 0 bytes sumfiles/gfortran.sum | 4 + sumfiles/gfortran.sum.sep | 3503 ---- sumfiles/libatomic.log.xz | Bin 2320 -> 0 bytes sumfiles/libatomic.sum | 6 +- sumfiles/libgomp.log.xz | Bin 217988 -> 0 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2676 -> 0 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.sep.xz | Bin 12004 -> 0 bytes sumfiles/libstdc++.log.xz | Bin 438200 -> 0 bytes sumfiles/libstdc++.sum | 10 +- sumfiles/libstdc++.sum.sep | 229 - sumfiles/xfails.xfail | 544 + 64 files changed, 9520 insertions(+), 29115 deletions(-) create mode 100644 00-sumfiles/g++.log.0.xz copy sumfiles/g++.sum => 00-sumfiles/g++.sum.0 (100%) create mode 100644 00-sumfiles/gcc.log.0.xz create mode 100644 00-sumfiles/gcc.log.1.xz copy sumfiles/gcc.sum => 00-sumfiles/gcc.sum.0 (99%) create mode 100644 00-sumfiles/gcc.sum.1 create mode 100644 00-sumfiles/gfortran.log.0.xz copy sumfiles/gfortran.sum => 00-sumfiles/gfortran.sum.0 (100%) create mode 100644 00-sumfiles/libatomic.log.0.xz copy sumfiles/libatomic.sum => 00-sumfiles/libatomic.sum.0 (98%) create mode 100644 00-sumfiles/libgomp.log.0.xz copy sumfiles/libgomp.sum => 00-sumfiles/libgomp.sum.0 (99%) create mode 100644 00-sumfiles/libitm.log.0.xz copy sumfiles/libitm.sum => 00-sumfiles/libitm.sum.0 (97%) create mode 100644 00-sumfiles/libstdc++.log.0.xz copy sumfiles/libstdc++.sum => 00-sumfiles/libstdc++.sum.0 (99%) create mode 100644 12-build_abe-check_gcc/flaky.xfail delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions delete mode 100644 mail/results.regressions delete mode 100644 sumfiles/g++.log.sep.xz delete mode 100644 sumfiles/g++.log.xz delete mode 100644 sumfiles/g++.sum.sep delete mode 100644 sumfiles/gcc.log.sep.xz delete mode 100644 sumfiles/gcc.log.xz delete mode 100644 sumfiles/gcc.sum.sep delete mode 100644 sumfiles/gfortran.log.sep.xz delete mode 100644 sumfiles/gfortran.log.xz delete mode 100644 sumfiles/gfortran.sum.sep delete mode 100644 sumfiles/libatomic.log.xz delete mode 100644 sumfiles/libgomp.log.xz delete mode 100644 sumfiles/libitm.log.xz delete mode 100644 sumfiles/libstdc++.log.sep.xz delete mode 100644 sumfiles/libstdc++.log.xz delete mode 100644 sumfiles/libstdc++.sum.sep