Geth roast/absolute-lib-paths: cf1cedd429 | (Nick Logan)++ | 254 files
Allow tests to be run outside of rakudo dir

Absolutify lib paths and file paths using $?FILE.IO.parent(...), since a test can know the file layout of its own repo but not the cwd the user is invoking a test from.
This allows you to install perl6, clone the roast anywhere you ... (11 more lines)		 05:09
ugexe I will merge that after the release
Geth roast: ugexe++ created pull request #356:
Allow tests to be run outside of rakudo dir		 05:14
synopsebot SPEC#356 [open]: github.com/perl6/roast/pull/356 Allow tests to be run outside of rakudo dir
[Tux] Rakudo version 2017.10-216-g8ccb60e39 - MoarVM version 2017.10-86-g89fae17a6
csv-ip5xs1.110 - 1.116
csv-ip5xs-2012.780 - 12.936
csv-parser12.190 - 12.201
csv-test-xs-200.418 - 0.436
test11.897 - 12.651
test-t3.245 - 3.324
test-t --race1.302 - 1.344
test-t-2058.748 - 58.853
test-t-20 --race20.041 - 20.846
 07:27
samcv MoarVM 2017.11 has now been released! 08:54
ufobat m: require IO::XXX 09:05
camelia IO::XXX is a builtin type, not an external module
in block <unit> at <tmp> line 1
ufobat is it because this code creates the, i dont know what it is called, namespace..., and doesn't clean it up if the require actually fails
github.com/rakudo/rakudo/blob/mast....nqp#L2123
El_Che releasable6: status 10:08
releasable6 El_Che, Next release will happen when it's ready. No blockers. 213 out of 216 commits logged
El_Che, Details: gist.github.com/01c3f71308e5567c89...07158bece3
stmuk www.einval.com/~steve/DebianT/grol...n-open.gif 13:03
"we only release when it's ready"
El_Che stmuk: in the old days, this pic was also popular during pre- reelases of Debian and Debian X stack: i.imgur.com/ZbhW1pd.jpg 13:21
stmuk :D
AlexDaniel +1 to all these pics :) 14:22
AlexDaniel just woke up, will get to it shortly
samcv++
huggable: no release? :is: www.einval.com/~steve/DebianT/grol...n-open.gif 14:40
huggable AlexDaniel, Added no release? as www.einval.com/~steve/DebianT/grol...n-open.gif
Geth rakudo: 34421ab6f7 | (Aleks-Daniel Jakimenko-Aleksejev)++ | 2 files
Generate announcement, claim next release
 15:21
AlexDaniel hm, oops 15:22
Geth rakudo: b860dea456 | (Aleks-Daniel Jakimenko-Aleksejev)++ | 2 files
Unmarkdownify $*PID
 15:24
nqp: 39325f54e2 | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/build/MOAR_REVISION
[release] Bump MoarVM revision to 2017.11
 16:25
nqp: version bump brought these changes: github.com/MoarVM/MoarVM/compare/2......2017.11
e664aa53b4 | (Aleks-Daniel Jakimenko-Aleksejev)++ | VERSION
rakudo: 0e4a1f96d8 | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/build/NQP_REVISION
[release] Bump NQP revision to 2017.11
rakudo: version bump brought these changes: github.com/perl6/nqp/compare/2017.......2017.11
e0394b6acc | (Aleks-Daniel Jakimenko-Aleksejev)++ | VERSION
AlexDaniel releasable6: status 16:27
releasable6 AlexDaniel, Next release in 25 days and ≈2 hours. No blockers. 213 out of 218 commits logged
AlexDaniel, Details: gist.github.com/5efe9ddf9eb6e16e9b...6043eb1f8b
AlexDaniel that's… not exactly the right answer :) 16:28
ah, it is delayed by a minute or two
Geth rakudo: 47ebc4ab24 | (Aleks-Daniel Jakimenko-Aleksejev)++ | docs/ChangeLog
Point to rakudo wiki for the next changelog

The contents of the wiki page will be move into the changelog file before the release.		 16:41
El_Che \o/ let's kick travis to see if it build ok on platforms I support 16:45
travis-ci.org/nxadm/rakudo-pkg/builds/305370024 16:49
running
AlexDaniel I've wikified the changelog for MoarVM also. Hoping that this will help with some things (e.g. people correcting spelling mistakes instead of just pointing at them, no more unintentional markdown formatting, etc.) 16:50
El_Che thx AlexDaniel, looking fwd to the new release 16:51
ah the tars have not been pushed yet
I was a little too enthousiastic :) 16:52
AlexDaniel hmm… what? 16:55
I'm pretty sure they were
El_Che moarvm.org/releases/MoarVM-2017.11.tar.gz 16:56
that's where my build process dies
not there
AlexDaniel ouch
samcv: ↑ ?
El_Che (or the naming changed)
AlexDaniel I remember there was a delay for moarvm tars
but moarvm release was many hours ago so hmm
El_Che checke, not there even with alternative spellings :)
jnthn There was no commit here: github.com/MoarVM/moarvm.org/commits/master 16:57
Maybe that step was somehow forgotten, or a forgotten push, or some such?
[Coke] t/spec/S17-supply/watch-path.t fails on OSX here; known? 17:48
gist.github.com/coke/65d995a1ad321...ed1bde8c52 17:49
ugexe yeah 18:03
its the only one that should fail on osx
well, not should, but can be ignored
AlexDaniel I think most tests that are failing on os x are actually fudged 18:14
ugexe can the fudger be done in code instead now, instead of preprocessing? 18:17
El_Che if it's a know failure, wouldn't it make sense to skip it there (torture the implemeters thing)?
(not now, but in the future)
[Coke] fudge, no, manually todo, sure. There are some that are todo'd for os x, IIRC
ugexe [Coke]: why cant the fudge step happen at runtime? i thought it just inserts todos /skips 18:19
[Coke] it's rewriting the source code. you could do a normal todo, but that ain't fudging. 18:20
so, yes, it can be done. Just not with the fudger as is.
I don't actually see an os x skips right now.
samcv AlexDaniel: where do you need me to put the tar file 18:21
AlexDaniel samcv: just like it was done for 2017.10 here: github.com/MoarVM/moarvm.org/commits/master
samcv ok
ugexe ah right. i imagined the fudger itself just adding the codegen for selecting OS, you'd run it once, and then keep the modified files as the final source
samcv ok doing it right now 18:22
done 18:23
AlexDaniel samcv: thank you!
El_Che: OK, try again? :)
[Coke] heads out.
El_Che AlexDaniel: running, same build: travis-ci.org/nxadm/rakudo-pkg/builds/305370024 18:24
Zoffix How come you can `but` a type object but not `does` a type object? 18:28
El_Che AlexDaniel: first build just finished (apine in 9m18s). It does 5 builds at the time :) 18:35
AlexDaniel :)
El_Che by the time I wrote that, 4 other finished 18:36
:)
AlexDaniel: so this is final? If all the build pass, can tag my repo so the pkgs are uploaded to github?
AlexDaniel El_Che: well, it's already tagged and pushed, so there's no coming back really 18:37
El_Che great
AlexDaniel unless we want to make a point release, and that'd need some good reason…
El_Che let's hope not :) 18:38
Zoffix ZOFVM: Files=1282, Tests=152871, 150 wallclock secs (20.61 usr 3.18 sys + 3204.95 cusr 159.94 csys = 3388.68 CPU) 18:51
Geth rakudo: 575d31e251 | (Zoffix Znet)++ | src/core/operators.pm
Consistify &[but] and &[does] with non-roles

Implement the same auto-role-making shortcut for `does` that is available for `but`.		 18:52
roast: 344d6d50a0 | (Zoffix Znet)++ | S03-operators/misc.t
Test `does` can be used with non-composable :D RHS

Rakudo impl: github.com/rakudo/rakudo/commit/575d31e251
  (Couldn't find where the `infix:<does>` is tested so stuck new
tests here)		 18:55
El_Che AlexDaniel: i386 fails : travis-ci.org/nxadm/rakudo-pkg/job...0056#L2491 18:56
AlexDaniel yay…
:)
dogbert17: iirc you had 32-bit system by hand? 18:57
El_Che mmm
17.04 i386... passed
AlexDaniel dogbert17: any chance to bisect rakudo-s t/04-nativecall/12-sizeof.t ?
El_Che waiting on ubuntu 17.10 i386 18:58
passed
I'll relaunch 16.04?
AlexDaniel ticket to track the issue: github.com/rakudo/rakudo/issues/1262 19:00
El_Che: I see no point really
El_Che: what'd be useful is to know which test fails exactly 19:01
.oO( “rakudo-s”? Why did I type it that way… )
 19:08
El_Che AlexDaniel: it builds now 19:10
AlexDaniel huh? Was it a flap then?
El_Che seems an intermittent bug
AlexDaniel wheeeeeeewwww… 19:11
let's see if I can make it fail here then
dogbert17: ok, what about: while perl6 t/04-nativecall/12-sizeof.t; do :; done 19:19
Got a segfault here 19:23
dogbert17 oops, will check :) 19:28
AlexDaniel so nvm everyone
well, you can check :)
but it's not specific to the architecture it seems
dogbert17: you'll have to run it in a loop to reproduce 19:30
or maybe you just need ASAN
dogbert17 I am, no failures yet
AlexDaniel dogbert17: yeah, took about 10 minutes here 19:31
dogbert17 are you golfing something here 19:38
AlexDaniel not yet 19:43
El_Che AlexDaniel: I hold the packages for now? 19:58
I can replay the travis builds as many times as you want
AlexDaniel El_Che: no, we have a bunch of flappers, that's “OK” 20:01
“ok” as in SNAFU :) 20:02
El_Che ok as "pkgs are releasable if they pass the tests" or ok as "don't release, don't replay travis, we know we have a bunch of flappers" 20:05
?
AlexDaniel stuff is releasable if tests pass at least sometimes :) 20:06
El_Che ok, will release then :)
AlexDaniel fwiw releasable6 itself has to run the stresstest several times before it actually passes properly
travis-ci Rakudo build failed. Aleks-Daniel Jakimenko-Aleksejev 'Unmarkdownify $*PID'
travis-ci.org/rakudo/rakudo/builds/305330839 github.com/rakudo/rakudo/compare/3...60dea456ac
buggable [travis build above] ✓ All failures are due to: GitHub connectivity (1 failure).
El_Che reproducibility is overrated 8) 20:08
dogbert17 AlexDaniel: no crash yet 20:24
El_Che I just had had a new fail on ubuntu 17.04 i386. Restarting that build 20:32
dogbert17: maybe the fails happens faster with restricted resources?
ubuntu 17.10 i386 failed as well 20:33
dogbert17 El:Che, could be, any suggestions 20:35
El_Che how are you building rakudo? native? on a vm? docker? 20:36
dogbert17 on a vm
El_Che give it less resources? 20:38
all right they all passed now 20:42
travis-ci Rakudo build failed. Aleks-Daniel Jakimenko-Aleksejev '[release] Bump VERSION to 2017.11' 22:17
travis-ci.org/rakudo/rakudo/builds/305360480 github.com/rakudo/rakudo/compare/b...394b6acc44
buggable [travis build above] ☠ All failures are due to: failed make test (1 failure). Across all jobs, only t/02-rakudo/repl.t test file failed.
lizmat . 22:49
AlexDaniel m: use Test; isnt 5, 6 23:21
camelia ok 1 -
AlexDaniel “isnt”? rly?
m: use Test; isn't 5, 6
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
isn't used at line 1. Did you mean 'isnt'?

Powered by Cro and the Raku® Programming Language.

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

Thank you!