Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Who present in meetingDavid L, Rob W, Pete, Jay B
Commitf5c396902fe755a2b6415961403ecef9420e118b
DetailsThe build stage has failed.
Root Cause Analysis

The Build stage has failed with the exception:

Code Block
themeConfluence
Exception: hudson.AbortException: script returned exit code 1 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:558)
 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:504)
 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:450)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
Primary Report: See more logs at https://qa.forgerock.com/am/master/f5c396902fe755a2b6415961403ecef9420e118b/343813e9-8727-4f7f-a221-82d94b3cdf68/build/jenkinslogs.txt ... (23 lines excluded) ... + docker ps --filter label=1 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES + docker container prune --force --filter label=1 Total reclaimed space: 0B + docker ps --filter label=1 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES script returned exit code 1Exception occurred: hudson.AbortException: script returned exit code 1
 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:558)
 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:504)
 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:450)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748) + curl --show-error --silent -u **** 
'https://ci.forgerock.org/blue/rest/organizations/jenkins/pipelines/OpenAM-master/pipelines/OpenAM-Pipeline/branches/master/runs/4771/nodes/?limit=10000' + mkdir 2064b2e3-6d44-4764-b8ad-8fcdb301ede6 + curl 
--show-error --silent -u **** 
'https://ci.forgerock.org/blue/rest/organizations/jenkins/pipelines/OpenAM-master/pipelines/OpenAM-Pipeline/branches/master/runs/4771/nodes/1183/log/?start=0'

The build stage on PR#11539 was successful. We have noticed that the PR was run with the configuration:

Code Block
themeConfluence
CI Build Configuration
mock-build=true
fast-mode=true
only-stages=ui-admin-smoke-tests,mandatory-coverage

The change included in the PR attempts to copy the stashed m2 files into every stages input directory. This was run on a PR with mock-build, which skips the build stage, and uses stashes from a previous run for subsequent stages. On the merge to master, this tries to copy the m2 stash into the input directory of the build stage. At this point, the m2 stash does not exist, and because cp command exits with an error code if there is nothing to copy, an exception is thrown.

Actions

Revert commit from master

Takeaways

The mock-build=true configuration broke the build in the jenkins scripts.

The build could add a comment and task to the PP in stash that will warn the developer of the risks. 

Jira
serverForgeRock JIRA
serverId45b4e541-fe03-30e2-b999-cf4e643b93ec
keyAME-20337

...

11/09/2020 16:50

Who present in meetingJay, Andy, Isaac, Pete R, Luna
Commit469cf832d38
DetailsFailure in the functional-tests stage test classes: TestSetDynamicAttributes
Root Cause Analysis

Looks like a Miranda timeout as the mock push service is not indicating that it has received a message. The commit that triggered this does not appear to be directly related to the failure we are seeing.

Failure seen in functional tests https://temper-dashboard.engineering.forgerock.com/openam/master/functional/test-run/469cf832d38f4e5a908d20e4c648176e017f4c6e/functional-tests

The test history does not seem to show this test as being flaky, however the run on the PR prior to merging was successful and local runs during the post mortem were also successful.

The test has succeeded in isolation locally, when looped in temper and run multiple times against a locally deployed AM. The stage was also green prior to merging the PR.

Actions

PR 12419 has been created to re-run the functional-tests stage. If it fails, the commit will be reverted, if it succeeds, an investigation will be needed into the flakiness of the test.

Takeaways


...