FYI, I've just recently re-connected Appveyor, after noticing that AppVeyor integration got broken for 6 months, and that Mesa MSVC builds got broken for two months.
I configured AppVeyor only build master, but it seems that it's not effective, unless one modifies appveyor.yml itself. At any rate, notifications are setup to notify only when build changes state (pass <-> fail) so hopefully it won't spam the list, even on branches (such as 20.3) where MSVC stays broken. If that doesn't work I can always drop mesa-dev from the list. Jose ________________________________ From: mesa-dev <[email protected]> on behalf of AppVeyor <[email protected]> Sent: Wednesday, November 25, 2020 18:28 To: [email protected] <[email protected]> Subject: [Mesa-dev] [AppVeyor] mesa staging/20.3 #20 failed Build mesa 20 failed<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.appveyor.com%2Fproject%2Fmesa3d%2Fmesa-ftwhm%2Fbuilds%2F36511344&data=04%7C01%7Cjfonseca%40vmware.com%7Cd977a25a3bca43cf50bf08d8916ff8ba%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637419257398121221%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kLVRwAWBfyX%2Bk9igxBFwX1IWqOg3qzexKvBYdRUzU1Q%3D&reserved=0> Commit 0cbc19416a by Dylan Baker<mailto:[email protected]> on 11/25/2020 6:15 PM: .pick_status.json: Update to ff9ea469f6b319cb07ee1ebbb687fa19c9d48e1c Configure your notification preferences<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.appveyor.com%2Fnotifications&data=04%7C01%7Cjfonseca%40vmware.com%7Cd977a25a3bca43cf50bf08d8916ff8ba%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637419257398121221%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lI%2BXqF4zPuzdQ9TwbeGVEtr1UUXXT1jY%2FJkPA5BcxAw%3D&reserved=0>
_______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
