Bug #16622
closed
Timeout for `NuCommand` test is too short
Added by François ARMAND almost 5 years ago.
Updated over 4 years ago.
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.
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
- Target version set to 6.0.3
- 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
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Name check changed from To do to Reviewed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.
Also available in: Atom
PDF