Actions
Bug #16622
closed
Timeout for `NuCommand` test is too short
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
In a test, we have a command that is set to timeout after 100 ms. This is too short for our CI. I will change it to 500 ms.
Updated by François ARMAND almost 5 years ago
2020-01-24T16:02:03+0100 WARNING Failed to execute shell command from Rudder: error=2, No such file or directoryFiber failed. 16:02:22 A checked error was not handled. 16:02:22 Inconsistancy(oups, timed out) .... 16:02:22 Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.589 sec <<< FAILURE! 16:02:22 A command should::has only the environment variable explicitly defined(com.normation.rudder.hooks.RunNuCommandTest) Time elapsed: 0.031 sec <<< FAILURE! 16:02:22 java.lang.Exception: 'return code=0 16:02:22 PATH=/usr/lib/jvm/java-8-openjdk-amd64//bin:/home/jenkins/.cargo/bin:/usr/lib/jvm/java-8-openjdk-amd64/bin:/usr/local/bin:/usr/bin:/bin:/home/jenkins/bin 16:02:22 foo=bar 16:02:22 ' doesn't match 'return code=0 16:02:22 PATH=.* 16:02:22 foo=bar 16:02:22 ' 16:02:22 at com.normation.rudder.hooks.RunNuCommandTest.$anonfun$new$3(RunNuCommandTest.scala:76) 16:02:22
Updated by François ARMAND almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/2741
Updated by François ARMAND almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|ff1ab2783b07e85b702cc54535f0ae5650c68bcf.
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset over 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.
Actions