-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Fix typecheck foundations #167060
Fix typecheck foundations #167060
Conversation
…s on OOM kills of execa/child_proc, log, fix some small issues
Pinging @elastic/kibana-operations (Team:Operations) |
4c522f0
to
3e46165
Compare
3e46165
to
e1f2044
Compare
if (code > 0 && !(code === 143 || code === 130)) { | ||
throw createFailError(`[${name}] exited with code ${code}`, { | ||
exitCode: code, | ||
}); | ||
} | ||
|
||
// A stop signal of SIGABRT indicates a self-inflicted app crash, | ||
// then we can't rely on an exit code, because it's not passed | ||
if (signal === 'SIGABRT') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% confident we can trust that there will not be other signals that might indicate a crash. We don't have to do that in this PR, but in the future I'd like to simplify this code so that it just listens for the rejected promise instead of trying to be so clever and possibly missing some things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair point, here's a fix: d057ecf
@@ -124,6 +124,9 @@ run( | |||
'--pretty', | |||
...(flagsReader.boolean('verbose') ? ['--verbose'] : []), | |||
], | |||
env: { | |||
NODE_OPTIONS: '--max-old-space-size=8192', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
@@ -67,7 +67,7 @@ | |||
"test:ftr:server": "node scripts/functional_tests_server", | |||
"test:jest": "node scripts/jest", | |||
"test:jest_integration": "node scripts/jest_integration", | |||
"typecheck": "node scripts/type_check" | |||
"test:type_check": "node scripts/type_check" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you rename the script?
For me test:type_check
would mean run typechecks on the test code, or similar - this is not test-related, but typechecking any code
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
## Summary After merging #167060, `Check Types` is going to fail in the on merge pipeline until all type errors are triaged. For now, lets use the commit diff type check.
This is a manual backport of elastic#167060 + recent updates to the backported files
## Summary We've recently seen a handful of step timeouts when running type-checks. While this is not the best solution, it mitigates for potential builds failed, and retries due to timeouts. This PR also contains some cleanup around previous, type-check related jobs (e.g.: the [type-check issue of 2023 august](#167060))
Summary
This PR is the core part of #166813. The original work seems to grow large, and we'd like to enable a preventive check beforehand to prevent more errors from entering the codebase.
The idea is to have a selective type check that would only check changed files' projects.
ci:hard-typecheck
is present, run the regular (but now, working) full typecheck (expected to fail: )cc: @watson