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.

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

Partial Build [Possibly due to parallelization] #664

Closed
zoffixznet opened this issue Jul 4, 2016 · 7 comments
Closed

Partial Build [Possibly due to parallelization] #664

zoffixznet opened this issue Jul 4, 2016 · 7 comments

Comments

@zoffixznet
Copy link
Contributor

zoffixznet commented Jul 4, 2016

The screenshot below shows a partial build of the Language docs, even though the build log shows them built. Visiting the missing pages directly gave a 404.

This issue may or may not have been caused by 8d83f42 that added parallelzation. We undid it in d41f52e and the docs built fine.

Some more testing needs to be done with the parallelization feature turned on.

lang

@MasterDuke17
Copy link
Contributor

I would not have --parallel enabled for whatever auto-builds the docs for docs.perl6.org. I believe my code is correct, but Rakudo just doesn't implement it well enough (yet). On my machine it's actually still faster to just run with --parallel a couple times until it completes, versus running it serially, but unless the script loops until the exit status is ok I'd leave it on the old behavior for the website.

@coke coke changed the title Partial Build [Possibly due to parallelazation] Partial Build [Possibly due to parallelization] Dec 13, 2016
@coke
Copy link
Collaborator

coke commented Dec 22, 2016

The parallel code causes SEGVs and other oddities. A barebones version of htmlify that exhibits the issue is on the coke/bughunt branch

@coke
Copy link
Collaborator

coke commented Feb 12, 2017

jnthn++ fixed the issues I had golfed down on the coke/bughunt branch - need to investigate what issues are left with --parallel now.

@jnthn
Copy link
Contributor

jnthn commented Feb 12, 2017

The remaining one I know about is the code-gen for NEXT phasers in while/until/loop has issues, which show up under recursion of concurrency. There may be further problems in htmlify.p6 and its related modules beyond those I already fixed, however. Guess we'll see after the NEXT bug is addressed.

@AlexDaniel
Copy link
Member

@jnthn ticket id?

@JJ
Copy link
Contributor

JJ commented Mar 24, 2018

What's the current status of this? If I got this correctly, parallelization is turned off but we would like to turn it on for, among other things, speed up test, right?

@JJ
Copy link
Contributor

JJ commented Apr 8, 2018

It looks like this issue has been addressed and is no longer needed. I'll close it, please clarify and reopen it if necessary.

@JJ JJ closed this as completed Apr 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants