Your IP : 216.73.217.129
3
� f� � @ s� d dl Z d dlZd dlZd dlZd dlZd dlZd dlZd dlm Z m
Z
dd� Zdd� ZG dd� d�Z
G d d
� d
e
�ZG dd� de
�ZG d
d� dej�ZG dd� de�ZG dd� de�ZG dd� de�ZG dd� de�Zdd� Zedkr�e� dS )� N)�findfile�run_unittestc C s t jjt| dd��S )NZ
dtracedata)Zsubdir)�os�path�abspathr )�filename� r �5/opt/alt/python36/lib64/python3.6/test/test_dtrace.pyr s r c C st t jdd| �} y:dd� | j� D �}|jdd� d� dd� |D �}d j|�S ttfk
rn td
j| ���Y nX dS )aM Normalize DTrace output for comparison.
DTrace keeps a per-CPU buffer, and when showing the fired probes, buffers
are concatenated. So if the operating system moves our thread around, the
straight result can be "non-causal". So we add timestamps to the probe
firing, sort by that field, then strip it from the outputz\[[0-9]+ refs\]� c S s&