Update dependencies (NPM and others)#451
Update dependencies (NPM and others)#451deribaucourt wants to merge 13 commits intoyoctoproject:stagingfrom
Conversation
deribaucourt
force-pushed
the
update-npm
branch
2 times, most recently
from
26472ab to
1f52746
Compare
deribaucourt
changed the title
deribaucourt
force-pushed
the
update-npm
branch
from
b6ce4ad to
3935c28
Compare
WilsonZiweiWang
force-pushed
the
update-npm
branch
from
e249b4c to
1d37a65
Compare
|
@WilsonZiweiWang from my experience, some tests failed due to calling Maybe I'm wrong and the tests fail for a reason, but that's my thoughts so far. |
When the integration tests are skipped, the CI can consistently pass if a little more time is given to the unit tests, for example, 10 minutes of timeout. Successful runs with integration tests skipped: According to the logs from a previous CI run and my local runs, they are all stuck at the |
|
While the bitbake is scanning the project ( zwang 1479052 12.5 0.4 208992 136632 ? Sl 15:20 0:01 /usr/bin/python3 /home/zwang/projects/vscode-bitbake/resources/poky/bitbake/bin/bitbake-server decafbad 3 6 /home/zwang/projects/vscode-bitbake/integration-tests/project-folder/build/bitbake-cookerdaemon.log /home/zwang/projects/vscode-bitbake/integration-tests/project-folder/build/bitbake.lock /home/zwang/projects/vscode-bitbake/integration-tests/project-folder/build/bitbake.sock 0 0 None 0In the meantime, the extension host is repeatedly trying to reconnect to the bitbake server: |
|
Maybe we need to disable some test parallelization option that is new or reworded? |
WilsonZiweiWang
force-pushed
the
update-npm
branch
from
66022a9 to
d9cc7eb
Compare
deribaucourt
force-pushed
the
update-npm
branch
5 times, most recently
from
544c254 to
57a09bc
Compare
Run `npm update` in every package to update the dependencies. Fixes a few security audit warnings.
Run our update-refs scripts to bump all non-nodejs dependencies.
Update the run-test script based on the latest vscode-test sample.
Follow the same pattern as for other settings to avoid potential mismatches.
With the updated extensions, some diagnostics linger. They are not harmful, we just need the test to filter out our own expected.
It looks like pylance now sends the diagnostics as pylint, and require to show and save the document before seding them.
Otherwise it would simply remove the line, which may revert to the user's command wrapper if they had one.
The latest vscode version doesn't want to fire the OpenDocument language server event, so we need to deploy full force edits to trigger the diagnostics. It was fine except on headless mode. Also sometimes the diagnostics are sourced as Pylance, sometimes as Pylint, so we use a broader filter. See: microsoft/vscode#138924
deribaucourt
force-pushed
the
update-npm
branch
from
dfd88c5 to
38f9d04
Compare
deribaucourt
force-pushed
the
update-npm
branch
from
38f9d04 to
1a2a8a9
Compare
Run `npm upgrade` in all packages to bump the minor revisions on all components. Some npm audit warnings are still present so another ncu round will be required.
deribaucourt
force-pushed
the
update-npm
branch
from
1a2a8a9 to
52f5044
Compare
deribaucourt
force-pushed
the
update-npm
branch
from
52f5044 to
58a1372
Compare
2 participants
Run
npm updatein every package to update the dependencies. Fixes a few security audit warnings.