Change:
<ins> diff -u "a/src/linux/integration-test.py" "b/src/linux/integration-test.py" --- a/src/linux/integration-test.py +++ b/src/linux/integration-test.py @@ -870,5 +870,4 @@ self.assertEqual(self.get_dbus_dev_property(bat0_up, 'EnergyFull'), 126.0) self.assertEqual(self.get_dbus_dev_property(bat0_up, 'EnergyFullDesign'), 132.0) self.assertEqual(self.get_dbus_dev_property(bat0_up, 'Voltage'), 12.0) -        self.assertEqual(self.get_dbus_dev_property(bat0_up, 'Percentage'), 40.0) self.stop_daemon() Diff finished.  Tue Nov  8 16:48:57 2022 </ins>

Discussion:
Steps to reproduce the behavior: building KDE on i686 machine. I've been struggling with building KDE for a few recent NixOS versions. I've managed to get it running recently and made 2 MRs that fix it: and . The first one was merged, while the other one wasn't. Creating this as an issue to add as a 22.11 blocker to hopefully get KDE running on i686 in 22.11. Whether it is really a blocker and whether should be merged is up to the dev team to decide of course. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I think it is time to let go of i686-linux. Keeping it around for wine/steam is fine, but we haven't even been able to build firefox for i686-linux since 2020.
Note we also have an RFC covering this. i686-linux is a tier 3 platform. Tier 3 platforms are non-blocking.
The build log in OP is misleading, as that's from 22.05 and doesn't apply anymore. Here's a link that should work all the time:
The build log I've provided as an example of what's going on there in 22.05, the last stable version, trunk may or may not have some other issues on top of the ones present in 22.05, since it obviously changes all the time. Since I'm commenting on this issue again, can someone elaborate on the existence of binary cache for i686? From what I could gather, even if we get Hydra jobs working correctly, the binary cache still wouldn't exist as it was disabled for the entire i686 architecture?
has everything that's built on Immediately.
I'm sorry, but I keep getting conflicting information on this and all of it got me somewhat confused. What about Nix? If a binary cache for i686 should exist and I'm rebuilding Nixos from a local nixpkgs repo copy set to a revision already built Hydra, for example the latest 22.05 revision from , it should not be building Nix from scratch, right? It should get it from the binary cache?
Yes, you do get it (just tried).
Did you try it on i686? For some reason it's trying to build it from scratch for me.

I got i686-linux version of the attribute on the latest channel. You can download e.g. by
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Now upower fails to build. Personally I don't think we need to support i686 beyond wine and steam because 4GB RAM is to little to run nix comfortable anyway and more and more upstream projects done support it. I would vote for closing this.
. Seems like some kind of Python integer precision issue, I'll make an MR to fix it.
A month ago with no reaction so far. Doesn't look promising. We could patch that test downstream, or disable the specific test, if the test runner supports that.