On Release dashboard a multi-run test (e.g. rolling upgrade) is marked as not planned, even though it was scheduled and started, but all runs are failed #533
Assignees
Labels
bug
Something isn't working
Comments
|
The reason here is that the submitted test has the version set as |
|
This screenshot is for one of 2 failed runs in this multi-run |
|
This is the overview of the main pipeline of that run: Pipeline tasks for versions 2022.2 and 2023.1 failed, so that the Argus runs were not even created for them. But Argus runs for 5.4 and 2024.1 were successfully created |
|
I see, in this case it is a planned feature to support base versions without a succesful upgrade, currently there's no way to tell which version is the base and upgraded one without upgraded one being submitted |
@k0machi |
@k0machi we work on this, and add report from sct_config.py before the test is running, isn't argus using those reports ? are they getting into Arugs ? |
fruch
added a commit
to fruch/scylla-cluster-tests
that referenced
this issue
Jan 2, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533
4 tasks
|
trying to fix the reporting of version to argus in: scylladb/scylla-cluster-tests#9638 |
fruch
added a commit
to fruch/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533
fruch
added a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533
mergify bot
pushed a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
4 tasks
mergify bot
pushed a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
4 tasks
mergify bot
pushed a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
4 tasks
mergify bot
pushed a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
4 tasks
mergify bot
pushed a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 7, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
4 tasks
fruch
added a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 8, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
fruch
added a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 8, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
fruch
added a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 8, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
fruch
added a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 8, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
fruch
added a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 8, 2025
`ARGUS_VERSION_RE` wasn't covering plain version like `6.3.0~dev` hence not sending it out to Argus. the change is fixing the regex this change also fixes `get_branch_version` to be able to return a full version string (including git sha and a date), cause we know Argus would need this data for metrics graphs and perf summaries. also not having this information, is casuing confusion on patch releases, when test are not get to the phase a node is upgrades Ref: scylladb/argus#533 (cherry picked from commit 7d2d0bb)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A multi-run test (e.g. rolling-upgrade) is marked as not-run on Release dashboard, if all runs of the test are failed.
When investigating test results of a release it may seem that such a test was not planned. The assignee would notice that the test was actually executed (and failed) only when checking My Jobs page.
Example of such a not-run test on a release dashboard:
And actual rub for the release in question:
The text was updated successfully, but these errors were encountered: