[
https://issues.apache.org/jira/browse/MESOS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604982#comment-14604982
]
Adam B commented on MESOS-2402:
-------------------------------
I haven't seen it fail recently. The last failure was back in mid-April, after
[~vinodkone]'s previous fix in March. Maybe it was fixed again by [~tnachen] or
[~jieyu]'s changes in late April. Let's close as fixed/not-reproducible, and we
can reopen it if it starts failing again. Thanks for attempting to reproduce,
[[email protected]]
commit bd0863e8482f38f905aebffb7d710b58c9f44f20
Author: Jie Yu <[email protected]>
Date: Mon Apr 20 12:56:07 2015 -0700
Changed the isolator recover interface to take a set of orphan
containers detected by the launcher.
Review: https://reviews.apache.org/r/33413
commit 24c78a156f68f09de2c7b6729e077547edf768db
Author: Jie Yu <[email protected]>
Date: Mon Apr 20 12:17:51 2015 -0700
Made the launcher recover interface to return a set of orphan containers.
Review: https://reviews.apache.org/r/33412
commit 1a69b55652e867fee80ffb224ee3096b9e6c5390
Author: Timothy Chen <[email protected]>
Date: Wed Apr 15 15:18:35 2015 -0700
Fixed recover tasks only by the intiated containerizer.
Review: https://reviews.apache.org/r/33257
> MesosContainerizerDestroyTest.LauncherDestroyFailure is flaky
> -------------------------------------------------------------
>
> Key: MESOS-2402
> URL: https://issues.apache.org/jira/browse/MESOS-2402
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Vinod Kone
> Assignee: haosdent
> Fix For: 0.23.0
>
>
> "Failed to os::execvpe in childMain". Never seen this one before.
> {code}
> [ RUN ] MesosContainerizerDestroyTest.LauncherDestroyFailure
> Using temporary directory
> '/tmp/MesosContainerizerDestroyTest_LauncherDestroyFailure_QpjQEn'
> I0224 18:55:49.326912 21391 containerizer.cpp:461] Starting container
> 'test_container' for executor 'executor' of framework ''
> I0224 18:55:49.332252 21391 launcher.cpp:130] Forked child with pid '23496'
> for container 'test_container'
> ABORT: (src/subprocess.cpp:165): Failed to os::execvpe in childMain
> *** Aborted at 1424832949 (unix time) try "date -d @1424832949" if you are
> using GNU date ***
> PC: @ 0x2b178c5db0d5 (unknown)
> I0224 18:55:49.340955 21392 process.cpp:2117] Dropped / Lost event for PID:
> [email protected]:39647
> I0224 18:55:49.342300 21386 containerizer.cpp:911] Destroying container
> 'test_container'
> *** SIGABRT (@0x3e800005bc8) received by PID 23496 (TID 0x2b178f9f0700) from
> PID 23496; stack trace: ***
> @ 0x2b178c397cb0 (unknown)
> @ 0x2b178c5db0d5 (unknown)
> @ 0x2b178c5de83b (unknown)
> @ 0x87a945 _Abort()
> @ 0x2b1789f610b9 process::childMain()
> I0224 18:55:49.391793 21386 containerizer.cpp:1120] Executor for container
> 'test_container' has exited
> I0224 18:55:49.400478 21391 process.cpp:2770] Handling HTTP event for process
> 'metrics' with path: '/metrics/snapshot'
> tests/containerizer_tests.cpp:485: Failure
> Value of: metrics.values["containerizer/mesos/container_destroy_errors"]
> Actual: 16-byte object <02-00 00-00 17-2B 00-00 E0-86 0E-04 00-00 00-00>
> Expected: 1u
> Which is: 1
> [ FAILED ] MesosContainerizerDestroyTest.LauncherDestroyFailure (89 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
