Closed lukas-vlcek closed 2 years ago
@lukas-vlcek: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: lukas-vlcek
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@lukas-vlcek: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
@lukas-vlcek: This pull request references Bugzilla bug 2002671, which is invalid:
Comment /bugzilla refresh
to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
/bugzilla refresh
@lukas-vlcek: This pull request references Bugzilla bug 2002671, which is invalid:
Comment /bugzilla refresh
to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
/bugzilla refresh
@lukas-vlcek: This pull request references Bugzilla bug 2002671, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (anli@redhat.com), skipping review request.
/retest
@lukas-vlcek: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
ci/prow/images | ddfb7e72f84b9007475bc9e2f60af66e922e6209 | link | /test images |
ci/openshift-jenkins/json-file | ddfb7e72f84b9007475bc9e2f60af66e922e6209 | link | /test json-file |
ci/openshift-jenkins/logging | ddfb7e72f84b9007475bc9e2f60af66e922e6209 | link | /test logging |
Full PR test history. Your PR dashboard.
/hold
There seem to be some versioning issues that must be addressed first. A quick hint from Jeff:
[...] it may because the lock file is not checked in for ruby. same with the python command, we should be able to "lock" what we are building
Merging manually as this only changes the logging-dump script for evaluating 3.11 issues.
@lukas-vlcek: All pull requests linked via external trackers have merged:
Bugzilla bug 2002671 has been moved to the MODIFIED state.
Description
Adding new resources:
Extending curl timout to 20 sec:
We are experiencing empty resource logs in must-gather archives. Instead of expected content they only contain message referencing to "timeout error code (28)".
Completing the documentation.
Adding suffix to each type of resource.
/cc @btaani /assign @jcantrill
Links