Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release 2020.01 rakudo hangs on 6.c-errata advent2011-day07.t #3441

Closed
Altai-man opened this issue Jan 24, 2020 · 5 comments
Closed

Release 2020.01 rakudo hangs on 6.c-errata advent2011-day07.t #3441

Altai-man opened this issue Jan 24, 2020 · 5 comments
Labels
BLOCKER Preventing the next release of rakudo, or just needing attention before the release

Comments

@Altai-man
Copy link
Member

Altai-man commented Jan 24, 2020 •
edited

When doing release from 2020.01-release branch, t/spec/integration/advent2011-day07.t test hangs (left on night, it didn't complete in more than 7 hours, and on a second run it hung too):

The full log of releasable run: https://gist.github.com/Altai-man/16c352ffa637a786c1e848df8255f505

Steps to Reproduce

The long way: VERSION=2020.01 VERSION_MOAR=2020.01.1 BRANCH_ROAST=b425a4b31fb36b91bbac15e5d63b992f6acf5bc1 BRANCH_RAKUDO=release-2020.01 BRANCH_NQP=master sake all using sake and https://github.com/rakudo/rakudo/blob/master/tools/releasable/Sakefile
The short way: not yet found.
@Altai-man Altai-man added the BLOCKER Preventing the next release of rakudo, or just needing attention before the release label Jan 24, 2020
@Altai-man
Copy link
Member Author

So this is a certainly persistent issue as I am getting it 3rd time in a row.
The bad thing is I don't have an idea how to golf down the sakefile command to anything smaller.
@AlexDaniel maybe you have some ideas?

@lizmat
Copy link
Contributor

lizmat commented Jan 24, 2020

I find the number of TODO tests passing suspect? Could this be using the wrong roast checkout?

@Altai-man
Copy link
Member Author

Altai-man commented Jan 24, 2020 •
edited

I am setting 6(7) days old roast commit to match with the fact that release branch is a bit behind:
Raku/roast@b425a4b
A newer one Raku/roast@db3fec5 doesn't pass test on this rakudo branch.

@Altai-man
Copy link
Member Author

Altai-man commented Jan 24, 2020 •
edited

Trying with Raku/roast@a5af083
No luck. Trying with even older roast commit...
No luck at all.

@lizmat
Copy link
Contributor

lizmat commented Jan 26, 2020

I've fixed the test with Raku/roast@9a9ba99c1c , it is no longer hanging for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BLOCKER Preventing the next release of rakudo, or just needing attention before the release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lizmat @Altai-man