Skip to content
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

use user given task names in chrome trace #570

Merged
merged 3 commits into from
Aug 29, 2024

Conversation

m-fila
Copy link
Contributor

@m-fila m-fila commented Aug 27, 2024

Adding user defined task names #560 in visualization with :chrome-trace #540 . By default an automatically inferred named is used, if a task has user provided name then it will be used instead

logs_event_pairs is not used anymore as the :data_annotation are not present in it

@jpsamaroo
Copy link
Member

logs_event_pairs is not used anymore as the :data_annotation are not present in it

That's a bug, I did something stupid by making the IDs of :data_annotation start/finish not match up (which logs_event_pairs rightly skips over, since it can't then provide a matching pair). Making the ID field in

Dagger.TimespanLogging.timespan_finish(ctx, :data_annotation, nothing, nothing)
match the timespan_start line above it would fix this issue.

@m-fila
Copy link
Contributor Author

m-fila commented Aug 27, 2024

Thanks 😃 I found that mismatch but then read the comment # TODO: Remove redundant log event and fought it's intended. I'll fix and update the PR tomorrow

@jpsamaroo jpsamaroo merged commit a4d6a67 into JuliaParallel:master Aug 29, 2024
9 of 11 checks passed
@jpsamaroo
Copy link
Member

Awesome, thank you!

@m-fila m-fila deleted the chrome_trace_names branch August 29, 2024 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants