Buildbot page is messed up,a 502 Bad Gateway this time.
When will the revert of the shadergen static commit be done so users can safely grab a newer build once the site is back in working order?
I had to deal with a nightmare on newer builds due to that one commit causing "sigsevs" seen in the issues list and I had it freeze my Shield TV Pro twice (hard drive=risky business) before finding out,forcing me to unplug it as a result both times.
I hope this didn't/doesn't end up bricking unlocked/rooted users.
When will the revert of the shadergen static commit be done so users can safely grab a newer build once the site is back in working order?
I had to deal with a nightmare on newer builds due to that one commit causing "sigsevs" seen in the issues list and I had it freeze my Shield TV Pro twice (hard drive=risky business) before finding out,forcing me to unplug it as a result both times.
I hope this didn't/doesn't end up bricking unlocked/rooted users.
Shield TV Pro (stock/non-rooted OTA 6.3)
Acer Aspire E 15 E5-575G-59EE
CPU: i5-6200U 2.3-2.8Ghz _ GPU: Nvidia GeForce 940MX 2GB (GDDR5) VRAM
Hyundai 8GB DDR4 Dual-channel SDRAM _ 1000GB HDD
New; CPU: Intel i9 9900KF_ GPU: Nvidia RTX 2060 Super | ◕‿◕
Acer Aspire E 15 E5-575G-59EE
CPU: i5-6200U 2.3-2.8Ghz _ GPU: Nvidia GeForce 940MX 2GB (GDDR5) VRAM
Hyundai 8GB DDR4 Dual-channel SDRAM _ 1000GB HDD
New; CPU: Intel i9 9900KF_ GPU: Nvidia RTX 2060 Super | ◕‿◕
