-
Notifications
You must be signed in to change notification settings - Fork 224
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
tracking issue for spurious Windows CI failures due to azure-functions-core-tools dep #3107
Comments
github-actions
bot
added
the
agent-nodejs
Make available for APM Agents project planning.
label
Jan 18, 2023
Another failure on the "main" branch Jenkins CI windows build: |
trentm
changed the title
tracking issue for Windows CI failures due to azure-functions-core-tools dep
tracking issue for spurious Windows CI failures due to azure-functions-core-tools dep
Jan 24, 2023
And again (on the same PR): https://apm-ci.elastic.co/blue/organizations/jenkins/apm-agent-nodejs%2Fapm-agent-nodejs-mbp/detail/PR-3121/3/pipeline This issue needs to be resolved now. |
trentm
added a commit
that referenced
this issue
Jan 24, 2023
This is because the 'azure-function-core-tools' package install on Windows is too flaky in CI. Closes: #3107
trentm
added a commit
that referenced
this issue
Jan 24, 2023
This is because the 'azure-function-core-tools' package install on Windows is too flaky in CI. Closes: #3107
fpm-peter
pushed a commit
to fpm-git/apm-agent-nodejs
that referenced
this issue
Aug 20, 2024
This is because the 'azure-function-core-tools' package install on Windows is too flaky in CI. Closes: elastic#3107
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #3071 the "azure-functions-core-tools" package was added to the top-level "devDependencies". This dep installs a
func
CLI tool that is used fortest/instrumentation/azure-functions/azure-functions.test.js
to run (running Azure Functions locally). This package has a postinstall step that downloads a large support package -- on the order of a couple hundred MBs.After this merged to main, it was noticed that the Jenkins Windows CI failed a number of times with:
Currently this issue is to track such failures to see if we want/need to deal with it.
A weird side-effect of this failure: Currently the test run with retry the
npm install
. In the cases below (so far), the secondnpm install
passes, then the tests fail. The test failure is in the "http2" tests. This failure is actually likely due to the firstnpm install
failure, because the "https-pem" devDependency post install script somehow now wasn't run -- at least not run properly -- such that there isn't a pem file to use for http2/https testing.noticed failures
possible fix/workaround options
If this becomes too-frequent of a flaky-test issue then some possible options are:
npm install
manually in "test/instrumentation/azure-functions/azure-functions.test.js" on first run, skip running tests on Windows.So far, if this tends to be a failure only for Windows CI, then I prefer option 1.
The text was updated successfully, but these errors were encountered: