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.

Sign up for GitHub

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

Jump to bottom

openqa-investigate: Provide support for multi-machine scenarios #170

Merged
merged 4 commits into from
Jul 11, 2022
Merged

openqa-investigate: Provide support for multi-machine scenarios #170

merged 4 commits into from
Jul 11, 2022

Commits on Jul 8, 2022

  1. openqa-investigate: Provide support for multi-machine scenarios 

    See https://progress.opensuse.org/issues/95783
    @Martchus
    Martchus committed Jul 8, 2022
    Configuration menu
    Copy the full SHA
    2e52c6e View commit details
    Browse the repository at this point in the history

  2. Investigate only failed jobs 

    When checking `openqa.ini` on OSD I've noticed that hooks scripts for
incomplete jobs and timeouts are only invoking openqa-label-known-issues.
So for consistency with when we currently trigger the investigation I make
the investigate script anything but failures.
    @Martchus
    Martchus committed Jul 8, 2022
    Configuration menu
    Copy the full SHA
    614bfcc View commit details
    Browse the repository at this point in the history

  3. Sync investigation of parallel clusters via openQA comment 

    * Instead of only considering parallel parents, just do the investigation
  for any job with parallel dependencies
    * Avoid having to run the investigation script for all job results
    * Sync via an openQA comment instead (to avoid running the same
      investigation twice; abort if a concurrent job already does the
      investigation of the cluster)
    * Use `--max-depth 0` to clone all jobs in the parallel cluster,
      regardless whether we're starting from a parallel parent or child
        * Has no effect on other dependency types since we're
            * using `--skip-chained-deps` anyways
            * *not* using `--clone-children`
            * still excluding directly chained dependencies
* Write an investigation comment on the job we're actually investigating
  and on the first job in the cluster (for the synchronization)
* See https://progress.opensuse.org/issues/95783#note-58
    @Martchus
    Martchus committed Jul 8, 2022
    Configuration menu
    Copy the full SHA
    d4ff9c3 View commit details
    Browse the repository at this point in the history

  4. Apply job settings for investigate jobs to whole cluster 

    * See os-autoinst#170 (review)
* See https://openqa.opensuse.org/tests/2456116#comment-286104 for an
  example
    @Martchus
    Martchus committed Jul 8, 2022
    Configuration menu
    Copy the full SHA
    c12e3b3 View commit details
    Browse the repository at this point in the history