Skip to content

Make trace dispatch purely a function of context rather than a function of both context and data. This lets us delete a lot of machinery for managing data-dependent tracing: levels, sublevels, post_process_call, new_base_main, custom_bind and so on. #2289

Make trace dispatch purely a function of context rather than a function of both context and data. This lets us delete a lot of machinery for managing data-dependent tracing: levels, sublevels, post_process_call, new_base_main, custom_bind and so on.

Make trace dispatch purely a function of context rather than a function of both context and data. This lets us delete a lot of machinery for managing data-dependent tracing: levels, sublevels, post_process_call, new_base_main, custom_bind and so on. #2289

Triggered via pull request October 24, 2024 19:32
Status Failure
Total duration 6m 44s
Artifacts

integration.yml

on: pull_request
Matrix: test-ubuntu
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
integration tests on 3.10 on ubuntu-latest
Process completed with exit code 1.
integration tests on 3.11 on ubuntu-latest
The job was canceled because "_3_10_ubuntu-latest" failed.
integration tests on 3.11 on ubuntu-latest
The operation was canceled.
integration tests on 3.10 on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
integration tests on 3.10 on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/