This repository has been archived by the owner on Oct 31, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
JsonProtcol.scala should properly decode BlockDeviceUtilizations #18
Labels
Comments
kayousterhout
added a commit
that referenced
this issue
Mar 21, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18.
kayousterhout
added a commit
that referenced
this issue
Apr 21, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
Apr 22, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
Apr 22, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
Apr 22, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
Apr 24, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
to kayousterhout/spark-1
that referenced
this issue
Apr 24, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in NetSys/spark-monotasks#18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
Apr 24, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
May 22, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
kayousterhout
added a commit
that referenced
this issue
Jun 3, 2015
Previous commits to add utilization information and add instrumentation for the total computation nanoseconds broke the Json related tests (JsonProtocolSuite.scala and ReplayListenerSuite.scala) because (a) these tests weren't properly updated and (b) JsonProtocol.scala did not include functionality to decode the cpu, disk, and network utilization. This commit mostly fixes those issues; the only remaining issue is described in #18. Conflicts: core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now it doesn't. This is not a high priority issue, because we're not currently replaying the UI ever.
The text was updated successfully, but these errors were encountered: