Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
30535
120ea99d Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
R
Succeeded
30535
4bad7481 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
R
Failed
30535
983bf48a Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
R
Succeeded
30535
c8ccda60 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
R
Succeeded
30535
5501379d Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
R
Succeeded
30535
749b89c0 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
Failed
30535
5babd809 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
Succeeded
30535
0d04e6d7 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
Succeeded
30535
b0a7f524 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
Failed
30535
3ed4928d Changed a field's access to be required in the admin client ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections The admin client treated a field's access as something that might be missing, and read it through a helper that answered "staff only" when it was, so that an admin deployed ahead of a Ghost without the setting would not draw a field as open to members. There is no such Ghost. This ships behind a flag with no released data, so nothing is running a version that serves a field without one, and being lenient about it only bought a quiet fallback that would outlive the reason for it. The setting is now simply part of what a field is, which is also what makes the compiler point at every place that builds one rather than leaving them to be found. Nothing renders differently. A field the server did somehow send without an access would now fail while drawing the settings list, which that screen already catches and reports as a broken section rather than retrying, so the failure stays where it can be seen instead of turning into a loop.
by Rob Lester
Succeeded
30535
3ed4928d Changed a field's access to be required in the admin client ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections The admin client treated a field's access as something that might be missing, and read it through a helper that answered "staff only" when it was, so that an admin deployed ahead of a Ghost without the setting would not draw a field as open to members. There is no such Ghost. This ships behind a flag with no released data, so nothing is running a version that serves a field without one, and being lenient about it only bought a quiet fallback that would outlive the reason for it. The setting is now simply part of what a field is, which is also what makes the compiler point at every place that builds one rather than leaving them to be found. Nothing renders differently. A field the server did somehow send without an access would now fail while drawing the settings list, which that screen already catches and reports as a broken section rather than retrying, so the failure stays where it can be seen instead of turning into a loop.
by Rob Lester
Succeeded
30535
c89a7fc2 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too.
by Rob Lester
Succeeded
30535
eefdfad9 Changed the browser tests to one timeout everywhere ref https://linear.app/ghost/issue/BER-3864/differentiate-public-and-private-member-projections A test had half as long to finish on a laptop as it had on CI, so a correct test could fail in front of the person writing it and pass once pushed. That is the worst way for a suite to be wrong: it costs an investigation every time, and it teaches everyone to disbelieve a local failure, which is the one signal that arrives early enough to be cheap. Half a minute is also not the difference between a fast iteration loop and a slow one, so the shorter budget was buying nothing to offset that. It was not a decision anybody made. The two were deliberately brought together at thirty seconds once; a later commit raised CI to sixty because CI needed longer, and splitting them again was a side effect of that rather than its intent. The identical branches left behind on the assertion timeout are the fossil of the same tidy-up, and go here too. Claude-Session: https://claude.ai/code/session_01XFCbqgYHYhd9rZ5WXtqZyT
by Rob Lester