timo oh whew, i have finally apparently reproduced a hang in moar on arm64 01:44
02:45 librasteve_ left
Geth nqp: usev6++ created pull request #833:
[JVM] Return exit code for run failure		 07:51
rakudo/azure_improvements_squashed: 30c5edc5f9 | (Patrick Böker)++ | azure-pipelines.yml
test mac cpanm path
 09:32
09:33 sena_kun joined
Geth rakudo/azure_improvements_squashed: 26750801df | (Patrick Böker)++ | azure-pipelines.yml
tabs
 09:34
rakudo/azure_improvements_squashed: 3b0f35df92 | (Patrick Böker)++ | azure-pipelines.yml
right perl version
 09:44
09:50 sena_kun left
Geth rakudo/azure_improvements_squashed: 2208db214f | (Patrick Böker)++ | t/04-nativecall/CompileTestLib.rakumod
Fix nativecall tests on Windows/cl/enabled debugging
 09:59
rakudo/azure_improvements_squashed: 81f2dbe45a | (Patrick Böker)++ | src/vm/moar/runner/main.c
Deal with long paths in moar runner
rakudo/azure_improvements_squashed: f982346771 | (Timo Paulssen)++ (committed by Patrick Böker) | 2 files
Reimagine Azure CI

  - Prettier output (using the JUnit test result formatter)
  - Restructure making better use of parameters
  - Disable OOMing Win_JMV
  - Speed up CI on Windows by working around the compiler search
  - More granular output using `echo` commands
  - add a nodelay & blocking spec test run
  - persist build artifacts
  - Speed up testing by running tests in parallel
  - Bump the OS versions to latest as of now
11:38 librasteve_ joined
Geth rakudo/azure_improvements_squashed: bdfc5d6807 | (Patrick Böker)++ | azure-pipelines.yml
Install prove on windows
 12:29
rakudo/azure_improvements_squashed: d2f21c04f2 | (Patrick Böker)++ | azure-pipelines.yml
where is prove?
 12:56
nqp/main: 649a0f378e | (Christian Bartolomäus)++ (committed using GitHub Web editor) | src/vm/jvm/runtime/org/raku/nqp/io/AsyncProcessHandle.java
[JVM] Return exit code for run failure

This adjusts the behaviour of the JVM backend to the change from
  github.com/rakudo/rakudo/commit/81c7064ba7. The error callback
now accepts a second argument with an exit code.
At least for IOExceptions the original error code from the JVM can be seen in the error message. I don't see a real benefit in extracting that error code and passing it on. Instead, we'll just set the exit code to -1 (which is also expected by at least one spectest:
  github.com/Raku/roast/blob/3032bcf...em.t#L47).		 15:26
rakudo/main: 530e20597d | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
[JVM] Bump NQP to get run failure exit code fixes
 15:32
16:02 [Tux] left 16:06 [Tux] joined
[Tux] Rakudo v2024.10-61-g530e20597 (v6.d) on MoarVM 2024.10-38-g8dd8a8c08
csv-ip5xs0.262 - 0.266
csv-ip5xs-201.123 - 1.148
csv-parser1.460 - 1.532
csv-test-xs-200.144 - 0.144
test1.868 - 1.906
test-t0.399 - 0.399
test-t --race0.263 - 0.267
test-t-204.777 - 4.819
test-t-20 --race1.227 - 1.231
 16:26
tux.nl/Talks/CSV6/speed4-20.html / tux.nl/Talks/CSV6/speed4.html tux.nl/Talks/CSV6/speed.log
timo d'oh, got a segfault but core size limit was set to 0 so i don't have a core dump ;_; 17:01
19:03 Xliff left
ugexe one-million conditionals program has been precompiling for 6 hours now 19:37
Geth roast: 15eacbeebc | (Christian Bartolomäus)++ | S29-os/system.t
[JVM] Unfudge tests for run failures

Fixed with github.com/Raku/nqp/commit/649a0f378e (and a corresponding bump of NQP).		 19:38
bartolin bisectable6: use MONKEY; augment class Any { method foo() { "foo" } }; say 1.foo ## github.com/rakudo/rakudo/issues/3209 19:51
bisectable6 bartolin, Will bisect the whole range automagically because no endpoints were provided, hang tight
bartolin, Output on all releases: gist.github.com/581147496bff0c8840...1fe0e95602 19:52
bartolin, More than 3 changes to bisect, please try a narrower range like old=2024.10 new=HEAD
bartolin bisectable6: old=2021.09 new=2021.10 use MONKEY; augment class Any { method foo() { "foo" } }; say 1.foo 19:53
bisectable6 bartolin, Bisecting by exit code (old=2021.09 new=2021.10). Old exit code: 1 19:54
bartolin, bisect log: gist.github.com/65c7016d138352671a...c7f0486f29 19:57
bartolin, There are 224 candidates for the first “new” revision. See the log for more details
20:09 MasterDuke joined
MasterDuke patrickb++ for the windows work 20:10
bartolin could maybe someone double check if 6.c/MISC/bug-coverage-stress.t passes with a recent Rakudo? (it fails test 14 for me)
and yes, patrickb++ 20:11
MasterDuke `Failed test:  14`
bisectable6: ((1..10)[2.polymod($_ xx 1000).map($_ ** *) »%» *] with 1) 20:12
bisectable6 MasterDuke, Will bisect the whole range automagically because no endpoints were provided, hang tight
MasterDuke, Output on all releases: gist.github.com/7f2c2a9cbcdf75b743...0d80012fa7 20:13
MasterDuke, More than 3 changes to bisect, please try a narrower range like old=2024.10 new=HEAD
MasterDuke bisectable6: old=2024.10 ((1..10)[2.polymod($_ xx 1000).map($_ ** *) »%» *] with 1) 20:14
bisectable6 MasterDuke, Problem with 530e205 commit: Broken archive
bartolin ah, maybe you should add a "dd" in front?
MasterDuke bisectable6: old=2024.10 new=461b81f79459674ca049dc618d5fa412127e2583 ((1..10)[2.polymod($_ xx 1000).map($_ ** *) »%» *] with 1) 20:15
bisectable6 MasterDuke, On both starting points (old=2024.10 new=461b81f) the exit code is 0 and the output is identical as well
MasterDuke, Output on both points: «»
MasterDuke bisectable6: old=2024.10 new=461b81f79459674ca049dc618d5fa412127e2583 dd ((1..10)[2.polymod($_ xx 1000).map($_ ** *) »%» *] with 1)
bisectable6 MasterDuke, Bisecting by output (old=2024.10 new=461b81f) because on both starting points the exit code is 0
MasterDuke, bisect log: gist.github.com/0784dbbe5e899b33e0...449973d157
MasterDuke, (2024-10-25) github.com/rakudo/rakudo/commit/c8...636a8364b0
MasterDuke lizmat: ^^^ 20:16
Geth ¦ rakudo: lizmat self-assigned Iteration does not stop if divisor is 1 github.com/rakudo/rakudo/issues/4523 20:21
lizmat MasterDuke: noted
MasterDuke lizmat++ 20:22
bartolin++ also
20:43 notna joined 20:45 notna left 20:46 notna joined, notna left
Geth rakudo/azure_improvements_squashed: 752b6e6e85 | (Patrick Böker)++ | azure-pipelines.yml
more debug prints
 21:36
rakudo/azure_improvements_squashed: df21068c18 | (Patrick Böker)++ | azure-pipelines.yml
debug
 21:38
rakudo/azure_improvements_squashed: 8c4ebc0b6b | (Patrick Böker)++ | azure-pipelines.yml
debug
 22:02
22:06 sena_kun joined
Geth rakudo/azure_improvements_squashed: cefef07e00 | (Patrick Böker)++ | azure-pipelines.yml
more debug
 22:30
22:36 sena_kun left
ugexe patrickb: what are you trying to do? get prove installed? 22:57
patrickb get prove actually run tests instead of silently doing nothing 22:58
ugexe try prove.bat
github.com/ugexe/zef/blob/d8b73d20...akumod#L96 22:59
i used prove.bat in zef when it had a prove plugin for some reason
patrickb the latest run did run stuff. Sadly the prints are not in the right order, so I don't know for sure which versions worked. I suspect it's the "--ext .t" that poses an issue 23:02
ugexe ah
when you say prints are not in the right order, you're not talking about something that would occur from tests running in parallel though right? 23:03
Geth rakudo/azure_improvements_squashed: 7c0ad2e2e6 | (Patrick Böker)++ | azure-pipelines.yml
next try
 23:05
ugexe its outputting JUnit to the raw log screen which seems less than ideal
patrickb no I did multiple different prove calls with echos before to identify them. But it seems the echos and succeeding prove runs switch order 23:06
but I think I'm almost there. 23:07
either the --ext is the issue or the backward slashes
ugexe on windows i do notice a lot of times in zef where the outputs of stdout and stderr are shown in an unexpected order 23:08
patrickb Yeah, I believe that's what was happening here
timo maybe split it into multiple jobs or stages or steps or what it was called 23:17
then it won't be able to mix things up 23:18
Geth rakudo/azure_improvements_squashed: b90fb35e7e | (Patrick Böker)++ | azure-pipelines.yml
one more
 23:32
patrickb Last try for tonight. I'm off to bed. o/
\q
23:51 japhb left 23:53 japhb joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!