Skip to content
Python CI

feat: add timing for results filtering #221

Sign in to view logs

feat: add timing for results filtering

feat: add timing for results filtering #221

Triggered via pull request January 4, 2024 19:34
@davidnuondavidnuon
synchronize #142
feature/search-performance-logging
Status Success
Total duration 1m 12s
Artifacts –

ci.yml

on: pull_request
Matrix: Tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Tests (ubuntu-20.04, 3.8, quality)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (ubuntu-20.04, 3.8, django40)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (ubuntu-20.04, 3.8, django32)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (ubuntu-20.04, 3.8, django42)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/