I don't have anymore build failures after Thursday in my inbox. Please LMK if anybody is getting flooded with emails.
Thanks, Andy ________________________________ From: Andrew Palumbo <[email protected]> Sent: Tuesday, October 22, 2019 4:09 PM To: Mahout Dev List <[email protected]>; Dmitriy Lyubimov <[email protected]>; Trevor Grant <[email protected]>; Andrew Musselman <[email protected]>; Pat Ferrel <[email protected]>; Isabel Drost <[email protected]> Subject: Re: Build failed in Jenkins: mahout-nightly #2299 Trevor. Yeah- I did. thanks to microsoft. I filed a ticket w INFRA, Gavin McDonald, about it. we must enforce mvn 3.3.9.. . https://issues.apache.org/jira/browse/INFRA-19292 This email is from last week when i was working on this Thursday night/Friday morn. Have People been getting emails since? Also What do you guys think- should we change the email ti Issues@? rather than dev@? There is also a builds@ which I was unaware of.. I (we, some of the PMC) should to subscribe to it, as Gavin Pointed out on the ticket. I'm, going to do some mahout work today. Pretty sure I see the release error. also BTW. when I run. PRs from the refactored Branch (mahout-14.1), It is in the green... Maybe time I write up a formal PR to Merge that branch, I think that we should be able to release soon.. (I'm not sure that there is a reason not to have this on master at this point. Was looking at the assembly last night again, and I have to do a rollback, and test of what i think may be off in the bin.xml, and root pom. We do have staged binary artifacts, currently for the 14.1 release pegged to scala 2.12, spark 2.4.4, java 8 and maven 3.3.9+. We had touched on, in slack, the idea of a realease of these binaries, If I/we can't get this assembly together in a reasonable abount of time @rawkintrevo, @akm, @pferrel, @Dmitriy Lyubimov<mailto:[email protected]> @Isabel Drost<mailto:[email protected]>, @Mahout Dev List<mailto:[email protected]> thoughts? Thanks, Andy ________________________________ From: Trevor Grant <[email protected]> Sent: Thursday, October 17, 2019 7:07 AM To: Mahout Dev List <[email protected]> Subject: Re: Build failed in Jenkins: mahout-nightly #2299 Guessing.... Palumbo turned this back on? Maybe set them to not send messages to dev until we get the Jenkins build working right again. On Thu, Oct 17, 2019 at 5:38 AM Apache Jenkins Server < [email protected]> wrote: > See <https://builds.apache.org/job/mahout-nightly/2299/display/redirect> > > Changes: > > > ------------------------------------------ > Started by user apalumbo > Running as SYSTEM > [EnvInject] - Loading node environment variables. > Building remotely on H31 (ubuntu) in workspace < > https://builds.apache.org/job/mahout-nightly/ws/> > ERROR: A Maven installation needs to be available for this project to be > built.Either your server has no Maven installations defined, or the > requested Maven version does not exist. > Retrying after 10 seconds > ERROR: A Maven installation needs to be available for this project to be > built.Either your server has no Maven installations defined, or the > requested Maven version does not exist. > Retrying after 10 seconds > ERROR: A Maven installation needs to be available for this project to be > built.Either your server has no Maven installations defined, or the > requested Maven version does not exist. >
