Perl 6 language and compiler development | Logs at colabti.org/irclogger/irclogger_log/perl6-dev | For toolchain/installation stuff see #perl6-toolchain | For MoarVM see #moarvm
Set by Zoffix on 27 July 2018.
lizmat Files=1262, Tests=108018, 204 wallclock secs (26.75 usr 7.63 sys + 2856.08 cusr 283.52 csys = 3173.98 CPU) 05:32
bisectable6: dd ((0, 0), (0, 1), (1, 1)).grep(*.any) 05:38
bisectable6 lizmat, Bisecting by output (old=2015.12 new=8a37b93) because on both starting points the exit code is 0
lizmat, bisect log: gist.github.com/9b44f2c0d32d0438cf...6745f85538
lizmat, (2019-01-29) github.com/rakudo/rakudo/commit/c2...ee4b1ee0fb
jmerelo A question: is perl dependency so hard when building Perl 6? 07:58
I see a lot of Extutils::Command there, but I'm not sure there's anything else... 07:59
and it's mainly cp and mkpath...
well, also some tools in build/... I guess it's just convenient. 08:00
hankache any set date for the next release of Rakudo? 08:18
lizmat releasable6: status 08:22
releasable6 lizmat, Next release in ≈8 days and ≈10 hours. 2 blockers. 140 out of 602 commits logged (⚠ 2 warnings)
lizmat, Details: gist.github.com/4774d9e13cfc7b7678...62d1a4b867
hankache thanks 08:24
jmerelo Latest build seems to be failing: travis-ci.org/perl6/doc/jobs/544582852, far as I can tell... 08:40
perl6: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by //tmp/whateverable/rakudo-moar/8a37b9311c2d18d72912a63ef33b84ad86ff2a5c/lib/libmoar.so)
evalable6 (exit code 1) 04===SORRY!04=== Error while compiling /tmp/XyBTKcjTNq
Unsuppo…
jmerelo, Full output: gist.github.com/475e9152778b381a4d...5da3554567
timotimo jmerelo: unless you want to rewrite Configure.pl in sh, the dependency is pretty hard 09:54
lizmat bisectable6: given gather for ^10 { .take } { dd .all; dd .all } 09:57
bisectable6 lizmat, Bisecting by output (old=2015.12 new=8a37b93) because on both starting points the exit code is 1
lizmat, bisect log: gist.github.com/1104e4948975ef3fe4...34dfc85c9f
lizmat, (2016-03-02) github.com/rakudo/rakudo/commit/fd...7e379b5038
lizmat bisectable6: old=2019.03 given gather for ^10 { .take } { dd .all; dd .all } 09:58
bisectable6 lizmat, On both starting points (old=2019.03 new=8a37b93) the exit code is 1 and the output is identical as well
lizmat, gist.github.com/bf0f017e2ea16bd8fe...a33d944426
lizmat :-( 10:13
bisectable6: given Seq.new((1,2,3).iterator) { dd .elems; dd .all; dd .all 10:27
bisectable6 lizmat, On both starting points (old=2015.12 new=8a37b93) the exit code is 1 and the output is identical as well 10:28
lizmat, gist.github.com/63820917237b43c333...69db5e9a23
lizmat bisectable6: given Seq.new((1,2,3).iterator) { dd .elems; dd .all; dd .all }
bisectable6 lizmat, Bisecting by output (old=2015.12 new=8a37b93) because on both starting points the exit code is 1
lizmat, bisect log: gist.github.com/25df822e118f71438c...0517f313cd
lizmat, (2016-01-22) github.com/rakudo/rakudo/commit/5a...de4d106973
lizmat bisectable6: old=2019.03 given Seq.new((1,2,3).iterator) { dd .elems; dd .all; dd .all } 10:29
bisectable6 lizmat, Bisecting by exit code (old=2019.03 new=8a37b93). Old exit code: 0
lizmat, bisect log: gist.github.com/b6c66fcf97b8798af3...928c3a28fc
lizmat, (2019-06-10) github.com/rakudo/rakudo/commit/91...11fc017758
lizmat yup, that's the one :-)
bisectable6: old=2019.03 given Seq.new((1,2,3).iterator) { dd .list; dd .all; dd .all } 10:39
bisectable6 lizmat, On both starting points (old=2019.03 new=8a37b93) the exit code is 1 and the output is identical as well
lizmat, Output on both points: «(1, 2, 3)␤The iterator of this Seq is already in use/consumed by another Seq␤(you might solve this by adding .cache on usages of the Seq, or␤by assigning the Seq into an array)␤ in block <unit> at /tmp/LF5Glv3vqN line 1␤␤»
lizmat that feels wrong to me: if we expect .elems to cache, why doesn't .list as well ??
Geth rakudo: 7af0fb1c4c | (Elizabeth Mattijsen)++ | src/core/Sequence.pm6
Make sure Sequence.list also caches

We expect .elems to cache, but .list was not cached.		 10:47
lizmat spectests clean
lizmat now on to how to preserver the github.com/rakudo/rakudo/commit/91...11fc017758 optimization 10:47
Geth roast: 63116a9701 | (Elizabeth Mattijsen)++ | S32-list/skip.t
Don't use a CachedIterator in the skip tests
 11:45
Geth rakudo: 94ba19f7e5 | (Elizabeth Mattijsen)++ | 3 files
Introducing/Using the CachedIterator role

This is CachedIterator role is a refinement of the PredictiveIterator role. The difference is that a CachedIterator role is supposed to supply a "cache" method that will be called to set the cache of the Seq as soon as the iterator is being used.
... (13 more lines)		 12:04
lizmat .tell AlexDaniel I think I've documented all of my commits in the ChangeLog wiki 13:13
yoleaux lizmat: I'll pass your message to AlexDaniel.
lizmat github.com/rakudo/rakudo/wiki/ChangeLog-Draft 13:14
vrurg patrickb ^^ perhaps you could also have a look ?
patrickb lizmat: I'll probably find some time for this in the evening, the largest bunch of my commits are logged already though. 13:16
lizmat: Do you know when the release is planned? There are some PRs that should definitely go in before... 13:17
AlexDaniel` lizmat++
vrurg lizmat: thanks! 13:37
lizmat releasable6: status 14:03
releasable6 lizmat, Next release in ≈8 days and ≈4 hours. 2 blockers. 218 out of 604 commits logged (⚠ 4 warnings)
lizmat, Details: gist.github.com/3227f27775d8cc6bb5...909bcc6253
lizmat patrickb ^^^
lizmat releasable6: status 14:07
releasable6 lizmat, Next release in ≈8 days and ≈4 hours. 2 blockers. 218 out of 604 commits logged (⚠ 4 warnings)
lizmat, Details: gist.github.com/2e4bc04a31fbf8fa53...85dc991c7c
lizmat hmmm I though I'd fixed all the warnings :-(
vrurg lizmat: it's my two additions. 14:23
releasable6: status 14:29
releasable6 vrurg, Next release in ≈8 days and ≈4 hours. 2 blockers. 220 out of 604 commits logged (⚠ 1 warnings)
vrurg, Details: gist.github.com/9e331460c911cc1947...99271c86ad
MasterDuke lizmat: do you have a repro for that busted profile you created? i want to do some debugging, but haven't been able to repro it independantly 16:30
Geth rakudo: a4d38539f8 | (Elizabeth Mattijsen)++ | t/08-performance/03-corekeys.t
Oops, forgot to add CachedIterator to known core objects list

Should make Travis happy again.		 17:49
rakudo: 95a7866c07 | (Elizabeth Mattijsen)++ | src/Perl6/Metamodel/BOOTSTRAP.nqp
Fix copy pasto, spotted by Michael Schroeder
 17:59
travis-ci Rakudo build passed. Elizabeth Mattijsen 'Oops, forgot to add CachedIterator to known core objects list 19:10
travis-ci.org/rakudo/rakudo/builds/544858809 github.com/rakudo/rakudo/compare/9...d38539f821
lizmat whee ! :-) 19:10
Geth rakudo: f8ced4987a | (Patrick Böker)++ | 3 files
Remove harmful stale files

Files in NQP_HOME/lib/Perl6 left there of previous installs will be loaded before files in PERL6_HOME/lib/Perl6 and thus have precedence. Because of that these files break the install if left there. We thus check for their existence and remove them during install if necessary. The user is notified of this during Configure.		 20:38
rakudo: b3cceac9f7 | (Patrick Böker)++ (committed using GitHub Web editor) | 3 files
Merge pull request #2956 from patzim/rm-stale-nqp-files

Remove harmful stale files during build
Geth rakudo: patzim++ created pull request #2978:
Fix build runner comp repos		 21:32
rakudo/master: 4 commits pushed by (Patrick Böker)++ 22:11
Geth rakudo: 40cc12ac14 | (Patrick Böker)++ | 6 files
Use a static exec path with non-reloc builds

In the non-relocatable case it's not necessary to determine the executable path at runtime. We can just as well compile it in. Doing so solves the problem of OpenBSD where it's currently not technically possible to determine the path of an executable from within.
Fixes #2904
Also some cleanup of the C runner.		 23:33
synopsebot RAKUDO#2904 [closed]: github.com/rakudo/rakudo/issues/2904 Rakudo no longer builds properly on OpenBSD
rakudo: 370c866cbe | (Patrick Böker)++ (committed using GitHub Web editor) | 6 files
Merge pull request #2963 from patzim/static-exec-path

Use a static exec path with non-reloc builds

Powered by Cro and the Raku® Programming Language.

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

Thank you!