-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
src: trace_event: secondary storage for metadata #20900
Conversation
7392e98
to
210a0c4
Compare
I am unable to build on AIX to reproduce the timeout that only happens on AIX.
This is after I setup the environment as per I'm stuck at this point. @mhdawson @richardlau is there a way to get help with this? The test that times out has a large number of FS/IO operations in it. It is quite possible that the AIX machines genuinely not able able to finish this work in 120s. Either way, I cannot build on the machine, so I am unable to debug. |
cc @nodejs/platform-aix @jBarz |
@refack pointed me to the job config on jenkins which fills in more blanks for me. I can build now. |
Out of interest, what was the missing piece? |
Building requires LIBPATH to be unset and CC to be set to gcc.
…On Wed, Jun 27, 2018, 6:57 PM Richard Lau ***@***.***> wrote:
Out of interest, what was the missing piece?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20900 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAE0qSNw7dc-nfHJrPuPEde4lqhyOgHSks5uBDf2gaJpZM4UJgl1>
.
|
The aix timeout should be fixed by #21335. On AIX the race manifests as an infinite loop on this particular test on erroneous shutdown. EDIT: minimal repro: |
Ping @ofrobots |
Thanks for the ping. I plan to come back to this later this week. |
Ping again :-) |
I am planning to come back to this once #22865 is addressed, i.e. after libuv/libuv#2003, #23110, and #22938 land. |
210a0c4
to
7bcd8fa
Compare
7bcd8fa
to
f51983d
Compare
This is updated now given the cascade of blockers are now resolved. New CI: https://ci.nodejs.org/job/node-test-pull-request/17751/ Linter re-run: https://ci.nodejs.org/job/node-test-linter/22720/ |
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush.
f51983d
to
2bde938
Compare
CI is green. @jasnell assuming your LGTM from 5 months ago (!) still holds, I am going to land this later today. The rebase did not change this PR in substance. |
Landed in f5986a4 |
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush. PR-URL: #20900 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
Should this be backported to |
backport on #23700 |
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush. PR-URL: #20900 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush. PR-URL: nodejs#20900 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Backport-PR-URL: nodejs#23700
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush. Backport-PR-URL: #23700 PR-URL: #20900 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Backport-PR-URL: #23700
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush. Backport-PR-URL: #23700 PR-URL: #20900 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Backport-PR-URL: #23700
Metadata trace-events should be held in secondary storage so that they can be periodically reemitted. This change establishes the secondary storage and ensures that events are reemitted on each flush. Backport-PR-URL: #23700 PR-URL: #20900 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Backport-PR-URL: #23700
Metadata trace-events should be held in secondary storage so that they
can be periodically reemitted. This change establishes the secondary
storage and ensures that events are reemitted on each flush.
/cc @nodejs/trace-events
CI:
https://ci.nodejs.org/job/node-test-pull-request/15041/https://ci.nodejs.org/job/node-test-pull-request/15640/Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes