This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 165
edit mgmt systems #2
Labels
Comments
ghost
assigned bcrochet
Apr 2, 2013
Merged
mfalesni
pushed a commit
that referenced
this issue
Oct 19, 2017
* [WIP] Check V2_key perms * Rework for review * Rework for review #2 * Move test to distributed FA
bsquizz
added a commit
to bsquizz/integration_tests
that referenced
this issue
Feb 27, 2018
Add hard reboot string Remove un-needed lines Add 'not' lint fixes lint ManageIQ#2
jamesooden
added a commit
to jamesooden/integration_tests
that referenced
this issue
Mar 2, 2018
Updated logging calls to not use format() as that is unnecessary. Also had to add an import of logger to coverage_report_sprout.py.
jamesooden
added a commit
to jamesooden/integration_tests
that referenced
this issue
Mar 23, 2018
Calls to ssh.run_command have been wrapped to ensure consistent logging and error handling.
mshriver
pushed a commit
that referenced
this issue
Mar 24, 2018
…bs (#6916) * Add ability to aggregate coverage from multiple jenkins jobs In addition to aggregating multiple Jenkins jobs I had to do a work around because we ran out of disk space on the appliance. The work around was to extract the coverage tarballs in waves, merge that data, cleanup and use the merged data in the next wave. Taking this route allowed me to quickly get this working, but over time I think we seriously need to look at a different way of storing and getting out the coverage data from test runs. * Code review #1 PR 6916 The particular issue in question was the proper use of namedtuple classes. Sorted this out, so I wasn't creating a Build class over and over again. Also, had to deal with the fact that namedtuple generated classes are immutable. * Move check for no eligible jobs to account for multiple jobs. * Code Review #2 for PR 6916 Calls to ssh.run_command have been wrapped to ensure consistent logging and error handling.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: