Hey Folks, Good news: this is resolved. I did some additional testing on xenial boxes we previously had successful builds. The culprit was eslint v6+. So, I’ve regressed gulp-eslint to the previous major version (v.5), to pull back eslint (dependency) to a previous version (v5.16). Now builds are passing on node.js 12.2.0.
I’ll send this report to eslint—didn’t see any other error reports and there isn’t any guidance on testing against different OS. Also, added some additional lines to our build proc in Jenkins to report Node/NPM and Ubuntu version. This should be helpful down the line—at least our last successful build was on a 16.04.6 Ubuntu node, which is getting a little stale. I’ll write an INFRA ticket about maybe updating a few of these build servers to upgrade their Ubuntu versions. Thanks again for helping with testing and running this madness to ground. Josh > On Jul 27, 2019, at 3:55 PM, Joshua Poore <poor...@me.com.INVALID> wrote: > > Thanks, Michael. I assume nothing wrt our Jenkins server :) > > I’ll work more on it tonight and see where we get. > > Joshua Poore > > >> On Jul 27, 2019, at 3:17 PM, Michael Schreiber >> <michael.a.schrei...@gmail.com> wrote: >> >> I can test when I return from travel Sunday evening, assuming it hasn’t >> been resolved. >> >> Michael >> >> On Sat, Jul 27, 2019 at 10:39 AM Joshua Poore <poor...@me.com.invalid> >> wrote: >> >>> Hi Dave, thanks! >>> >>> I went into Jenkins configs and flipped off “build periodically” on the >>> bionic node—as per INFRA guidance, we’re only allowed to use the ‘Ubuntu' >>> tag (and probably ‘xenial'). This will keep it from running unless we push, >>> merge, or manually trigger, and hopefully not get the Hadoop folks angry at >>> us. >>> >>> If you look at build #73—was successful build after final merge of v2.0.0 >>> RC into master. This was a successful build on xenial using node v12.2.0 >>> linux x64, on machine H22. I’ll pin to this machine and see if the 12.7.0 >>> build doesn’t work on it. If so, then we have some issue with servers and >>> labels in Jenkins, if not, it could be a node or package issue, in which >>> case I’ll regress gulp-eslint back to a previous version and retest, and >>> we’ll keep running CI on node 12.2.0 until we see that node has worked out >>> any kinks with their new version. We know it builds on 12.7.0 on darwin and >>> linux, so I don’t think we need to walk back our package.json. >>> >>> Thanks for the assist folks! #community #boosh! >>> >>> Josh >>> >>>> On Jul 27, 2019, at 6:27 AM, Dave Meikle <dmei...@apache.org> wrote: >>>> >>>> Yes, it looks like it works on Bionic but not Xenial. I pinned the CI >>> build >>>> to confirm. >>>> >>>> I need to go offline just now but will try to see the difference. It >>> looks >>>> like a node version from the error but can see it dynamically downloads. >>>> >>>> Cheers, >>>> Dave >>>> >>>>> On Sat, 27 Jul 2019 at 09:47, Dave Meikle <dmei...@apache.org> wrote: >>>>> >>>>> >>>>> >>>>>> On Fri, 26 Jul 2019 at 21:01, Joshua Poore <poor...@apache.org> wrote: >>>>>> >>>>>> Going insane. Can someone please try and build the RC branch ( >>>>>> https://github.com/apache/incubator-flagon-useralejs < >>>>>> https://github.com/apache/incubator-flagon-useralejs>) on a Linux X64 >>>>>> machine and see if builds/tests run on npm 12.7 (I’ll take 12.2 too). >>> This >>>>>> would be super helpful in debugging this issue. Should only take a >>> minute >>>>>> or two to run install, built, and test. >>>>>> >>>>>> >>>>> Builds and tests fine here. Ubuntu 19.04 x64 with: >>>>> >>>>> - Node v12.6.0, NPM 6.4.1 >>>>> - Node v12.7.0, NPM 6.10.0 >>>>> >>>>> Cheers, >>>>> Dave >>>>> >>> >>> >
