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

script,worker,suite: note down the rerun parameter in the first-job-in-suite #1198

Merged
merged 3 commits into from Sep 6, 2018
Merged

script,worker,suite: note down the rerun parameter in the first-job-in-suite #1198

merged 3 commits into from Sep 6, 2018

Commits on Aug 31, 2018

  1. suite: do not bail out if results.log is not around 

    Signed-off-by: Kefu Chai <kchai@redhat.com>
    @tchaikov
    tchaikov committed Aug 31, 2018
    Copy the full SHA
    14db4eb View commit details
    Browse the repository at this point in the history

  2. suite.run: extract write_result() out of prepare_and_schedule() 

    so it's more modular.

Signed-off-by: Kefu Chai <kchai@redhat.com>
    @tchaikov
    tchaikov committed Aug 31, 2018
    Copy the full SHA
    753c75e View commit details
    Browse the repository at this point in the history

Commits on Sep 3, 2018

  1. suite/run,schedule,result: write rerun memo as the first job in suite 

    so we don't need to wait for the job to write result to for rerunning
the test suite. without this change, the "result" is normally the last
job in the suite to be scheduled, so it's likely we will not have the
results.log until the suite is almost completed. afer this change,
a "first-in-suite" job is scheduled as the first job to note down
the subset and seed to run the suite.

Signed-off-by: Kefu Chai <kchai@redhat.com>
    @tchaikov
    tchaikov committed Sep 3, 2018
    Copy the full SHA
    d488b9b View commit details
    Browse the repository at this point in the history