-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Release 2.27 checklist #1005
Comments
Larger projects currently in the last phases:
|
Are we on track with things? Adjoint ODE looks as if it just makes the deadline... should there be any additional hickup it would be worthwhile to finish last cleanups for adjoint ODE (should there be any need). |
I've got a branch for #1011 - if I got a PR in today, would that go in? |
the freeze is on the 17th end of day anywhere.. so it's the 18th... So if the PR can be reviewed by tomorrow then it can be in. |
Its end of day on the 18th, thats how we usually do it. |
Even better |
What's the matter with varmat? When you post the RC can you point people to the design doc of the adjoint ODE thing? This is to make it possible for people to call the new function for which I am writing the doc this week... or do you have other suggestions? Thanks! |
Missing stanc3 implementation, mostly ran out of time.
That was my plan yes! |
if anyone has time and feels qualified to review CmdStan pr #1017, that would be great. |
@serban-nicusor-toptal let me know when you have time to proceed with the release candidate. We only need to wait for this master stanc3 run to finish: https://jenkins.mc-stan.org/blue/organizations/jenkins/stanc3/detail/master/840/pipeline which should be soon. |
Hey @rok-cesnovar I can start today around 5 PM CEST time. |
Great, thanks! If you can handle the first three points above it would be great!
I have the rest of the stuff ready and will check the tarballs/releases once they are ready. |
Hey @rok-cesnovar here you can find the rcs: It's taking a bit more because I am trying to figure out why this jenkins job is failing in the
|
That happened a few times today yeah. Just restarted a few times and it passed then. |
I see, I will restart one more and see what happens. In the meanwhile I'll try to debug locally, maybe they changed something that affects us as we didn't change anything code wise afaik. |
Sadly I'm getting the same error locally |
Weird, not sure what changed. Will take a look in the morning. |
I've found that here we're missing a |
Great. Fingers crossed. If you have time to build the cmdstan tarball today I can test and make an annoucement in the morning. |
Everything seems to be alright now, weird how that typo got into the pipeline and actually worked until now. |
Thanks Nic! The release candidates are ready and all announcements have been posted. If all goes well the release will be next Thursday. |
Both Mac machines that are located at Columbia have gone offline yesterday. These Mac machines have been the most stable for the last few years and both of them going offline in the same day is very strange. Not much tests have run since the freeze so its very very unlikey this would be related to overload or anything like that. We need these machines to build binaries for Mac and if we are unable to bring them online until Thursday, we will move the release to at least Monday (31st May). They will probably require physical intervention so not sure on the timeline to resolve this. We could use the AWS Mac instances temporarily but that would mean that the minimum Mac version for CmdStan would be |
We also need to resolve stan-dev/math#2493 prior to that. But I think that should be resolved prior to Thursday. |
I have access to Columbia, so I could go up there today and try to figure this out. |
Great! @serban-nicusor-toptal what would need to be done with the machine? Just reboot I am guessing? |
Awesome! Thanks !! |
@bgoodri mentioned that the Mac machines are in Andrew's office right? The Linux/Windows are in Ben's office I believe so thats probably not accessible? The Macs are definitely a bigger priority. The machines are named |
that sounds about right. one Mac machine is in my office ( |
will be up there after 1pm EDT |
Due to the issues with the Mac computer and the performance regression we still haven't gotten to the bottom of, I propose moving the release to Monday. We are unlikely to figure the regression today and I dont want to release on a Friday. |
@serban-nicusor-toptal I think we will need to set up that AWS Mac instance for the release. The performance regression was identified and we will need the Mac instance for the bugfix tests as well as the release. |
Hey @rok-cesnovar I can work on it tomorrow hoping to be ready until Monday, but just FYI Mac instances on AWS can't be bought using Spot Requests and also we can't have it on-demand as it's treated as a bare metal so we'll need to run it 24/7 with a 24-hour minimum allocation period. source |
hi @serban-nicusor-toptal, I can only get access to Andrew's office Tues and Thurs. I couldn't get up the this past Thursday, but will go up on Tuesday and will get access, one way or another. |
Ah okay then we'll need to go for aws for sure until then. Thanks! |
Hey @rok-cesnovar the new AWS Mac is up and running, I hope to get all the dependencies right. Please let me know if you see any job failure so I can sort it out, thanks! |
We currently dont use the Mac+gpu combination, that label is not used in our tests anymore. lets first wait for all tests to pass and merge the bugfix PRs. Its a holiday in the US today so no rush on releasing today. |
Do we need this pr for the current release ? Also, is there any other PR that we should wait for ? |
Yes, that is the last one we need to merge for the release. |
Huh okay that's good to know, I see it has some test failures so I'll probably have to wait until that's fixed. Please let me know if there's anything else I can do for now. |
The PR was merged so we just need to wait for the develop tests to pass so it propagates to cmdstan. That should take 4-5 hours so I guess we are probably going to do it tomorrow? To recap:
|
Nice, we can do it today too as I'll most probably work until late or leave it for tomorrow before US wakes up both work just fine for me. Thanks for the recap! |
@serban Nicusor ***@***.***> I am at Columbia now and will
be here until 3:30 pm New York time.
do you want to co-ordinate w/r/t restarting gelman-group-mac?
…On Mon, May 31, 2021 at 12:07 PM Nicusor Serban ***@***.***> wrote:
Nice, we can do it today too as I'll most probably work until late or
leave it for tomorrow before US wakes up both work just fine for me. Thanks
for the recap!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1005 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJWT5HDFCJGXZ6UT3I6DHDTQOX2VANCNFSM44FILQSQ>
.
|
Hey, sure let's go for it I'm available. |
OK, I just rebooted the machine. if you want to do a hangout, send invite
to my email.
…On Tue, Jun 1, 2021 at 12:52 PM Nicusor Serban ***@***.***> wrote:
Hey, sure let's go for it I'm available.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1005 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJWT5D35QNWAPAUVPQE5MTTQUF35ANCNFSM44FILQSQ>
.
|
I'm remotely connected to the machine, will try to see if I can change any setting for it. |
awesome. it seems to be plugged into one of the wall ethernet connections. took a photo and can reach out to CU IT if there's some kind of network issue. |
I did change
To disable most of the sleep/turnoff so let's hope this fixed it. Thanks a lot @mitzimorris ! |
Looks like we lost the mac machine again @mitzimorris. Nothing was running on it so we can rule out overheating also I don't think it was a standby/shutdown either as we changed those. |
OK, I will reach out to CU IT. |
Do we have to sort out the Mac thing? Or can we proceed with different means? |
Hey, I've already spin up a new Mac Instance on AWS that we can use for now. |
Release is done but there's one thing left, to generate new docs and update release notes with the new urls.
Not sure if I've messed something up in a dependency version or if it's a code error. |
tried to build the docs from current develop - failed on my mac. I don't think it's your scripts that are the problem here. |
I have managed to find a solution, one of the tables failed to render (produces latex that doesnt compile). Setting full_width to TRUE here fixes the issue: https://github.com/stan-dev/docs/blob/master/src/stan-users-guide/sparse-ragged.Rmd#L70 |
Nice! Good job for finding out the error. |
Hey PR for docs can be found here stan-dev/docs#371. |
Done! Eveything seems to be in place now. |
Thanks Nic! All of the announcements on various channels have now been posted so I am closing this issue. Thanks to all! Next release is planned for the 27th of September (RC on the 20th). |
Here is the checklist for the next release.
Feature freeze (May 20th):
Release (
May 27thTBD see #1005 (comment)):The text was updated successfully, but these errors were encountered: