| 27 Jul 2021 |
hexa | running tests
check flags: SHELL=/nix/store/xvvgw9sb8wk6d2c0j3ybn7sll67s3s4z-bash-4.4-p23/bin/bash VERBOSE=y test
"/nix/store/6qjj8apw48a2bxcp5gm6a2brbp4nnc7y-perl-5.30.3/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Magick.bs blib/arch/auto/Image/Magick/Magick.bs 644
PERL_DL_NONLAZY=1 "/nix/store/6qjj8apw48a2bxcp5gm6a2brbp4nnc7y-perl-5.30.3/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/bzlib/*.t t/jpeg/*.t t/jng/*.t t/png/*.t t/tiff/*.t t/zlib/*.t
t/blob.t .......... ok
t/bzlib/read.t .... ok
t/bzlib/write.t ... ok
t/composite.t ..... ok
t/filter.t ........ ok
t/getattribute.t .. ok
t/jng/read.t ...... ok
t/jng/write.t ..... ok
t/jpeg/read.t ..... ok
t/jpeg/write.t .... ok
t/montage.t ....... Fontconfig error: Cannot load default config file
t/montage.t ....... ok
t/ping.t .......... ok
t/png/read-16.t ... ok
t/png/read.t ...... ok
t/png/write-16.t .. ok
t/png/write.t ..... ok
t/read.t .......... ok
t/setattribute.t .. ok
t/tiff/read.t ..... ok
t/tiff/write.t .... Failed 2/10 subtests
t/write.t ......... ok
t/zlib/read.t ..... ok
t/zlib/write.t .... ok
Test Summary Report
-------------------
t/tiff/write.t (Wstat: 0 Tests: 10 Failed: 2)
Failed tests: 9-10
Files=23, Tests=353, 5 wallclock secs ( 0.20 usr 0.07 sys + 4.89 cusr 1.76 csys = 6.92 CPU)
Result: FAIL
Failed 1/23 test programs. 2/353 subtests failed.
make: *** [Makefile:1039: test_dynamic] Error 255
builder for '/nix/store/b39xmvxbcd98r2fcz5s8lq0a2p0i5nf3-perl5.30.3-PerlMagick-7.0.10.drv' failed with exit code 2
| 08:40:23 |
hexa | can someone restart https://hydra.nixos.org/build/148705173 please? | 10:51:36 |
| 29 Jul 2021 |
hexa | https://hydra.nixos.org/eval/1689692 lots of failures due to the cached aiohttp error that was restart | 08:58:33 |
hexa | do we restart all failed in that case? | 08:58:43 |
hexa | * https://hydra.nixos.org/eval/1689692 lots of failures due to the cached aiohttp error that was restarted | 09:01:59 |
hexa | https://github.com/NixOS/nixpkgs/pull/131928 | 09:09:24 |
Vladimír Čunát | Yes, probably. When there are many of such transitive failures, I do that (after making sure the individual failures succeeded). | 09:26:25 |
hexa | that is the case | 10:25:53 |
Vladimír Čunát | So the main remaining regression is the PerlMagick problem that seems stuck? | 10:35:55 |
hexa | https://shells.darmstadt.ccc.de/~hexa/1690057.html | 10:51:53 |
hexa | mostly aiohttp | 10:51:56 |
hexa | weirdly enough, if you have restarted failed jobs, they failed again even though aiohttp has succeeded | 10:53:40 |
hexa | * weirdly enough, if you have restarted failed jobs, they failed again with a reference to aiohttp, even though aiohttp has succeeded | 10:54:26 |
Vladimír Čunát | No, I only did it now. | 11:00:57 |
hexa | ah ok, was surprised that home-assistant was still queued, I thought it finished earlier | 11:08:53 |
Vladimír Čunát | It failed, so I restarted it individually. | 11:20:43 |
Vladimír Čunát | Sigh, pytorch gets repeatedly scheduled on wendy again: https://github.com/NixOS/nixos-org-configurations/issues/146 | 12:05:24 |
Sandro | wendy hit again 😏 | 13:27:04 |
hexa | wendy 🎉 | 13:46:44 |
FRidh | mass rebuild on master? | 14:17:10 |
FRidh | oh never mind, it's just because it's a different hydra project | 14:19:04 |
sterni | FRidh: looks like it to me? https://hydra.nixos.org/jobset/nixpkgs/trunk | 16:03:06 |
sterni | there's also no cache for current master, so seems like it | 16:03:21 |
sterni | oh hm seems to be in order mostly | 16:07:30 |
sterni | I screwed up with haskell-updates though since I missed the staging-next merge today | 16:10:50 |
sterni | so that's 20000 builds on master, maybe revert time? | 16:11:57 |
| 30 Jul 2021 |
FRidh | In reply to @sternenseemann:systemli.org I screwed up with haskell-updates though since I missed the staging-next merge today haskell-updates were always merged directly into master. While in principle all larger rebuilds go via staging I can get there are reasons to send it to master though. | 06:25:19 |
sterni | In reply to @FRidh:matrix.org haskell-updates were always merged directly into master. While in principle all larger rebuilds go via staging I can get there are reasons to send it to master though. we have specifically updated our workflow to minimize the rebuilds by adding all relevant platforms to the haskell-updates jobset and making it a policy to merge master before merging and waiting for any rebuilds, so normally that shouldn't be an issue | 09:21:32 |
sterni | just forgot to check if there was anything significant on master between merging haskell-updates and the last merging in of master yesterday which was the screw-up | 09:21:59 |
sterni | but seems like the rebuilds finished over night, so not too bad | 09:22:20 |