| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This reverts commit 673f49a. This change is breaking gulp on v14.x. Reverting so we can reland in a way that doesn't break stuff Refs: nodejs#33660 Refs: nodejs#34371
|
Can we please fast track so we can get this in 14.6.0 |
Sorry, something went wrong.
Sorry, something went wrong.
|
… this is very surprising – it’s purely a formatting change. If this breaks gulp, then gulp is already broken, but it seems almost impossible that this change actually affects behavior in anyway. If you are certain that this is breaking, maybe just leave the commit out of the v14.6.0 proposal? |
Sorry, something went wrong.
|
@addaleax this change went out in v14.5.0 and broke the gulp test suite. Reverting this change in v14.6.0 fixes it. I'll admit that I am also surprised that this change is having that effect. Although honestly I just ran the test suite again and this revert was not fixing it... TBH I'm very confused right now and will dig in a bit more |
Sorry, something went wrong.
|
@MylesBorins Maybe some other change made the test suite flaky? I think that seems like a more likely cause… |
Sorry, something went wrong.
|
there is definitely a change on 14.5.0 that broke gulp, perhaps this was a false positive from bisect Running bisect again and a few more manual tests... since when I checked again this revert didn't actually fix the problem I was seeing |
Sorry, something went wrong.
|
Closing as manual testing again on local machine shows gulp still failing |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This reverts commit 673f49a.
This change is breaking gulp on v14.x. Reverting so we can reland in a
way that doesn't break stuff
Refs: #33660
Refs: #34371