Closed disassembler closed 4 years ago
Regarding the broken NixOS tests for the Hydra module: I can reproduce the timeout locally, so this appears to be an actual issue. Currently investigating why.
Fixed xmonad test in 2442103bb79
FYI the formatting of the first message is kind of borked, which means not all maintainers were tagged. Not sure what's up with it
There is a limit of mentions per message, it's not due to formatting
I'm seeing qtwebengine 5.11 and 5.9 failing with log limit exceeded
I'm guessing a fix similar/same fix as https://github.com/NixOS/nixpkgs/pull/68434 could be used. Though I'm not sure how to confirm it works without a hydra instance.
cc @matthewbauer @d-goldin
@worldofpeace: Yes, it is pretty much identical to #68434 (same code, WebKit/Source/wtf/
being used). Last time I simply compiled locally and confirmed smaller log output.
Thanks @d-goldin. I can produce a PR for this shortly then.
nixpkgs.devpi-server.x86_64-linux
got fixed by #67984
EDIT: wupps, not fixed in staging but in master for some reason
nixpkgs.bees.x86_64-linux
was fixed by #68994.
nixpkgs.ntopng.x86_64-linux was fixed by #69096
Looks like bot fixed a build error :smile:
What's the deal with go failing on i686? I tried building with pkgsCross and I can't reproduce it
not sure why it happens, but the offending lines are
--- FAIL: TestGcSys (0.06s)
gc_test.go:33: expected "OK\n", but got "using too much memory: 44978176 bytes\n"
FAIL
FAIL runtime 21.763s
@rnhmjoj: I have been trying to figure that out for a few days now, off and on, and just couldn't get it to reproduce at all either. There is a little bit of info in https://github.com/NixOS/nixpkgs/pull/70153 and https://github.com/NixOS/nixpkgs/pull/69359 (some upstream fix that didnt really work is linked).
some upstream fix that didnt really work is linked
I have just found about that issue and hoped it could fix the issue... too bad. Given it has been reported the test is flakey, do you think we could temporarily disable it?
Given it has been reported the test is flakey, do you think we could temporarily disable it?
Absolutely :+1: If the test flaky, perhaps it will be fixed in a later release or we could check if other distro's had a similar issue and resolved it. I'm thinking a flaky test being flaky obviously doesn't serve well against warning any possible integration issue.
golang 1.13.1 was released, we could try seeing if a bump fixes it :)
go currently defaults to 1.12.*
in the release. I'm not sure how go handles their versioning but that could be a difficult change to backport to just fix a test. If picking a certain commit didn't fix it it's likely there isn't one.
same, @kalbasit do you have any opinions on this?
We shouldn't be moving to Go 1.13 as the default release just yet. Although Go1compat tells us that the software is not going to break, but there are some areas that may get affected. I recommend disabling the flaky test on the affected arch.
Initially I was more skeptical of disabling the test, because it might have very well been some more serious issue, but if nobody can really reproduce it well and the world is rolling with the versions just fine outside of the test-env, let's just go with it in 19.09.
Here is a proposal: https://github.com/NixOS/nixpkgs/pull/70368
Looks like #70645 accidentally killed a bunch of the nixos.* attributes, for instance by marking kscreen as broken. @disassembler was this intentional?
Yes, that wasn't supposed to happen… Will fix.
blcr removed in commit 923c449e9bf554f0bd0aa2df4d1f857e144eeaf3
I believe these should be closed post-release.
It's usually closed at one of the end of support, or the branch-off or the release of the next version.
It's usually closed at one of the end of support, or the branch-off or the release of the next version.
Ah, feel free to re-open then.
Could we mark all of the remaining as "broken"?
@matthewbauer I believe the RM's did this?
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixos-21-05-zero-hydra-failures/12954/4
Hi all! It's that time of year again! That time nixpkgs contributors look forward occuring twice a year! When we branch of the new release and open a ZHF issue to track it. Lets get started tackling all the issues.
As of today, we have 1502 (hydra build is currently running) failing jobs. For more up-to-date information, check here!
The deal is as before, we want to get this number as close to 0 as possible before the release! If you want to help, which would be much appreciated:
master
branch (orstaging
if it causes a mass rebuild) and mention this issue in your description. If it gets missed out, make sure to cc @NixOS/backports to get it backported (or make a backport PR yourself, in which you also cc the backports team).Getting latest evaluation for http://hydra.nixos.org/jobset/nixos/release-19.09
Parsing evaluation https://hydra.nixos.org/eval/1542173
Failures:
Dependency failures:
Image originally by Dr. K.A.I. Nekaris CC BY-SA 4.0