text
stringlengths
0
1.8k
[1522.66 --> 1523.10] is that
[1523.10 --> 1523.94] we often
[1523.94 --> 1524.54] talk about
[1524.54 --> 1525.26] the divergence
[1525.26 --> 1526.10] between dev
[1526.10 --> 1526.64] on ops
[1526.64 --> 1527.80] dev wanting
[1527.80 --> 1528.68] changing things
[1528.68 --> 1529.32] all the time
[1529.32 --> 1529.82] to deliver
[1529.82 --> 1530.92] new features
[1530.92 --> 1531.48] new business
[1531.48 --> 1532.14] value on
[1532.14 --> 1532.76] ops wanting
[1532.76 --> 1533.30] stability
[1533.30 --> 1534.66] we see that
[1534.66 --> 1535.62] on the cicd
[1535.62 --> 1536.14] platform
[1536.14 --> 1536.90] we have the
[1536.90 --> 1537.56] same challenge
[1537.56 --> 1538.32] with ci
[1538.32 --> 1538.98] administrators
[1538.98 --> 1540.30] wanting a
[1540.30 --> 1541.18] stable platform
[1541.18 --> 1541.88] to keep it
[1541.88 --> 1542.64] up and running
[1542.64 --> 1543.28] because it's
[1543.28 --> 1543.94] mission critical
[1543.94 --> 1544.78] for the company
[1544.78 --> 1546.24] on dev teams
[1546.24 --> 1547.02] wanting to
[1547.02 --> 1547.68] onboard new
[1547.68 --> 1548.16] projects
[1548.16 --> 1548.62] with new
[1548.62 --> 1549.00] needs
[1549.00 --> 1549.80] new fancy
[1549.80 --> 1550.84] requirements
[1550.84 --> 1551.92] and we
[1551.92 --> 1552.54] wanted to
[1552.54 --> 1552.96] find
[1552.96 --> 1553.68] assistance
[1553.68 --> 1554.98] so that
[1554.98 --> 1555.88] people could
[1555.88 --> 1556.48] embrace
[1556.48 --> 1557.04] changes
[1557.04 --> 1558.06] with confidence
[1558.06 --> 1558.84] and we felt
[1558.84 --> 1559.56] that observability
[1559.56 --> 1560.38] would be key
[1560.38 --> 1561.04] to create
[1561.04 --> 1561.66] this confidence
[1561.66 --> 1562.46] to embrace
[1562.46 --> 1562.94] changes
[1562.94 --> 1563.72] on the cd
[1563.72 --> 1564.22] pipelines
[1564.22 --> 1564.90] that's a great
[1564.90 --> 1565.46] point and it
[1565.46 --> 1566.20] made me think
[1566.20 --> 1566.98] of flaky
[1566.98 --> 1567.78] tests when
[1567.78 --> 1568.28] everything is
[1568.28 --> 1568.88] fine and the
[1568.88 --> 1569.54] cicd system
[1569.54 --> 1570.36] still fails
[1570.36 --> 1571.54] and you run
[1571.54 --> 1571.86] it again
[1571.86 --> 1572.18] and then it
[1572.18 --> 1572.52] passes
[1572.52 --> 1573.70] so i think
[1573.70 --> 1574.02] flaky
[1574.02 --> 1574.74] tests when
[1574.74 --> 1575.02] it comes
[1575.02 --> 1575.42] to
[1575.42 --> 1576.08] code
[1576.08 --> 1576.90] and developers
[1576.90 --> 1577.64] tend to be
[1577.64 --> 1578.56] very problematic
[1578.56 --> 1579.78] especially for
[1579.78 --> 1580.48] legacy code
[1580.48 --> 1580.88] bases
[1580.88 --> 1582.22] especially for
[1582.22 --> 1582.72] distributed
[1582.72 --> 1583.22] systems
[1583.22 --> 1583.62] when you have
[1583.62 --> 1584.30] tests and you're
[1584.30 --> 1584.98] testing distributed
[1584.98 --> 1586.06] systems you have
[1586.06 --> 1586.68] race conditions
[1586.68 --> 1587.36] left right and
[1587.36 --> 1587.60] center
[1587.60 --> 1588.88] so how does
[1588.88 --> 1589.86] open telemetry help
[1589.86 --> 1590.72] with flaky tests
[1590.72 --> 1592.82] so this is in
[1592.82 --> 1593.52] our radar
[1593.52 --> 1594.82] to also add
[1594.82 --> 1595.90] observability to
[1595.90 --> 1596.60] unit test
[1596.60 --> 1597.16] execution
[1597.16 --> 1599.26] there is already