• Basic upgrade CI testing

    From Andreas K. Huettel@21:1/5 to All on Thu Nov 4 00:44:51 2021
    Copy: ulm@gentoo.org (Ulrich Mueller)
    Copy: whissi@gentoo.org (Thomas Deutschmann)
    Copy: antarus@gentoo.org (Alec Warner)

    I think the obvious easy solution here is to run a CI that is using
    older stuff, and report problems when commits break that.

    Something that's been bouncing around my head:

    * archive stage3 files somewhere official

    * run a weekly CI job that attempts to upgrade a N-weeks old
    stage3 to current, with "emerge -uDNav world"

    * for N=1,2,4,8,16,32 etc

    * if it fails, annoy people

    Limitations:
    1) covers only stage3
    2) solutions may not always be obvious
    3) culprits may not always be obvious

    --
    Andreas K. Hüttel
    dilfridge@gentoo.org
    Gentoo Linux developer
    (council, toolchain, base-system, perl, libreoffice)
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2

    iQKTBAABCgB9FiEE6W4INB9YeKX6Qpi1TEn3nlTQogYFAmGDHvNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU5 NkUwODM0MUY1ODc4QTVGQTQyOThCNTRDNDlGNzlFNTREMEEyMDYACgkQTEn3nlTQ ogZrfg/7BS10EVUL9D5seVdBB0N3hPGrcibTfXCVgZZ4IYOgqOx2ebVHzegyrTKo +W8k1/Zdx637T9QIO+hX3RXVpIKDyxF6SQzDCjuWNxRf1KGyQPS2zyzTvjn2VQIb Id+MTMmz8Z7ikHeR7QRNuASXxy5ikJkXmPivIo/I6IotTLjswHtpS/jcuQu9FsQM n4eegITENAQ8sfUx+w8ZnbgyHdiqGPkeoUBuDzByRGeBwaCmNG6/3OZm0NfOqbnG QJYc3CjUijT9tU/M/205L08oPPpZGzA144aekuVO7lC6hBQIjnHJNiWRMKmyjp3g /OW3TremVLT4Tvsue9GVrC8ulbLdwmuBay5Y4qFvL7pV9iYo2kGUAZx1clb9CRS8 docru8mklbqHXRarX85UTiEUzjuTEPaEZAT3297aJ6NxR23zUOSSgc5aaRHl/thP 7qjAUenOp/e3fqJDYS4wtSc8K6P/Z5MzcGUVIDavWN5ERw1ICYoFfKm9mb7aRxVv PrGK5lFfV7Yu33nL6V4oX9CjNhqfZajMBZXOn06OuQUg2uXTD3Lo+HDW0rK5yECV 5OhnOPIX32dlsesofL37m4/aqiQb7VjLqm4doyRoP85IDm8fFbB5HDfN