Closed CelianR closed 2 months ago
[Fast Unit Tests Report]
On pipeline 39033913 (CI Visibility). The following jobs did not run any unit tests:
If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help
Run ID: 61f04f82-28e1-43ac-b309-3df15439e9ad Metrics dashboard Target profiles
Baseline: 76be39d3e7a9cd16f334dbf012097f42ddadb76f Comparison: df616a2649a91a7006ada2148a8d5f2a071b8c1d
Performance changes are noted in the perf column of each table:
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 1 | 1 | 1 |
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 0 | 1 | 0 |
:information_source: Diff available in the job log.
👏 praise: Wtf this is so clean omg thank you for this !!!!
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 63 | 10 | 0 |
As discussed offline, I think we should test what happens if a very large number of jobs is modified. If this makes the message hard to read, we'll want to show a summary only (to not pollute the PR).
/merge
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main
is 26m.
Use /merge -c
to cancel this operation!
What does this PR do?
This adds a task that prints gitlab ci modifications as shown below. It also comments on PRs.
Motivation
Additional Notes
This adds:
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes