Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[1599.26 --> 1600.06] a solution
[1600.06 --> 1601.42] for go test
[1601.42 --> 1602.40] it's written by
[1602.40 --> 1603.34] yana dogan
[1603.34 --> 1604.12] who works at
[1604.12 --> 1604.84] aws where
[1604.84 --> 1605.22] she has
[1605.22 --> 1606.38] instrumented with
[1606.38 --> 1607.32] open telemetry
[1607.32 --> 1607.96] go test
[1607.96 --> 1609.42] and we have
[1609.42 --> 1610.10] the idea that
[1610.10 --> 1610.92] it could also
[1610.92 --> 1612.56] work on java
[1612.56 --> 1613.60] unit test or
[1613.60 --> 1614.20] any other
[1614.20 --> 1615.36] language on
[1615.36 --> 1615.86] that we could
[1615.86 --> 1616.94] as well use
[1616.94 --> 1618.06] distributed traces
[1618.06 --> 1619.94] to visualize your
[1619.94 --> 1620.56] unit test
[1620.56 --> 1621.48] execution the
[1621.48 --> 1622.36] duration on the
[1622.36 --> 1623.06] outcome success
[1623.06 --> 1624.58] failure on where
[1624.58 --> 1625.44] i think open
[1625.44 --> 1626.56] telemetry is very
[1626.56 --> 1627.48] powerful is that
[1627.48 --> 1629.00] every large
[1629.00 --> 1630.00] organization has
[1630.00 --> 1630.94] its flaky test
[1630.94 --> 1632.08] detector implemented
[1632.08 --> 1632.96] in some ways
[1632.96 --> 1634.52] people tend to
[1634.52 --> 1635.26] reinvent the wheel
[1635.26 --> 1636.20] and with open
[1636.20 --> 1637.14] telemetry with the
[1637.14 --> 1638.54] open nature of
[1638.54 --> 1639.56] its format
[1639.56 --> 1641.36] then we have an
[1641.36 --> 1642.24] opportunity to
[1642.24 --> 1643.20] create a backbone
[1643.20 --> 1644.74] of unit test
[1644.74 --> 1646.20] results going
[1646.20 --> 1646.88] through open
[1646.88 --> 1648.10] telemetry channels
[1648.10 --> 1649.16] which typically can
[1649.16 --> 1649.78] be a kafka
[1649.78 --> 1651.16] streams then you
[1651.16 --> 1651.70] will have dev
[1651.70 --> 1652.30] ops team i
[1652.30 --> 1653.62] think flaky test
[1653.62 --> 1654.40] first not be
[1654.40 --> 1655.22] something that an
[1655.22 --> 1656.22] observability vendor
[1656.22 --> 1657.92] will implement but
[1657.92 --> 1659.30] maybe it will be
[1659.30 --> 1660.02] dev ops team
[1660.02 --> 1660.88] somewhere in an
[1660.88 --> 1661.72] organization who
[1661.72 --> 1662.98] will just connect
[1662.98 --> 1663.86] to these kafka
[1663.86 --> 1665.00] streams of open
[1665.00 --> 1665.92] telemetry traces
[1665.92 --> 1667.58] create its own
[1667.58 --> 1668.70] tool to process
[1668.70 --> 1669.58] its flaky test
[1669.58 --> 1671.14] report and share
[1671.14 --> 1671.62] this with the
[1671.62 --> 1672.66] community with this
[1672.66 --> 1673.26] open source
[1673.26 --> 1674.78] community nature i
[1674.78 --> 1676.10] imagine that an
[1676.10 --> 1677.08] open source solution
[1677.08 --> 1678.76] will grow in the
[1678.76 --> 1680.30] community leverage
[1680.30 --> 1681.38] the fact that open
[1681.38 --> 1682.20] telemetry is a very
[1682.20 --> 1683.12] flexible architecture
[1683.12 --> 1684.60] popular technology
[1684.60 --> 1685.64] with open telemetry
[1685.64 --> 1686.20] itself and the
[1686.22 --> 1687.66] streaming like kafka
[1687.66 --> 1689.44] kinesis or google
[1689.44 --> 1690.90] pub sub and so i
[1690.90 --> 1691.50] see a lot of
[1691.50 --> 1692.66] traction and i
[1692.66 --> 1693.60] expect the solution
[1693.60 --> 1694.82] to come soon in the
[1694.82 --> 1695.74] community so i'm
[1695.74 --> 1696.80] sold i definitely
[1696.80 --> 1697.82] want open telemetry
[1697.82 --> 1698.96] my ci city system
[1698.96 --> 1700.04] how do i get it
[1700.04 --> 1700.92] all like what do i
[1700.92 --> 1702.14] do well in theory
[1702.14 --> 1703.90] any system should
[1703.90 --> 1704.80] include open
[1704.80 --> 1706.24] telemetry or the