dronegen: Enable verbose logs for electron tooling on macOS #15836
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is in effort to fix flaky builds described in #15835.
zmb3
reviewed
Aug 26, 2022
tigrato
approved these changes
Aug 26, 2022
zmb3
approved these changes
Aug 26, 2022
|
@ravicious See the table below for backport results.
|
ravicious
added a commit
that referenced
this pull request
Aug 31, 2022
ravicious
added a commit
that referenced
this pull request
Sep 2, 2022
ravicious
added a commit
that referenced
this pull request
Nov 30, 2022
It was added in effort to debug flaky Connect builds (#15836). However, we discovered that the v11.1.0 macOS version of Connect stopped working. This was likely due to upgrade of electron-builder which recently updated its process of building native deps (electron-userland/electron-builder#7196). In the Node.js ecosystem, the DEBUG env var is typically used to control which packages emit debug messages [1]. However, after the update of electron-builder, the env var also changed the behavior of one of the packages responsible for building the apps. This was confirmed by inspecting file tree between different app bundles and running the build locally with DEBUG set to electron-*. [1] https://www.npmjs.com/package/debug
ravicious
added a commit
that referenced
this pull request
Nov 30, 2022
It was added in effort to debug flaky Connect builds (#15836). However, we discovered that the v11.1.0 macOS version of Connect stopped working. This was likely due to upgrade of electron-builder which recently updated its process of building native deps (electron-userland/electron-builder#7196). In the Node.js ecosystem, the DEBUG env var is typically used to control which packages emit debug messages [1]. However, after the update of electron-builder, the env var also changed the behavior of one of the packages responsible for building the apps. This was confirmed by inspecting file tree between different app bundles and running the build locally with DEBUG set to electron-*. [1] https://www.npmjs.com/package/debug
ravicious
added a commit
that referenced
this pull request
Nov 30, 2022
It was added in effort to debug flaky Connect builds (#15836). However, we discovered that the v11.1.0 macOS version of Connect stopped working. This was likely due to upgrade of electron-builder which recently updated its process of building native deps (electron-userland/electron-builder#7196). In the Node.js ecosystem, the DEBUG env var is typically used to control which packages emit debug messages [1]. However, after the update of electron-builder, the env var also changed the behavior of one of the packages responsible for building the apps. This was confirmed by inspecting file tree between different app bundles and running the build locally with DEBUG set to electron-*. [1] https://www.npmjs.com/package/debug
ravicious
added a commit
that referenced
this pull request
Nov 30, 2022
It was added in effort to debug flaky Connect builds (#15836). However, we discovered that the v11.1.0 macOS version of Connect stopped working. This was likely due to upgrade of electron-builder which recently updated its process of building native deps (electron-userland/electron-builder#7196). In the Node.js ecosystem, the DEBUG env var is typically used to control which packages emit debug messages [1]. However, after the update of electron-builder, the env var also changed the behavior of one of the packages responsible for building the apps. This was confirmed by inspecting file tree between different app bundles and running the build locally with DEBUG set to electron-*. [1] https://www.npmjs.com/package/debug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is in effort to fix flaky builds described in #15835.